Complete firstOutcome-oriented goal
A clear goal and at least one potential signal are named.
A feature list does not provide a shared rationale for scope.
Method guideProduct Strategy
Impact Mapping
A practical method guide: clarify prerequisites and materials, understand the complete process, and look up outputs, pitfalls, and stop criteria.
ComplexityMedium
Time45-90 min
Participants3-8
FormatWorkshop
MaturityEstablished
01
Prerequisite
What needs to be finished first
Complete firstCross-functional discussion
Business, technical and affected-user perspectives are represented.
Without varied perspectives, actors and impact assumptions remain hidden.
02
Preparation
What needs to be ready before start
Materials
Wall space or digital mind-map board, cards for goal, actor, impact and deliverable, outcome signals and available evidence.
People / roles
Business and technical owners, product team, affected user or domain perspective and one facilitator.
Pre-read
Gather the Why goal and current baseline. Review available indicators, influence boundaries and ongoing initiatives.
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.
03
Core question
The one question this method answers
Why does the goal matter, who can influence it, how should behavior change and what could support it?
04
Flow
Phases with goal, actions, output and pitfall
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.
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.
- 1
Why
Set a measurable goal
Goal
The map begins with a verifiable outcome instead of a feature list.
Inputs for this step
- Business or product goal
- Baseline, horizon and influence where known
Actions
- Phrase the goal as an outcome and measurement.
- Connect it to a baseline and time horizon when data is available.
- Mark dependencies and limits of influence.
Output
Goal at the center of the impact map
Why · outcome · horizon
Quality check
Does the goal state an outcome rather than a solution delivery?
Pitfall
The goal is an activity or feature. Clarify the outcome and why it matters to the organization.
Timing: About 15 minutes.
- 2
Who
Identify relevant actors
Goal
The map focuses on groups whose behavior can affect the goal.
Inputs for this step
- Goal and system boundaries
- Customer, business and delivery perspectives
Actions
- List people, roles, groups or systems that could contribute or obstruct.
- Include affected users and relevant stakeholders.
- Group actors by their potential influence on the goal.
Output
Actor groups connected to the goal
Actor · ability to influence · affectedness
Quality check
Are actors connected to the goal through their possible behavior?
Pitfall
A complete organization chart obscures relevant behavior groups. Define actors by their influence on the goal, not only by hierarchy.
Timing: About 20 minutes.
- 3
How
Describe desired behavior changes
Goal
Each impact path is visible as a hypothesis that can be examined.
Inputs for this step
- Actor groups
- Goal and relevant user or business evidence
Actions
- For each actor, phrase desired or prevented behavior.
- Connect behavior changes to the outcome logic and evidence.
- Mark unsupported behavior assumptions clearly.
Output
Impact branches for each actor
Actor → behavior → contribution to the goal
Quality check
Does each impact describe a behavior change? Is its connection to the goal clear?
Pitfall
An impact is phrased as a delivered feature. Translate the feature idea into the behavior change it is meant to support.
Timing: About 25 minutes.
- 4
What
Derive possible deliverables
Goal
Scope is discussed in relation to intended impact, not as a wish list.
Inputs for this step
- Goal, actor and impact branches
- Product, service and organizational options
Actions
- List possible product, process, service or communication contributions.
- Connect each proposal to its impact and actor.
- Keep options high-level and connect them to learning needs.
Output
Optional deliverables for each impact
Option → impact → actor → goal
Quality check
Can each deliverable be traced through an impact to the goal? Which assumption should be tested before delivery?
Pitfall
Deliverables are treated as committed scope. Mark them as options and measure impact after implementation.
Timing: About 20 minutes.
05
Artifact
What comes out at the end
Sketch: what the artifact looks like
Form
A versioned impact map with goal, actors, behavior impacts, possible deliverables, assumptions, signals and later results.
Versioning / ownership
Record the goal, date and participants. Version changes to impact paths, assumptions and outcome signals; do not treat delivered items as proof of impact.
Tool alternatives
- Digital mind-map or whiteboard tool
- Cards grouped by Why / Who / How / What
- Measurement and research notes with source links
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
06
Example output
Concrete filled scenario, fictional example
Fictional example for orientation. Counts and timings describe this case and are not universal requirements.
impact-mapping-beispiel.md
Concrete filled scenario, fictional example
Fictional teaching example: Tool lending
All goals, impact assumptions and deliverables are invented; no causal evidence is available.
Why (fictional): 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.
Who: Households that need a tool; tool-library volunteers.
How: Households can assess availability in advance; volunteers update status promptly. These are behavior assumptions to test.
What options: Reservation confirmation; simple status workflow. Both remain options.
Next step: Examine whether availability uncertainty affects loan completion. The map is an impact model, not proof of causality.
07
Pitfalls
Recognize symptoms and steer against them
Quick overview, the full text is in the matching phase in the flow
- Set a measurable goalThe goal is an activity or feature.View in phase
- Identify relevant actorsA complete organization chart obscures relevant behavior groups.View in phase
- Describe desired behavior changesAn impact is phrased as a delivered feature.View in phase
- Derive possible deliverablesDeliverables are treated as committed scope.View in phase
Trap
Set a measurable goal
Symptom
The goal is an activity or feature.
What to do
Clarify the outcome and why it matters to the organization.
Trap
Identify relevant actors
Symptom
A complete organization chart obscures relevant behavior groups.
What to do
Define actors by their influence on the goal, not only by hierarchy.
Trap
Describe desired behavior changes
Symptom
An impact is phrased as a delivered feature.
What to do
Translate the feature idea into the behavior change it is meant to support.
Trap
Derive possible deliverables
Symptom
Deliverables are treated as committed scope.
What to do
Mark them as options and measure impact after implementation.
08
Stop criteria
When to pause, resolve prerequisites, or choose another approach
The goal cannot be described as an outcome: clarify the goal and baseline.
An impact describes only a feature: add the actor and behavior change.
What branches lack a clear Who/How path: remove the option or justify the connection.
Impact is claimed after delivery without measurement: plan an outcome review with appropriate evidence.
Finished the method guide?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.