The Essence of Every Mapping Technique

PUBLISHED

Jul 24, 2026

READ ON

Ways we can work together

1️⃣ Order my book: Real Progress: How to Connect the Dots of Product Strategy, OKRs, and Discovery, which readers call "a practical guide you can return to again and again."

2️⃣ Join my Workshop From Staring at KPIs to Prioritizing with OKRs, in 6 Hours, for turning generic dashboard metrics into useful goals, helping you prioritize and measure your work.

3️⃣ Join the Live Cohort of my How to Build and Execute a Winning Product Strategy course, to learn how to set up your own Strategy process that allows you to say no to things and that creates clarity and context, instead of theoretical processes.

4️⃣ Learn about my training and coaching options for product teams, with a focus on creating strategic clarity, setting pragmatic goals, and implementing real-life discovery practices to reduce risk

Dear Reader,

99% of the mapping and tree techniques product teams reach for reduce to the same three layers:

A business context layer
A problem space layer
A solution space layer.

Two questions move you between them. WHY, to move up. HOW, to move down.

Impromptu Sketch during a Discovery Workshop

That is the whole model. Everything else is a naming convention layered on top of it.

Impact Mapping's version

(Original) Impact Mapping names the layers Business Goal, Actor, Outcome, Output. The Business Goal sits in the business context layer. Actor and Outcome sit in the problem space. Output sits in the solution space. Ask WHY this Output matters, and you land on the Actor's Outcome. Ask WHY that Outcome matters, and you land on the Business Goal. Same two motions, different labels.

The Opportunity Solution Tree's version

The Opportunity Solution Tree names the layers Outcome, Opportunity, Solution, Experiment. The Outcome is business context. Opportunities live in the problem space. Solutions and Experiments live in the solution space. Ask WHY this Experiment matters, and you land on the Solution it's testing. Ask WHY that Solution matters, and you land on the Opportunity it addresses.

Metrics trees and canvases carry the same shape

A metrics tree separates a top-line metric (business context) from the metrics that diagnose it (problem space) from the levers a team can pull (solution space). Even a canvas that packs everything onto one page, like the Business Model Canvas, still separates why the business exists from who it serves and what they need from what gets built to serve it. Aakash Gupta and I talked through this on a prep call for his podcast: canvases are specific windows into a strategy, not the strategy itself. Once you understand the layers underneath, you can fill any canvas your boss hands you.

Where this actually helps

If your tree feels too wide, or your canvas feels disconnected from what the team ships, do not blame the technique. Check whether the layer above it carries enough specificity to guide what belongs below it. A vague Business Goal produces a vague Outcome, which produces an Opportunity space nobody can prioritize. The fix rarely lives in the tree. It lives one layer up.

Next time your team debates which framework to adopt, skip the debate. Ask which layer is missing and how to move towards it.

Thank you for Practicing Product,

Tim