- This topic has 1 reply, 2 voices, and was last updated 1 year, 6 months ago by
-
Posts
-
Feedback on email to software engineering leader
Hello Chris,
According to the 2022 Gartner Software Engineering Leaders survey, the top performance objective was meeting business goals. To achieve these goals, it’s important to work with product managers to create and deliver great digital products and experiences. This requires focusing on the business case, delivery processes, UX design, and building shared assets.
By way of introduction, I co-lead that Gartner team aligned to supporting leaders at GDIT and across GD.
Our experts just published “2023 Strategic Roadmap for Building and Delivering Digital Products to Drive Business Results” that outlines the best practices from across the market for doing exactly that.
I would love to hear your strategy for delivering business results this year and how it compares to the best practices our analysts have learned.
Would you be available for a brief discussion next week? I’d be happy to bring a copy of the report.
Best regards,
Travis Enfield
Hey Travis,
You need to personalise that first line.
Also, rethink the email from the “why would they give a shit” angle.
Get rid of any language like “by way of introduction”. Would you say that in person? Probably not. So it shouldn’t be in an email either.
This isn’t perfect but I’d be leaning into something like –
“Hi Chris,
It’s the beginning of March and so I’m sure you’ve got your plan for the year in place.
Our analysis have just published a best practices report.
Would it be worth 10 minutes for me to share a couple of highlights to make sure that they align with the goals you’ve set?”
- You must be logged in to reply to this topic.
