Impact Mapping
Link every feature to a business goal in 4 levels: Why, Who, How, What. Gojko Adzic's visual strategic planning method.
Description
Impact Mapping is a visual strategic planning method created by Gojko Adzic in 2012 that structures product thinking across four levels (Why, Who, How, What) to link every feature to a measurable business objective. Its purpose: transform a "shopping list" roadmap into a strategic map where every initiative is traceable back to an expected outcome. Your roadmaps probably look like a succession of disconnected features. When a stakeholder asks "Why are we building this?", the best answer you can find is "It's on the Q2 roadmap." But why is it on the Q2 roadmap? Awkward silence. It is like driving with a GPS that shows streets but not the destination. Gojko Adzic, an agile software delivery consultant and Jolt Award winner for his book Specification by Example, created Impact Mapping by combining three disciplines: user interaction design, outcome-driven planning (inspired by the Swedish agency InUse), and mind mapping. The exercise consists of drawing a mind map in a tree structure with four levels. At the center, the WHY: a measurable business goal ("increase conversion rate from 12% to 18%"). Then the WHO: the actors whose behavior can influence that goal (users, internal teams, partners). Next, the HOW: the expected behavioral changes in those actors. Finally, the WHAT: the concrete features or actions to trigger those changes. Each branch of the impact map becomes an explicit, testable hypothesis. If a deliverable does not contribute to any behavioral change in any actor, it has no place in your backlog. The result: you eliminate "nice-to-have" features that serve no objective, and you get a strategic communication tool you can present to the C-level in 5 minutes instead of 30 slides.
Objectives
- Prioritize features
- Define the vision
- Ensure strategic alignment
Used by
- -uSwitch (primary case study documented by Gojko Adzic in his book Impact Mapping)
- -Spotify (uses Impact Mapping to align squads with quarterly objectives)
- -BBC (adopted to prioritize features for digital platforms)
Advantages
- Eliminates unnecessary scope. Reveals features that contribute to no measurable objective. Expect to cut 30-50% of the backlog.
- Immediate strategic alignment. The entire team understands the link between their work and business objectives by looking at the map.
- Facilitates pivots. If a hypothesis fails (an actor does not change behavior), cut the entire branch without guilt.
- C-level communication tool. Present your roadmap in 5 minutes via the map instead of 30 PowerPoint slides.
Limitations
- Does not replace discovery. The impact map structures hypotheses, but you still need to test them with users.
- Requires clear business objectives. If your CEO cannot articulate the objective, the map will be blurry. Clarify upstream.
- Risk of overly complex maps. Beyond 3-4 actors and 10-15 impacts, the map becomes unreadable. Segment.
- Requires initial investment. Count 2-4 hours of workshop to create the first map, but the time is recovered afterward.
How to apply Impact Mapping
- 1
Prepare the impact mapping workshop
Block 2-4 hours. Invite PM, 1-2 tech leads, 1 designer, 1-2 business stakeholders (marketing, sales, or CEO). Prepare a visual support: whiteboard, Miro, or Mural. Send a one-pager explanation 24 hours in advance to avoid confusion. Output: room booked, participants confirmed, mapping tool ready.
- 2
WHY: Define a measurable business objective (center of the map)
Ask the question: "What is the business objective this product must achieve in the next 3-6 months?" Demand metrics, not vague intentions: "Increase conversion rate from 12% to 18%," not "improve the experience." Place this objective at the center of your impact map. If you have multiple objectives, create multiple maps or prioritize a single objective for this session. Output: 1 SMART objective at the center of the map.
- 3
WHO: Identify the actors who influence the objective
Brainstorm: "Who can help or prevent achieving this objective?" List user segments, internal stakeholders, partners, and even potential blockers. Examples: "free users", "sales team", "API partners", "new visitors". Draw each actor as a branch extending from the center. Aim for 3-7 actors max to keep the map readable. Output: 3-7 actors drawn around the central objective.
- 4
HOW: Define the expected impacts on each actor
For each actor, ask: "How must their behavior change for us to reach the objective?" Examples: "Free users must upgrade to the paid plan," "The sales team must reduce the sales cycle from 30 to 20 days." Each impact is a hypothesis, not a fact. Draw these impacts as sub-branches of each actor. Output: 2-5 impacts per actor.
- 5
WHAT: List features and actions to generate these impacts
For each impact, brainstorm: "What features or actions could trigger this behavior change?" Examples: "Add a comparative onboarding free vs. paid", "Create an ROI dashboard for sales". Do not filter yet, list all ideas. Output: 3-10 potential features per impact, the complete map.
- 6
Prioritize branches by dot voting
Each participant votes for the 3 branches (actor to impact to feature) they consider most critical. The most-voted branches become your priority roadmap. Cut ruthlessly the low-scoring branches. If the goal is achieved after the first deliverable, you can stop work on that branch. Output: 2-4 critical paths identified and visually marked.
- 7
Transform priority paths into user stories and metrics
For each priority path, break down the features into developable user stories. Define validation criteria: "How will we know this impact has occurred?" Example: if impact = "free users upgrade", metric = free-to-paid conversion rate goes from X% to Y%. Output: user story backlog with impact metrics dashboard.
- 8
Iterate the map after each sprint
Every 2-4 sprints, revisit your impact map as a team: which hypotheses were validated? Which ones failed? Cut dead branches (impact not achieved despite the delivered feature). Add new branches if new actors or opportunities emerge. The impact map is a living document, not a static artifact. Output: updated map reflecting the field reality.