Quick answer
Impact mapping is a planning technique that links a goal to the people who can affect it, the behavior changes you need from them and the deliverables that could cause those changes. Four layers (why, who, how, what) make every feature justify itself against the goal.
What the four layers ask
An impact map is drawn from the centre outwards, and each layer answers one question. The goal sits in the middle, the actors branch off it, the behavior changes branch off the actors, and the deliverables come last. Gojko Adžić, who introduced the technique in his 2012 book, describes the four layers as goal, actors, impacts and deliverables.
| Layer | Question | What goes in it | Example (sample data) |
|---|---|---|---|
| Why (goal) | Why are we doing this? | One measurable outcome with a number and a date | Raise free-to-paid conversion from 4.0% to 6.0% of new sign-ups within 6 months |
| Who (actors) | Who can produce or block that outcome? | Groups of people, not job titles or "the market" | New free users; team admins |
| How (impacts) | How should their behavior change? | A change in what the actor does, in the actor's own terms | New users create a first project on day 1; admins invite teammates in week 1 |
| What (deliverables) | What can we build or run to cause that change? | Features, content, campaigns, process changes | Onboarding checklist; "invite a teammate" prompt; template gallery |
The word that matters is impact. An impact is not a feature and not a result for the business. It is a change in behavior that you could, in principle, watch happen in your data. That is also why the technique pairs well with analytics: every second-layer branch is a sentence you can turn into an event and a rate.
Why impact mapping cuts features, not just organises them
The map records the reasoning behind each deliverable. Adžić's guidance is to link every deliverable to the impact it supports, compare deliverables against each other, and remove those that do not contribute to a critical impact. Without that link, a requirements list is a shopping list with no justification.
A practical way to run that check is three questions per deliverable:
- Which impact does it serve? If you cannot point at a branch, it is off the map.
- Which actor changes their behavior because of it? "Everyone" means nobody in particular.
- How would we see the change? If no event or rate would move, you cannot learn whether it worked.
A deliverable that fails question 1 is a candidate for deletion. One that fails question 3 can stay only if you add the measurement first. In the example below, dark mode was on the backlog and fails the first test: no branch of the map needs it, so it stays off the map until a goal that needs it exists.
A worked map: from a conversion goal to numbers
Sample data: a SaaS product gets 5,000 new free sign-ups a month and converts 4.0% of them to paid, about 200 accounts. The goal is 6.0% (300 accounts) within six months.
| Impact (actor + behavior) | Metric | Today | Target | Deliverables mapped to it |
|---|---|---|---|---|
| New free users create a first project on day 1 | Day-1 activation rate | 38% | 50% | Onboarding checklist, template gallery |
| Team admins invite a teammate in week 1 | Share of sign-ups where an admin invites someone within 7 days | 22% | 35% | "Invite a teammate" prompt after the first project |
| (no impact) | none | n/a | n/a | Dark mode: not on the map, cut |
To see whether the map is plausible, put the first impact through the goal. Assume that activated users pay at 9.0% and users who never activate pay at 0.9% (sample rates):
- Today: 5,000 × 38% = 1,900 activated users; 1,900 × 9.0% = 171 paying. The 3,100 who never activate add 3,100 × 0.9% = 27.9. Total 198.9, which is 3.98% of 5,000, the starting 4.0%.
- With 50% activation: 2,500 × 9.0% = 225, plus 2,500 × 0.9% = 22.5. Total 247.5, which is 4.95%.
Activation alone gets to 247.5 accounts, 52.5 short of the 300 the goal needs. The second impact therefore has to carry that gap, and you can already ask whether raising the invite share from 22% to 35% could plausibly be worth 52 accounts. If not, the map needs another actor or impact before anyone builds anything. That check, done on a whiteboard in minutes, is what the technique is for.
How to give each impact a metric you can recompute
An impact is only useful if you can measure it. Use the same four-part shape for each one:
| Part | Rule | Example |
|---|---|---|
| Actor | A group you can select in data | Users whose first visit was in the last 7 days |
| Action | One named event, not "engaged" | project_created |
| Window | Relative to the actor's start, not a calendar month | Within 24 hours of sign-up |
| Rate | Actors who did it ÷ actors in the group | 1,900 ÷ 5,000 = 38% |
Write the baseline before you build. A target without today's number cannot be judged later, and a baseline measured after the launch is contaminated by the launch.
Two further rules keep the metrics honest. First, measure the impact, not the deliverable: "checklist viewed" tells you the checklist loaded, while "project created within 24 hours" tells you behavior changed. Second, keep a goal-level number at the centre (here, paid conversion) so the impacts cannot all improve while the goal does not. If activation reaches 50% and conversion stays at 4%, the map was wrong about the link, which is exactly what you want to learn early.
Impact map, story map, opportunity solution tree
The three are often confused because all of them are tree-like and all are used in product discovery.
| Tool | Starts from | Branches into | Best used to |
|---|---|---|---|
| Impact map | A business goal | Actors, behavior changes, deliverables | Decide what is in scope and what to cut |
| Story map | A user's journey | Steps and the stories under each step | Plan the order of delivery |
| Opportunity solution tree | A desired outcome | Customer opportunities, solutions, experiments | Choose which customer problem to explore next |
An impact map is the most goal-first of the three. For the discovery-side alternative, see opportunity solution tree. The testable claim behind each branch, "if we do this, this group will do that", is a product hypothesis.
Common mistakes
- A feature list drawn as a tree. If the second layer contains "dashboard" or "onboarding flow", those are deliverables. Impacts are verbs about people: "create", "invite", "return".
- A goal without a number. "Grow the business" cannot be checked. Use a metric, a baseline, a target and a date, as in the 4.0% to 6.0% example.
- Actors that are too broad. "Users" hides the fact that new users and long-time admins behave differently. If two groups would respond to different deliverables, they are two actors.
- Mapping only helpful actors. The technique also asks who could block the outcome. A procurement team or an internal sceptic is an actor with an impact (for instance, "delay sign-off") that you may need a deliverable for.
- Drawing it once. The map records assumptions. When the data contradicts one, redraw that branch. A map nobody revisits is documentation, not a decision tool.
- Treating the map as a plan. It decides what to consider; delivery order is a separate step. For where this fits in the wider planning picture, see product strategy framework.
Impact mapping in TapCub
TapCub does not draw maps; draw yours on a whiteboard or in any mind-mapping tool. TapCub measures whether the second layer of the map, the behavior changes, actually happens. Using the example above:
- Write the impacts down as events. In All-platform analytics › Data › Tracking plan, add
project_createdandteammate_invitedwith an owner and a status, so the team agrees what will be counted before it is built. Use the real-time validation (last 24 hours) after release to confirm each event arrives with its required properties. - Measure the baseline. In All-platform analytics › Behavior › Behavior analysis, build a funnel from sign-up to
project_createdwith a 24-hour window, and read the step rate (the 38% in the example). Do this before the deliverable ships. - Define the actor as a segment. In All-platform analytics › Users › Segments & tags, create a rule segment such as "first seen in the last 7 days and did
project_created", so the same actors can be reused across funnels and retention. - Check the goal metric next to it. Keep the goal event (a purchase or upgrade) in the same funnel or goal view, so you can see whether activation rises and conversion follows.
- Know the limit. TapCub shows that behavior changed after a release and for which group; it does not run experiments or assign users to variants, so a before and after comparison does not by itself prove the deliverable caused the change.
Related: north star metric for choosing the number at the centre, and metric tree for breaking it into inputs.
Sources
- Adžić, G. Impact Mapping: Making a Big Impact with Software Products and Projects (2012), book site.
- Adžić, G. Impact mapping: drawing a map, the four questions (why, who, how, what) and the guidance on removing deliverables.
Was this explanation clear?
We use your answers to fix and expand this page.
Couldn’t send. Please try again in a minute.
Thanks for the feedback. We’ll use it to improve this page.You’ve already sent feedback on this page. Thanks.

Customer Experience Consultant
Writes about live chat, visitor conversations, and self-service, sharing practical ways to make customer communication clearer and more effective.