PM Gym

Impact Mapping

Connect what you build to why it matters

Teams waste months shipping features nobody needs. Impact mapping is a simple visual method that prevents this: it forces every feature to trace back — through real people and real behavior changes — to a business goal.

Step-by-step lessons

Master Impact Mapping

Four short lessons on the four-pillar chain that keeps product teams from building the wrong things.

1

The Four Pillars

The core rule of impact mapping: never ask "what should we build?" until you know whose behavior needs to change. The map is a chain with four links, always in this order:

Everyday example — deciding to get fit

Say your goal is "lose 5kg by summer" (the Why). Who can actually make that happen? Only you (the Who / actor). What do you need to do differently? Eat less sugar and walk daily (the How / impact — a real behavior change). And only then: what tools help you do that? A step-tracker, meal-prep boxes (the What / deliverable). Notice you'd never start by buying gadgets — that's backwards. Impact mapping keeps the same order for products: goal first, gadgets last.

Why

Goal

The business metric you need to move.

Who

Actors

The people who can make the goal succeed or fail.

How

Impact

The behavior change you want to see in those people.

What

Deliverable

The feature or tool you actually ship.

Quick check

You work at Spotify and want to drive subscription growth. What role does a "Share lyrics to Instagram" feature play in the map, and what is its impact?

2

Setting the Goal (the "Why")

A common beginner mistake is starting with a build goal ("launch a dashboard"). A strong goal is a SMART business outcome — Specific, Measurable, Achievable, Relevant, and Time-bound.

Everyday example — New Year's resolutions

"Get fit this year" is the resolution everyone quits by February — it's vague, has no number, and no deadline, so you can never tell if you're winning. "Run a 5k without stopping by June 1st" is the one people actually keep: it's SMART — specific, measurable, and time-bound. Product goals fail the same way. "Improve the product" is a wish; "reduce cart abandonment from 60% to 45% by end of Q3" is a goal you can build toward and check.

How to write a good goal

Start with an active verb, target a number you can measure, and give it a deadline.

"Reduce cart abandonment from 60% to 45% by the end of Q3."

Quick check

Which of these is a real goal, rather than a feature request in disguise?

3

Actors and Impacts (the "Who" and "How")

With the goal set, work out who can influence it (actors) and how their behavior needs to shift (impacts).

Everyday example — throwing a party

Your goal: "a packed, fun party." Who makes that happen? Your friends (the actors). What do they need to do differently? RSVP yes, actually show up, and bring friends — those are the impacts (real changes in behavior). Sending a nice invite is a deliverable, not an impact — it's just a tool to trigger the RSVP. Beginners constantly mix these up: "made a beautiful invite" feels like progress, but if nobody shows up, the impact never happened. Always ask: what must people actually do, not what did we make?

Actors — the "who"

Never just "the user." Think in specific segments (first-time guest buyers) and secondary players (delivery drivers, support agents).

Impacts — the "how"

A genuine change in what people do — doing something more, less, or differently. Not a click; a habit.

Quick check

The actor is a delivery partner and we want food delivered faster. Which of these is a true impact (behavior change) rather than a feature?

4

Aligning Deliverables (the "What")

Only after mapping the desired behavior changes do you brainstorm features. Deliverables are the software, systems, or content you ship to trigger those changes.

Everyday example — the grocery list

Shopping with a list tied to the meals you're cooking, you buy only what traces back to a dinner. Shopping while hungry with no list, you grab a cart full of snacks that connect to no meal — and half of it rots. Unmapped features are those impulse snacks: they look appealing in the aisle but serve no goal. The impact map is your shopping list. When a stakeholder tosses "let's add an AI chat companion!" in the cart, you kindly trace it back: which behavior change, for which actor, toward which goal? If the line breaks, it's an impulse buy — leave it on the shelf.

The alignment guard

When a stakeholder requests an arbitrary feature ("let's add an AI chat companion!"), trace it backwards: does it trigger a behavior change that serves the goal?

If the trace breaks anywhere, the feature is probably waste — say so, kindly, with the map.

Quick check

Goal: grow active fitness-app users 20%. Actor: casual joggers. Impact: they log runs daily. Which deliverable is tightly aligned with that impact?

Review the concepts

Impact Mapping Flashcards

Six cards covering the pillars, common mistakes, and thinking tools. Click to flip.

Mindset Card 1 of 6

The Golden Rule of Impact Mapping

