What is Impact Mapping?
Impact mapping was created by Gojko Adzic as a lightweight strategic planning technique. It produces a visual map with four levels: Goal, Actors, Impacts, and Deliverables.
The goal is the business objective you want to achieve (e.g., "increase monthly active users by 20%"). Actors are the people who can help or hinder that goal (e.g., new users, existing users, churned users). Impacts describe how each actor's behavior needs to change. Deliverables are the features or activities that could create those behavior changes.
The map reads left to right as a hypothesis: "We believe that building [deliverable] will cause [actor] to [impact], which will contribute to [goal]." This makes the assumptions behind every feature explicit and testable.
Why It Matters for Product Teams
Most product teams have more ideas than capacity. Impact mapping helps you focus on the ideas that connect to business outcomes. If a feature does not trace back to a goal through a clear chain of logic, it probably should not be a priority.
Impact mapping also helps teams avoid the "feature factory" trap. Instead of measuring success by the number of features shipped, you measure whether the expected impact actually occurred. This shifts the team's focus from output to outcome.
Customer feedback enriches impact maps. User requests and complaints reveal which impacts are most important. If your feedback shows that users are churning because of a specific workflow gap, that impact gets prioritized on the map.
How to Apply Impact Mapping
Start with a clear, measurable goal. Avoid vague goals like "improve the product." Use specific metrics like "reduce time-to-first-value for new users to under 5 minutes."
Identify your actors by reviewing your user base and feedback data. Who are the people whose behavior you need to change? Use your feedback tool to see which user segments submit the most requests or report the most issues.
For each actor, brainstorm the impacts: what behavior change would move you toward the goal? Then identify deliverables that could create each impact. Each deliverable should be the smallest thing you could build to test whether the impact occurs.
Revisit the map regularly. After shipping a deliverable, check whether the expected impact materialized. If not, adjust. Impact maps are living documents, not project plans set in stone.