Understanding the Problem Tree | Setup Your Project for Success

The Basic Framework

graph TB
    %% EFFECTS (Branches) - What happens because the problem exists
    E1["🌿 EFFECT 1<br/>Immediate Impact"]
    E2["🌿 EFFECT 2<br/>Medium-term Impact"]
    E3["🌿 EFFECT 3<br/>Long-term Impact"]

    %% CORE PROBLEM (Trunk) - The central issue
    CP["🌳 CORE PROBLEM<br/>The central issue your<br/>project will address"]

    %% ROOT CAUSES (Roots) - Why the problem exists
    RC1["🌱 ROOT CAUSE 1<br/>Direct Cause"]
    RC2["🌱 ROOT CAUSE 2<br/>Direct Cause"]
    RC3["🌱 ROOT CAUSE 3<br/>Direct Cause"]

    %% Underlying causes (deeper roots)
    UC1["🌱 Underlying<br/>Cause 1.1"]
    UC2["🌱 Underlying<br/>Cause 1.2"]
    UC3["🌱 Underlying<br/>Cause 2.1"]
    UC4["🌱 Underlying<br/>Cause 3.1"]

    %% Define relationships - Bottom to Top (Roots → Trunk → Branches)
    UC1 --> RC1
    UC2 --> RC1
    UC3 --> RC2
    UC4 --> RC3

    RC1 --> CP
    RC2 --> CP
    RC3 --> CP

    CP --> E1
    CP --> E2
    CP --> E3

    %% Festa Design System Colors
    style CP fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff
    style RC1 fill:#F59E0B,stroke:#D97706,stroke-width:2px,color:#1F2937
    style RC2 fill:#F59E0B,stroke:#D97706,stroke-width:2px,color:#1F2937
    style RC3 fill:#F59E0B,stroke:#D97706,stroke-width:2px,color:#1F2937
    style UC1 fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff
    style UC2 fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff
    style UC3 fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff
    style UC4 fill:#72B043,stroke:#5A8F36,stroke-width:2px,color:#fff
    style E1 fill:#E12729,stroke:#B91C1C,stroke-width:2px,color:#fff
    style E2 fill:#E12729,stroke:#B91C1C,stroke-width:2px,color:#fff
    style E3 fill:#E12729,stroke:#B91C1C,stroke-width:2px,color:#fff

Interactive Diagram

The flow runs bottom to top.

Key Components Explained

🌳 CORE PROBLEM (The Trunk)

A core problem is:

Specific: defined population, geographic context
Observable and measurable through data
Urgent to the community and stakeholders
Written without causes or solutions

Example: Good Core Problem Statement

"Young adults aged 18-25 in rural communities have limited access to decent, stable employment and livelihood opportunities."

Example: Poor Core Problem Statement

"Young adults lack skills training, which causes unemployment."

❌ Embeds a cause and a solution.

🌱 ROOT CAUSES (The Roots)

Identify root causes:

Go 2-3 levels deep asking "Why?"
Cover categories: economic, social, policy, geographic, cultural
Tag each cause (E) evidence-based or (A) assumption

Examples: Root Causes with Evidence Tags

• Skills-labor market mismatch (E)
• Limited access to startup capital and microcredit (A)

The Power of (E) and (A) Tags

Tags show funders what's proven and what's assumed.

🌿 EFFECTS (The Branches)

Map effects:

Immediate (0-6 months), medium-term (6 months-2 years), long-term (2+ years)
Levels: individual, family, community, system
Tag effects (E) or (A) like causes

Examples: Effects with Evidence Tags

Immediate: High youth income insecurity (E)
Long-term: Lost economic potential, demographic dividend (A)

How the Tree Works Together

Causes feed the problem; effects justify it
Where you act depends on which causes you can address

From Problem Tree to Theory of Change

In Lesson 1.4, causes become activities, effects become outcomes.

Common Mistakes to Avoid

❌ Embedding causes in the core problem statement

Poor: "skills gaps cause unemployment." Good: "limited access to employment."

❌ Confusing a symptom for a cause

Poor: "unemployed" restates the problem. Good: skills-market mismatch, the cause beneath it.

❌ Stopping at surface-level causes

Poor: "skills mismatch." Good: ask why again: curricula misaligned, then transition outpacing training.

❌ Skipping the (E)/(A) tags

Poor: "limited transportation," untagged. Good: tag (A) until stakeholders validate it.

From Framework to Practice

Next: use AI-assisted research to populate this framework.

Understanding the Problem Tree Structure