I bet after my previous deep dive on Impact Mapping, now you want to implement it. Right? In that piece, I described my custom approach to this technique and how Impact Mapping helps teams align their work with strategic goals. If you read it, you know what Impact Mapping is and why it is helpful. But that’s not enough. So I wrote this new article, detailing how you can use it. This is a step-by-step guide on how to run an Impact Mapping exercise with three alternatives, each suited to a different organisational context. Whether you’re in a product-driven environment, a feature factory, or somewhere in the messy middle, you’ll find a method that fits.
In December 2025, I had a chat with my friend about AI adoption at her company. Her response was anything but enthusiastic. Her response was anything but enthusiastic: "Oh, great. Now we all have to write code too." 2 months later, her sarcasm had been replaced by genuine awe. Not just at AI, but at what she is now capable of doing with the tools she’s been using.
What teams call "pragmatic decisions" are often just the path of least resistance. And now that AI coding makes this path even more attractive, “pragmatic” can become the synonym for “dangerous”.
As service providers, we tend to have the challenge that we do not get full transparency about overarching goals, which makes it hard to find the right metrics. Often projects are scoped together, and the goal is just to get that scope done. Is there room for real outcomes or optimisation?
What if I told you Impact Mapping is more than just a discovery tool? Today I’m here to show you how Impact Mapping can serve other purposes: How you can use it to bring your teams together around shared product goals and align their work with the overall strategic business context.
But let's be honest: the most impactful transformations in life or business are never solo performances. It's a bit like trying to high-five yourself - possible, but not nearly as satisfying or effective as having a partner! Here's your week's challenge.