How to Connect User Problems to Business Goals

​Dear Reader,​

Most people mistake Impact Mapping as a framework. As something they “have to” fill out. I encourage teams to treat it as a visual aid. Here’s what it can do for you but what it relies on to be useful:

• It’s a structure for the Synthesis of your Discovery (and OKRs and Strategy Work).
• It’s Garbage-in-Garbage-out. It either connects the dots that are there (independent of their quality) but can also help you uncover your blind spots

Here are five proven practices that improve your way of connecting business goals to user problems through Impact Mapping immediately:

Use Specific Impacts

It's easy to default to generic KPIs to set your Impact. But this will rarely help a product team with guiding their decisions. Instead, use specific Strategy Choices to define clear Impacts:

Accelerate inventory through private sellers → X% Inventory share from Private Sellers (instead of "Inventory Growth")

Connect it to other Practices

Impact Mapping should guide the decision-making of existing practices, not start a parallel universe. The various levels of the map connect to various Discovery practices like Strategy/Alignment to frame the Impact and Actors, Research to arrive at proven Outcomes, and Ideation + Testing for the Output and Experiment levels. Another loose mapping is that the Impact should link to Company KRs or Annual Team KRs, whereas the Outcomes should inform your Quarterly team-level KRs

Adapt and Bend it

Almost no way of working adds value to your work "out of the box." Modify it in whatever way possible. Like trying to reverse-engineer the gaps in your understanding by starting at the bottom (Outputs) and "mapping up." Or by adding more layers to the individual levels: One client added another overarching grouping of actors to group similar Actors by Geography.

Treat it as a Range of Options, Not Promises

Neither the Outcomes nor the Outputs items on an Impact Map should be seen as promises. Instead, they outline the options you have. For the 𝘈𝘤𝘵𝘰𝘳𝘴, that describes the possible groups of people for whom you 𝘤𝘰𝘶𝘭𝘥 solve a problem. For the 𝘖𝘶𝘵𝘤𝘰𝘮𝘦𝘴, that describes the options you have to improve the life of the various Actors. For the 𝘖𝘶𝘵p𝘶𝘵𝘴, that describes the 𝘱𝘰𝘴𝘴𝘪𝘣𝘭𝘦 solutions you could pursue to drive the identified Outcomes.

Prioritize Actor Outcomes over Business Outcomes

There's nothing wrong with aiming to improve a revenue target. But that doesn't mean a valid Outcome is to "put more items in my shopping basket." That's what the business wants. Instead, you have to understand what is in the user’s way of completing the actions that will contribute and lead to business success. "Continue shopping without having to leave the basket view first."

​

Thank you for Practicing Product,

Tim

PS.: My thinking on Impact Mapping stands on the shoulders of giants like Goijko Adzic, through whom I uncovered this approach about 10 years ago and have iterated on it ever since.

How to Dive Deeper into Product Discovery

Learn how I helped companies like Deutsche Telekom and Forto hone their Product Discovery practices. I closely work with product organizations through workshops and coaching to introduce and adapt Product Discovery.

Content I found Practical This Week

What did you think of this week's newsletter?

Who is Tim Herbig?

As a Product Management Coach, I guide Product Teams to measure the progress of their evidence-informed decisions.

I identify and share the patterns among better practices to connect the dots of Product Strategy, Product OKRs, and Product Discovery.