Click to flip

Tip: say the answer out loud before flipping.

Explanation

In practice

1 / 6
Apply what you learned

Practice Scenarios

15 realistic mapping situations. Pick the answer that keeps the goal → actor → impact → deliverable chain intact, then read why the others break it.

Scenario 1

An executive asks you to lead an initiative: grow premium subscriptions by 15% this quarter. The team immediately starts pitching feature ideas.

Where should the impact map start?

Scenario 2

Uber wants to cut driver churn by 10%. Your team drafts the map and needs to fill in the Impact column for the actor 'part-time commuter drivers'.

Which entry is a genuine impact?

Scenario 3

Duolingo's goal is +20% daily active users. A senior stakeholder insists on building a multiplayer gaming lounge and wants your support.

How do you evaluate the request with the impact map?

Scenario 4

A teammate writes the goal as: "Launch the new mobile app by Q2."

Why isn't this a valid impact-map goal?

Scenario 5

Goal: reduce support ticket volume by 30%. A PM lists only "end customers" as the actor.

What's missing in the actor thinking?

Scenario 6

In the Impact column, a team writes: "Users click the new 'Invite' button."

Why is this a weak impact?

Scenario 7

Your map has: Goal (grow retention 15%) → Actor (power users) → Impact (they invite colleagues) → Deliverable (a company-wide rebranding project).

What's broken?

Scenario 8

Leadership hands you a strategy where the map has ten actors, each with three impacts, each with several deliverables — 60+ features. Everything is "priority."

How does impact mapping help you prioritize?

Scenario 9

A stakeholder is adamant: "Just trust me, the AI companion feature will be huge. We don't need to map it."

What's the diplomatic impact-mapping response?

Scenario 10

Two deliverables both trace cleanly to the goal. One is a small notification tweak (2 days); the other is a full loyalty-program build (3 months). Both target the same impact.

How should the map inform your choice?

Scenario 11

Three months into building the deliverables on your map, data shows the target impact isn't moving the goal at all — the behavior changed, but retention didn't budge.

What does this reveal about the map?

Scenario 12

Goal: increase marketplace transactions. A junior PM maps only buyers as actors, forgetting sellers entirely.

What's the risk of this omission?

Scenario 13

Someone proposes the impact: "Make users happy."

Why is this a poor impact entry?

Scenario 14

Your finished impact map is beautiful, but a stakeholder asks: "How do we know these behavior changes will actually happen if we ship the deliverables?"

What's the honest answer about what a map is?

Scenario 15

A PM builds the entire map alone at their desk, then presents the finished version to engineering and design as final.

What's the process flaw?

Lock it in

Guess the Term

Read the clues and name the concept. The fewer clues you need, the more points you score.

Round 1 Score 0
Keep it handy

Impact Mapping Quick Reference

The whole framework on one screen — perfect for a two-minute refresher.

The Four-Pillar Chain

Every product plan should trace an unbroken line from why (goal) to what (deliverable).

1. Why

Goal

Measurable business metric. "Grow retention by 10%."

2. Who

Actor

The people with leverage. "Casual free listeners."

3. How

Impact

Visible behavior change. "Posting lyrics to stories."

4. What

Deliverable

Features you ship. "A lyric export button."

Common Traps

Three mistakes almost everyone makes at first — and how to avoid them.

1

Jumping to features

Asked "how would you improve X?" — anchor on a measurable goal first, then find the actors. Features come last.

2

Confusing clicks with impacts

An impact is never "users click the button." It's the change in habit or frequency the button causes.

3

Accepting unmapped features

Use the map to prioritize the backlog — if a request doesn't trace back to the goal, challenge it.

How to Run It

A map is a workshop and a hypothesis, not a solo artifact.

Build it together

Do it with eng, design, and stakeholders — better ideas, feasibility checks, buy-in.

It's a menu, not a mandate

A big map is options. Fund the highest-leverage branch first, then reassess.

Every link is an assumption

Test the riskiest impact→goal link cheaply; update the map as evidence lands.

Cheapest deliverable first

If two features hit the same impact, ship the cheaper one and learn.

Don't Forget Secondary Actors

The goal is rarely moved by the obvious user alone.

Primary user

The obvious one — but map their specific segments, not just "the user."

The other side

In marketplaces, sellers matter as much as buyers — both make a transaction.

Internal actors

Support agents, sales reps, moderators, engineers can all move a goal.

Notification