Impact Mapping: Connecting Deliverables to Business Outcomes

Impact Mapping is a technique created by Gojko Adzic that answers a fundamental question: “Why are we building this?”

The Impact Map Structure

Answer 4 questions in order:

1. Why? (Business Goal)

“Increase revenue by 20% next quarter.”

2. Who? (Actors)

Who can help or hinder this goal?

• New customers
• Existing customers
• Sales team

3. How? (Impacts)

How can each actor contribute?

• New customers: sign up more easily
• Existing customers: buy more frequently
• Sales team: close bigger deals

4. What? (Deliverables)

What can we deliver to create these impacts?

• Social login (reduces signup friction)
• Personalized recommendations (increases purchase frequency)
• Analytics dashboard for sales (closes bigger deals)

Visual Impact Map

Why: Increase revenue by 20%
├── Who: New customers
│   └── Impact: Easier signup
│       └── Deliverables: Social login, One-click signup
├── Who: Existing customers
│   └── Impact: More frequent purchases
│       └── Deliverables: Recommendations, Discount coupons
└── Who: Sales team
    └── Impact: Bigger deals
        └── Deliverables: Analytics dashboard, Automated proposals

Impact Map + Estimates

Impact Mapping makes estimates more valuable:

“Social login: 8 points. Social login → +15% new customer signups → $50K/month in additional revenue.”

Now we know that 8 points generate $50K. Compare with:

“Analytics dashboard: 21 points → +10% deal size → $30K/month.”

Social login is more efficient per point invested.

Prioritizing with Impact Map

ROI per Point

Feature	Estimated Impact	Points	ROI/Point
Social login	+$50K/month	8	$6.25K/point
Coupons	+$20K/month	5	$4K/point
Dashboard	+$30K/month	21	$1.4K/point
Recommendations	+$40K/month	13	$3K/point

Prioritize: Social login > Coupons > Recommendations > Dashboard

When to Use Impact Map

• Quarterly planning — align deliverables to objectives
• Prioritization workshop — with PO and stakeholders
• Product kickoff — define initial roadmap
• Portfolio review — justify or cancel initiatives

Anti-Patterns

Generic Map

Goal: “Improve the product.” — that’s not a goal. It must be measurable.

Deliverables Without Impact

“Refactor the database” → not connected to any actor or impact. It shouldn’t be on the map (or it should be tied to an efficiency impact).

Too Many Actors

If you have 15 actors, the map is too big. Group them by categories.

Conclusion

Impact Map connects technical work to business outcomes in a visual and transparent way. Teams that know why they are building something estimate better, prioritize smarter, and deliver with more purpose.