Before building a feature, ask: "Why are we building this?" Impact Mapping helps you work backwards from business goals to specific deliverables, ensuring every feature has a clear purpose.
Impact Mapping is a strategic planning technique that creates a visual map connecting:
It prevents building features for features' sake and keeps teams focused on outcomes.
Question: WHY are we doing this?
The business objective you're trying to achieve.
Good goals:
Bad goals:
Question: WHO can help us achieve this goal?
The people whose behavior needs to change to reach your goal.
Types of actors:
Example actors for "Increase revenue by 20%":
Question: HOW should their behavior change?
The specific behavior changes that will drive your goal.
These are not features—they're the behaviors you want to enable or encourage.
Example impacts for "Existing free users":
Question: WHAT can we build to create those impacts?
Only at this final level do you think about features.
Example deliverables for "Upgrade to paid plans":
Let's map a complete impact map for an analytics platform:
GOAL: Increase revenue by 30%
│
├─ ACTOR: Existing free users
│ │
│ ├─ IMPACT: Upgrade to paid plan
│ │ ├─ Usage limits on free tier
│ │ ├─ Premium feature teaser
│ │ └─ ROI calculator
│ │
│ └─ IMPACT: Invite team members
│ ├─ Team collaboration features
│ ├─ Referral incentive program
│ └─ Shared dashboards
│
├─ ACTOR: Trial users
│ │
│ ├─ IMPACT: Experience core value quickly
│ │ ├─ Improved onboarding flow
│ │ ├─ Sample data templates
│ │ └─ Guided tutorials
│ │
│ └─ IMPACT: Convert before trial ends
│ ├─ Trial extension offers
│ ├─ Success milestone tracking
│ └─ Conversion-moment prompts
│
└─ ACTOR: Enterprise decision-makers
│
├─ IMPACT: Trust platform for sensitive data
│ ├─ SOC 2 compliance
│ ├─ SSO integration
│ └─ Advanced security features
│
└─ IMPACT: Get executive buy-in
├─ Executive summary reports
├─ ROI dashboard
└─ Case studies library
Define your business objective clearly.
Use SMART criteria:
Brainstorm all the people who could help you achieve this goal.
Ask:
For each actor, ask: "How should their behavior change?"
Focus on:
Only now think about what to build.
For each impact, brainstorm features that could create that behavior change.
Not all paths are equally valuable. Prioritize by:
Instead of: "Let's build feature X" Try: "To help [Actor] [Impact], we'll build [Deliverable]"
Map competing initiatives to see which contributes most to your goals.
Show how proposed features connect to business objectives.
Validate assumptions about actors and impacts before building.
Every deliverable must connect to a goal through actors and impacts.
You can test different deliverables for the same impact.
Visualize which paths contribute most to your goals.
Everyone sees how their work connects to business objectives.
Makes explicit the behavioral assumptions you're making.
Don't jump straight to "We should build X." Always start with the goal.
"Use the mobile app" is a deliverable, not an impact. "Check analytics on the go" is an impact.
Keep it simple. Four levels are enough.
Impact maps should evolve as you learn. Update them regularly.
Don't focus only on end users. Include all actors who influence your goal.
vs. User Stories
vs. OKRs
vs. Roadmaps
Use them together:
Try impact mapping for your next big initiative. Start with a clear goal, identify the actors, map the impacts, and only then think about what to build.
Align engineering work with business goals using Objectives and Key Results framework
Visual framework for quick prioritization decisions based on business value and implementation complexity
Quantify and compare the value of different initiatives using Reach, Impact, Confidence, and Effort