When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.
Product Strategy Mapping tool
Impact Mapping
Connects a goal, actors, behavior changes, and possible deliverables in a traceable impact hypothesis.
Impact Mapping is a collaborative visualization of the assumptions behind an initiative: why the goal matters, who can influence it, how behavior might change and what could support that change.
Why does the goal matter, who can influence it, how should behavior change and what could support it?
- Participants
- 3-8
- Time
- About 90–120 minutes
Connect every What branch to the Why goal through an actor and behavior impact; deliverables are options to examine.

Why
Set a measurable goal
The goal explains why the work matters and bounds the map.
Who
Identify relevant actors
Actors can create or block desired effects, or be affected by the change.
How
Describe desired behavior changes
Impacts describe how an actor’s behavior would need to change to support the goal.
What
Derive possible deliverables
Deliverables are options the organization could use to support the intended impacts.
Review behavior assumptions and options against results. Update the map when learning changes the goal, actors or impact path.
A good fit when
Use it when an initiative is accumulating feature requests and their connection to business goals or user behavior is unclear.
Ideal for
- Strategy to Roadmap
- Outcome Planning
- Initiative Scoping
Not good for
- Pure feature lists
- Detailed implementation work
Outputs

Why goal
A justified, measurable outcome as the map root.

Actor-impact paths
Actors and desired or prevented behavior changes.

What options
Possible deliverables with impact assumptions and measurement needs.
Impact map: goal, actors, impacts and options
Fictional teaching example
Fictional map for a measurable outcome. The overarching Why node is stated separately; each row represents a possible actor-impact-deliverable branch.
| Possible branch | Who · actor | How · impact | What · deliverable |
|---|---|---|---|
| Branch 1Which actor, behavior and possible support belong together? | Households with occasional repair needs. | Choose available tools confidently before traveling. (Fictional impact assumption) | Availability view or firm reservation confirmation. (Option) |
| Branch 2How could this group support or obstruct the goal? | Volunteers who manage collection and returns. | Update availability and return status promptly. (Fictional impact assumption) | Simple status process or reminder workflow. (Option) |
| Branch 3Which other group can influence the impact? | Local organizations that provide tools. | Communicate stock and opening hours reliably. (Fictional impact assumption) | Coordinated stock and opening-hours process. (Option) |
1. Who · actor
- Branch 1
- Households with occasional repair needs.
- Branch 2
- Volunteers who manage collection and returns.
- Branch 3
- Local organizations that provide tools.
2. How · impact
- Branch 1
- Choose available tools confidently before traveling. (Fictional impact assumption)
- Branch 2
- Update availability and return status promptly. (Fictional impact assumption)
- Branch 3
- Communicate stock and opening hours reliably. (Fictional impact assumption)
3. What · deliverable
- Branch 1
- Availability view or firm reservation confirmation. (Option)
- Branch 2
- Simple status process or reminder workflow. (Option)
- Branch 3
- Coordinated stock and opening-hours process. (Option)
Fictional Why goal: increase completed loans as a share of all reservation requests in the pilot area from 20% to 35% within eight weeks. The baseline, target and timeframe are invented. Rows are impact assumptions and options, not proven causality or delivery commitments.
First step
Bring business and technical perspectives together around a clear goal. Define the system boundary and available outcome signals.
Good to do first
Deep dive
It draws a line from the desired impact through actors and behavior changes to possible solutions. The connection prevents features from being evaluated in isolation and makes every measure checkable against its contribution to the goal.
Impact Mapping holds up because it brings goal, involved actors, desired behavior change, and possible measures into one causal logic. Good use seriously asks whose behavior needs to change and whether an idea plausibly contributes to that. This quickly demystifies or sharpens solution ideas, because the path from activity to impact doesn't stay foggy.
Start with a clear goal and force the discussion early onto concrete actors and observable behavior. Its quality shows in the moment when a popular idea can no longer demonstrate a plausible impact path. Close with a few credible impact paths and open assumptions still to be checked for the strongest paths.
The method guide walks execution through 4 phases, timing, 4 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Impact Mapping: WorksheetPlan the shared conversation from the goal through actors and behavior changes to possible options.markdown
impact-mapping-working-template.md
Plan the shared conversation from the goal through actors and behavior changes to possible options.
Impact Mapping: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Develop an impact map Time: About 90–120 minutes
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Wall space or digital mind-map board, cards for goal, actor, impact and deliverable, outcome signals and available evidence.
- Roles: Business and technical owners, product team, affected user or domain perspective and one facilitator.
- Advance information: Gather the Why goal and current baseline. Review available indicators, influence boundaries and ongoing initiatives.
- Overall time needed: About 90–120 minutes for a focused first mapping pass; impact measurement and delivery review happen later.
- Setup: Start with Why, then branch through Who, How and What. Keep each What proposal connected to its actor and impact.
Prepare for the work steps
Why: Set a measurable goal
- Business or product goal
- Baseline, horizon and influence where known
Who: Identify relevant actors
- Goal and system boundaries
- Customer, business and delivery perspectives
How: Describe desired behavior changes
- Actor groups
- Goal and relevant user or business evidence
What: Derive possible deliverables
- Goal, actor and impact branches
- Product, service and organizational options
Impact map: goal, actors, impacts and options
| Possible branch | Actor | Behavior change | Optional deliverable |
|---|---|---|---|
| Branch 1 | |||
| Branch 2 | |||
| Branch 3 |
- Branch 1: Which actor, behavior and possible support belong together?
- Branch 2: How could this group support or obstruct the goal?
- Branch 3: Which other group can influence the impact?
Blank worksheet: define the goal outside the table. For each branch, record the actor, desired behavior change, possible support and assumption.
Why: Set a measurable goal
Expected artifact: Goal at the center of the impact map
Why · outcome · horizon
Entry:
...
- Does the goal state an outcome rather than a solution delivery?
Who: Identify relevant actors
Expected artifact: Actor groups connected to the goal
Actor · ability to influence · affectedness
Entry:
...
- Are actors connected to the goal through their possible behavior?
How: Describe desired behavior changes
Expected artifact: Impact branches for each actor
Actor → behavior → contribution to the goal
Entry:
...
- Does each impact describe a behavior change?
- Is its connection to the goal clear?
What: Derive possible deliverables
Expected artifact: Optional deliverables for each impact
Option → impact → actor → goal
Entry:
...
- Can each deliverable be traced through an impact to the goal?
- Which assumption should be tested before delivery?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/impact-mapping/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of Impact Mapping, when you want to use User Story Mapping to order the journey from goal to MVP slice along real user flows.

Connects goals, ideas, step projects, and tasks so product planning stays outcome-oriented and adaptive.

Vision, target group, needs, value, and business goals fit onto one board that exposes assumptions for validation.

Sharpens product goal, target group needs, core features, and assumptions into a shared working picture.

Links data, insights, beliefs, and bets so strategy and product decisions become traceable and reviewable.

Formulates goals precisely enough that measure, relevance, and deadline together form a clear basis for steering.
Constraints and origin
Profile
- Method form
- Mapping tool
- Participants
- 3-8
- Time
- 45-90 min
- Maturity
- Established
- Origin
- Praxisgemeinschaft


