Impact Mapping
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
Impact mapping is a strategic planning technique organized around four questions: Why, the business goal; Who, the actors who can help or hinder it; How, the behavior changes those actors would need to make; and What, the deliverables the team will build. Drawing the answers as a mind map keeps every proposed feature traceable to an expected behavioral change and an underlying goal. It is used widely in agile product planning to stop feature lists drifting away from outcomes. Key qualification: the map is only as good as the clarity of the top-level goal.
SCAFFOLDING EFFECT
Reduce cognitive load
- Filter features: require every proposed deliverable to name the behavior change it should produce. - Challenge assumptions: test whether the assumed actor behavior is plausible before building anything. - Align stakeholders: use one shared map to expose disagreements about goals and audiences.
Anchor fast decisions
Most plans fail because the link between a deliverable and a business outcome is assumed rather than stated. Writing the chain explicitly forces each assumption into the open, where it can be tested or rejected. Teams then stop measuring activity and start measuring whether the intended behavior actually changed, which shortens the distance between effort spent and value created.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- impactmapping.orghttps://www.impactmapping.org/verified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS