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

flowchart TB
    subgraph Row1["Lesson 1.1: Problem Analysis"]
        direction LR
        DESK["Desk Review
AI-assisted research"]
        TREE["Draft Problem Tree
Evidence and assumptions"]
        QA["Quality Assurance
Check research rigor"]
        QUESTIONS["Stakeholder Questions
Convert assumptions"]
        DESK --> TREE --> QA --> QUESTIONS
    end

    subgraph Row2["What Comes Next"]
        direction LR
        ENGAGE["Stakeholder Engagement
Lesson 1.2"]
        REFINE["Refine Tree
Community insights"]
        TOC["Theory of Change
Lesson 1.4"]
        DESIGN["Implementation Design
Module 2"]
        ENGAGE --> REFINE --> TOC --> DESIGN
    end

    Row1 -.-> Row2

    classDef problem fill:#D1FAE5,stroke:#059669,color:#111827,stroke-width:2px
    classDef next fill:#FED7AA,stroke:#EA580C,color:#111827,stroke-width:2px
    class DESK,TREE,QA,QUESTIONS problem
    class ENGAGE,REFINE,TOC,DESIGN next
    linkStyle 0,1,2 stroke:#059669,stroke-width:2px
    linkStyle 3,4,5 stroke:#EA580C,stroke-width:2px
    linkStyle 6 stroke:#6B7280,stroke-width:2px,stroke-dasharray: 4 4