Impact Mapping
Connect deliverables to business goals visually
Impact Mapping is a lightweight strategic planning technique that creates a mind-map-like visual connecting business goals to the actors who can influence them, the impacts those actors must make, and the deliverables that enable those impacts. It prevents teams from building features that don't connect to business outcomes by forcing explicit tracing from deliverable to goal.
Developed by Gojko Adzic, documented in his book 'Impact Mapping: Making a Big Impact with Software Products and Projects' (2012).
Use Impact Mapping when
- ✓Quarterly or programme-level planning where you need to connect the roadmap to business goals
- ✓Stakeholder alignment sessions where scope is being debated without clarity on the underlying goal
- ✓Teams prone to building features without clear connections to measurable business outcomes
- ✓Discovery workshops to identify who needs to change behaviour for the goal to be achieved
Avoid it when
- ✗Execution-mode teams in the middle of a sprint — impact mapping is a planning tool, not a delivery tool
- ✗Highly technical infrastructure work where the business impact is indirect and hard to trace
- ✗Daily backlog management — too heavyweight for task-level prioritisation
Key Concepts
The business goal the team is trying to achieve. Written as a specific, measurable, time-bound outcome at the centre of the map.
The second level: who can help or hinder achieving the goal? Includes customers, partners, internal teams, and even the team's own developers.
The third level: what behaviour change must each actor make? What's the impact on the actor that would move the goal?
The fourth level: what product changes, features, or services would enable or trigger each impact?
Impact Mapping is fundamentally about changing behaviour — not building features. If a feature doesn't change behaviour, it doesn't belong on the map.
Each branch of the map is an assumption: if we deliver X to actor Y, it will cause impact Z, which contributes to goal G. Testing the riskiest assumptions first is the key to de-risking the plan.
How it works
Agree on a specific, measurable business goal. Write it as a metric target with a deadline.
Who can help or hinder the goal? List every stakeholder, user segment, and internal team.
For each actor, what behaviour change is needed? What would they do differently if the goal is to be achieved?
For each impact, what could the product team deliver to enable it? Multiple deliverables per impact is normal.
Select the deliverables that address the most impactful assumptions. Use MoSCoW or cost-of-delay to prioritise.
Tools that support Impact Mapping
Industry standard for software development teams — most PMs will encounter Jira in their career
Exceptionally intuitive and visually clean interface — one of the lowest onboarding friction tools for non-technical teams
Highly visual and intuitive interface with color-coded boards — one of the easiest PM tools for non-technical teams to adopt
All-in-one platform replacing multiple tools — docs, whiteboards, goals, time tracking, chat, and project management in a single workspace
Unmatched flexibility as an all-in-one workspace — combines docs, wikis, databases, and project management in a single tool
Spreadsheet-familiar interface makes adoption easy for teams transitioning from Excel — minimal training needed for basic use
Extremely intuitive drag-and-drop Kanban interface — virtually zero learning curve, new users productive within minutes
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders
Frequently Asked Questions
A focused impact mapping session for a single goal takes 2–4 hours with the right participants (PM, engineering lead, key stakeholder). The output is a map that can be photographed and turned into a prioritised backlog in the same session.
User story mapping structures the user's journey and slices releases. Impact mapping connects deliverables to business goals through behaviour change. They serve different purposes: impact mapping is strategic (should we build this?); user story mapping is tactical (how do we build and sequence this?).
They're complementary. OKRs set the goals and key results. Impact mapping provides a visual technique to plan which deliverables will achieve the key results. Use OKRs for alignment and accountability; use impact mapping for planning sessions.