Why This Matters - Problem Tree Analysis

Problems that are not clearly defined produce weak solutions. Getting this step right shapes everything after it.

Common Pitfalls

Vague Problem Definition

Unfocused solutions follow.

Assumption-Based Planning

You end up with solutions that miss the mark.

Weak Evidence Base

Proposals built on it are hard to trust.

Skip Community Validation

Communities don't recognize themselves in the outcome.

The Problem Analysis Journey

graph LR
    DESK["📚 PHASE 1
Desk Review
(AI-Assisted
Research)"] TREE["🌳 PHASE 2
Draft Problem
Tree with (E)
and (A) tags"] QA["✓ PHASE 3
Quality
Assurance
Checklist"] QUESTIONS["❓ PHASE 4
Convert (A) to
Stakeholder
Questions"] ENGAGE["💬 PHASE 5
Stakeholder
Engagement &
Validation
(Lesson 1.2)"] REFINE["🔄 PHASE 6
Refine Tree
with Community
Insights"] TOC["🎯 PHASE 7
Theory of
Change
(Lesson 1.4)"] DESIGN["🚀 PHASE 8
Activity Design,
Proposals,
Budgets
(Module 2)"] DESK --> TREE TREE --> QA QA --> QUESTIONS QUESTIONS --> ENGAGE ENGAGE --> REFINE REFINE --> TOC TOC --> DESIGN style DESK fill:#F59E0B,stroke:#D97706,stroke-width:2px,color:#1F2937 style TREE fill:#F59E0B,stroke:#D97706,stroke-width:2px,color:#1F2937 style QA fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff style QUESTIONS fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff style ENGAGE fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff style REFINE fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff style TOC fill:#F37324,stroke:#E05C1B,stroke-width:2px,color:#fff style DESIGN fill:#E12729,stroke:#B91C1C,stroke-width:2px,color:#fff

Ready to Learn the Method

Move to Understanding Problem Tree next to learn the framework.

Lesson 1.1: Problem Tree Analysis 27%
Step 3 of 11 · Why This Matters