← Back to Glossary
FrameworksI

Impact Mapping

Definition

A strategic planning technique created by Gojko Adzic that connects business goals to deliverables through a four-level map: Goal (why), Actors (who), Impacts (how behavior changes), and Deliverables (what the team builds). Impact mapping prevents teams from jumping straight to features by first clarifying whose behavior needs to change and in what way. PMs use impact maps to justify roadmap decisions and to prune ideas that do not connect to a meaningful goal.

Why It Matters for Product Managers

Understanding impact mapping is critical for product managers because it directly influences how teams prioritize work, measure progress, and deliver value to users. PMs use impact maps to justify roadmap decisions and to prune ideas that do not connect to a meaningful goal. Without a clear grasp of this concept, PMs risk making decisions based on assumptions rather than evidence, which can lead to wasted engineering effort and missed market opportunities.

How It Works in Practice

Teams typically implement this framework by following a structured process:

  • Introduce — Share the framework with the team, explaining the problem it solves and when it is most useful.
  • Calibrate — Run a practice session with a small set of real examples so the team develops a shared understanding of how to apply it.
  • Apply — Use the framework on actual backlog items, roadmap decisions, or discovery questions during a dedicated working session.
  • Review — After a cycle (sprint or quarter), evaluate whether the framework produced better outcomes and adjust how the team uses it.

    • The goal is not to follow impact mapping dogmatically but to use it as a thinking tool that brings structure to decisions that would otherwise rely on gut feel.

    Common Pitfalls

  • Applying the framework mechanically without understanding the reasoning behind each step.
  • Using the framework as a substitute for product judgment rather than as an input to decisions.
  • Skipping calibration sessions, which causes inconsistent scoring or categorization across the team.

    • Related Concepts

    To build a more complete picture, explore these related concepts: Opportunity Solution Tree, and Story Mapping. Each connects to this term and together they form a toolkit that product managers draw on daily.

    Related Terms

    OKR (Objectives and Key Results)Opportunity Solution TreeStory Mapping

    Frequently Asked Questions

    What is impact mapping in product management?+
    A strategic planning technique created by Gojko Adzic that connects business goals to deliverables through a four-level map: Goal (why), Actors (who), Impacts (how behavior changes), and Deliverables (what the team builds). Product managers use this concept to make more informed decisions and deliver better outcomes for users and the business.
    When should a PM use impact mapping?+
    Use impact mapping when you need a structured approach to make decisions that would otherwise rely on opinion or gut feel. It is especially valuable during prioritization, planning, and stakeholder alignment sessions where a shared framework brings rigor and transparency.
    ← PreviousICE ScoringNext →Initiative Roadmap

    Explore More PM Terms

    Browse our complete glossary of 100+ product management terms.

    Full GlossaryExplore Frameworks