Michael Aring’s Post

View profile for Michael Aring, graphic

GTM at Gitpod | Focused on Developer Productivity

This is a great post by the team at commercetools 🪄 It shows how a 150-person engineering org explored, evaluated, and implemented a new technology in a structured way. And then they wrote it all down and shared it with the world! Buying completely new tools (for example CDEs or AI coding assistants) is challenging for many engineering organizations. Discussions swing from one extreme ("This is going to change the world! Everyone will be using this!) to the other ("This cannot possibly pass our security requirements for a POC"). Neither perspective is helpful for good decisions. It's best to start with a simple Q&A session that should look like something like this: - What do we want to achieve with the new technology? - What is the primary use case? (Alternatively: what problem are we facing today that could be addressed by the new technology?) - What is one team that could test it this quarter? - How do we want to set it up? (multi-tenant vs. single-tenant, open-source vs. full-service vendor) - How are we going to measure if it is a success or not? (IMHO, with a quantitative ROI perspective and a qualitative user survey) - Who will make the decision by when? The world of developer tools would benefit a ton from more teams writing about how they evaluate new tools. Thanks Tobias Deekens 🙏🏼

Michael Aring

GTM at Gitpod | Focused on Developer Productivity

1y

My only question would be: why did you make the evaluation period so long? I would challenge the team that it is possible to get a similar understanding after just a few weeks.

Like
Reply

To view or add a comment, sign in

Explore topics