Challenge Mapping

Purpose

Challenge Mapping breaks an overwhelming, ambiguous problem into a hierarchy of smaller, more manageable sub-challenges. By asking "Why?" to go broader and "How?" to go narrower, teams create a visual map that reveals where the most impactful intervention points lie and which sub-problems are already solvable.

At a glance

• Group size: 4–10
• Duration: 40 minutes
• Difficulty: Moderate
• Facilitation style: Guided collaborative analysis
• Setting: Large wall or whiteboard; digital boards work well

How to run

1. State the anchor challenge (5 min): Write the main challenge as a "How might we…" question in the centre of the wall.
2. Go broader — ask "Why?" (8 min): For the anchor challenge, ask "Why is this important?" The answers become higher-level challenges placed above.
3. Go narrower — ask "How?" (15 min): For the anchor challenge, ask "How might we address this?" Each answer becomes a sub-challenge placed below. Then break those down further with another round of "How?"
4. Identify the sweet spot (7 min): Look for sub-challenges that are narrow enough to act on but broad enough to matter. Mark 2–3 priority challenges.
5. Assign and plan (5 min): Each priority challenge gets a team or owner and a next step.

Materials needed

• Large sticky notes or cards
• Markers
• Wall space for a 3–4 level hierarchy
• Dot stickers for voting

Pitfalls & common mistakes

• Staying too high-level: If every sub-challenge still feels overwhelming, you haven’t gone narrow enough.
• Going too narrow too fast: Jumping to solutions prematurely. Keep asking "How?" at the challenge level, not the solution level.
• Linear list instead of tree: The map should branch — a flat list misses relationships.
• No prioritisation: Mapping without choosing where to focus is analysis without action.

Inclusion & accessibility

• Use large, legible writing on sticky notes.
• Read the map aloud periodically for visually impaired or remote participants.
• Let individuals brainstorm sub-challenges silently before group discussion.

Variations

• Reverse challenge mapping: Start with narrow, known problems and work upward to discover the systemic challenge.
• Challenge mapping + dot voting: After mapping, each participant gets 3 votes to place on the sub-challenge they think is most impactful.
• Digital async version: Use Miro/Mural; team members add branches over 24 hours, then reconvene to prioritise.

When NOT to use this

• When the problem is already well-defined and the team needs to ideate solutions, not refine the problem.
• When only one person has the domain knowledge — the map will reflect a single perspective.
• When the challenge is trivial and decomposition would be over-engineering.

Source & further reading

• Min Basadur — *The Power of Innovation* (Pitman, 1995)
• d.school, Stanford — "Reframe the Challenge" exercises
• Dorst, Kees — *Frame Innovation* (MIT Press, 2015)