Impact mapping

Impact mapping is a strategic planning technique that connects business goals to specific deliverables through a visual map. The technique asks four questions in sequence: Why (goal), Who (actors), How (impacts), and What (deliverables). By maintaining this chain of reasoning, impact maps ensure that features and initiatives can be traced back to meaningful outcomes.

The four levels

Why (Goal) - The business objective you're trying to achieve. This should be measurable and valuable: "Increase monthly recurring revenue by 25%" or "Reduce customer churn to under 5%." Without a clear goal, everything that follows lacks purpose.

Who (Actors) - The people whose behavior would change to achieve the goal. These might be users, customers, partners, or even internal stakeholders. Actors are not abstract segments but specific groups whose actions matter.

How (Impacts) - The changes in actor behavior that would contribute to the goal. How should actors behave differently? What should they start doing, stop doing, or do more of? Impacts are behavioral changes, not features.

What (Deliverables) - The features, capabilities, or activities that could enable the desired impacts. These are the things your team builds or does. Multiple deliverables might support a single impact; multiple impacts might serve a single goal.

Example impact map

Goal: Reduce support ticket volume by 30%

Actors:

Impacts (How):

Deliverables (What):

The map shows how each deliverable connects through an impact to the goal. Features without this chain should be questioned.

Why impact mapping works

Prevents solution fixation. Teams often start with features ("we need a mobile app") without connecting to goals. Impact mapping forces the question: what impact would that create, and does that impact serve our goal?

Creates focus. The map makes explicit why each initiative exists. When resources are constrained, the map helps identify what to cut (things with weak connections to the goal) versus what to protect (things with strong connections).

Enables alternatives. When impacts are explicit, teams can generate multiple ways to create them. If one deliverable fails, others might succeed in creating the same impact.

Aligns stakeholders. The visual format creates shared understanding across roles. Product, engineering, marketing, and leadership can see how their work connects to shared objectives.

Supports measurement. Each level is measurable: Did we deliver the thing? Did it create the impact? Did the impact move the goal? This chain supports learning and adjustment.

Creating impact maps

Start with the goal. What are you trying to achieve? Be specific enough that you'll know if you've succeeded. Vague goals produce vague maps.

Identify actors. Who could influence this goal through their behavior? Think beyond obvious users to include partners, influencers, internal stakeholders, and indirect actors.

Brainstorm impacts. For each actor, what behavioral changes would contribute to the goal? Generate many possibilities before filtering.

Generate deliverables. For each impact, what could you build or do to enable that change? Multiple deliverables per impact allows for alternatives.

Prioritize. Not all paths through the map are equal. Identify which actor-impact-deliverable combinations offer the best return.

Iterate. Impact maps aren't static. As you learn-some deliverables work, some don't-update the map to reflect reality.

Impact mapping pitfalls

Goals that aren't goals. "Launch feature X" isn't a goal-it's a deliverable. Impact maps work backward from outcomes, not forward from outputs.

Missing actors. Incomplete actor identification leaves behavior change opportunities undiscovered.

Impacts that are features. "User uses new dashboard" describes feature usage, not behavioral impact. Push to genuine change: "User makes faster decisions."

Deliverables without paths. If a deliverable can't be connected through an impact to the goal, its purpose is unclear.

Map as decoration. Creating an impact map once and ignoring it defeats the purpose. The map should be a living reference, consulted during prioritization and planning.

When to use impact mapping

Impact mapping fits situations where:

For exploratory work where goals are unclear, or for routine features where the connection to value is obvious, the technique may add overhead without proportional benefit.

Tools like Klero help populate impact maps with customer insight. When you can see what impacts customers expect from requested features, the How level of the map becomes grounded in real expectations rather than assumptions.