What needs to be finished first
A concrete business goal with measurable outcome and time frame is formulated (for example "double new user activation in Q3").
A North Star metric or comparable outcome metric exists and the goal is anchored to it.
What needs to be ready before start
Whiteboard or Miro board with four columns or a tree layout (Goal, Actors, Impacts, Deliverables); stickies in four colors; template per column; voting tokens for prioritization.
One facilitator; a Product Owner with mandate for the goal; 3-6 team members from product, engineering, marketing; a scribe; ideally a stakeholder with business perspective.
Goal and measurement; existing customer-journey insights; user segments and behaviors; existing measures and their effect; constraints.
3-4 h
Four columns or tree: Why (Goal), Who (Actors), How (Impacts), What (Deliverables). Goal clearly visible at the top. Rule: do not jump to Deliverables without Actor and Impact.
The one question this method answers
Which actors must change behavior for the business goal to be reached, and which actions support that?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Phase 1: Sharpen goal | 30 min | Phrase the goal so achievement is testable (SMART). Define main metric, baseline, target, time frame. Derive initial success criteria directly from the goal. | If the goal is ambiguous, the rest of the map fails. One sentence, one number, one date. |
2Phase 2: Identify actors | 30 min | Which people or groups can influence the goal? Capture primary actors (direct leverage) and secondary actors (indirect). Keep primary actors to 5-7. | If 15 actors emerge, the map is overextended. Focus on primaries. Keep secondaries as notes, not as main tree nodes. |
3Phase 3: Impacts per actor | 45 min | For each actor, define the behavior change that produces impact on the goal. Impact is a verb, for example "registers faster" or "recommends more actively". Add 2-4 impacts per actor. | Impacts are not features. "Shortens onboarding" is output; "user activates within 5 min" is impact. Actor verb should lead. |
4Phase 4: Deliverables per impact | 60 min | List possible deliverables per impact (features, content, interventions). Include multiple options per impact and rough effort. | Multiple deliverables per impact are desirable, not one fixed plan. The map helps select options. |
5Phase 5: Prioritization and hypotheses | 30 min | Vote on impacts (highest leverage first). Select one or more deliverables per top impact with hypothesis, owner, and deadline. Keep the map as a living document. | Prioritize on impact level first, then on deliverable. Otherwise favorite features are selected before impact is validated. |
What comes out at the end
Impact map as a tree or column diagram with Goal, Actors, Impacts, Deliverables. Companion note with prioritization, hypotheses, owners, and deadlines for top deliverables.
Living document with date. Version impacts (for example new hypotheses, validated effects) whenever they change. Add outcome tracking directly at the goal node over time.
Compact working template for Impact Mapping with context, input, output artifacts, and next step.
What is this method used for?
Which question should be answered at the end?
Which data, observations, or materials are available?
Owner, date, success signal.
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Goal: Raise activation rate (first booking within 7 days) from 6.8% to 12% by 30.09.2026.
Actors and impacts
Top deliverables (prioritized)
Secondary deliverables (backlog): Workspace comparison view, trust badges, onboarding video.
Recognize symptoms and steer against them
The map includes features directly under the goal while skipping actors and impacts.
Force the sequence: Goal -> Actor -> Impact -> Deliverable. If a skip occurs, return to the previous column.
Impact is written as "build a new function".
Impact must contain an actor verb. "Delivering an onboarding feature" is not impact. "User activates in 5 minutes" is impact.
Fifteen actors absorb all energy and prevent focus.
Keep it to 5-7 actors. Vote by leverage. Keep secondary actors as attachment rather than in the main tree.
The team says "we build X" instead of "double activation rate".
Formulate the goal as outcome. If the team has no outcome goal, step back and define it before impact mapping.
All impacts and deliverables feel equally urgent, so the team tries to build everything.
Vote at impact level. Top three impacts only, others are parked or dropped.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.