Design tips

Symptoms vs Root Causes: A Clarity Check

A short note to deepen Lesson 1: Problem Tree Analysis.

Abayomi Ogundipe

Abayomi Ogundipe

2 min read
Symptoms vs Root Causes: A Clarity Check

Teams often describe a problem by naming the most visible symptom. It sounds clear, but it hides the real drivers. A symptom is what people feel. A root cause is what creates the pattern in the first place. If you mix them, your project will solve the wrong thing.

I use this approach in my own project design work, and it helps teams stay aligned as the project evolves.

Here is a simple check you can run with any team.

Step 1: Write the symptom in one line.

Example: "Attendance is low in after school programs."

Step 2: Ask why three times.

  • Why is attendance low? Students do not stay after school.
  • Why do they not stay? They have to work or care for siblings.
  • Why is that happening? Household income is unstable and support systems are thin.

Step 3: Separate the layers.

  • Symptom: low attendance
  • Contributing factors: work and caregiving responsibilities
  • Root causes: economic instability, lack of support systems, scheduling that ignores household reality

Step 4: Name what you can influence.

You cannot change the entire economy, but you can design around family schedules, provide transportation, or adjust program timing.

If your team gets stuck, ask this: "If we removed the symptom, what would still be true?" Whatever remains is closer to the root cause. This question keeps the conversation grounded.

Try this today. Pick one project and run the check with two colleagues. If you disagree on the root cause, that is a good signal. It means you surfaced hidden assumptions early.

Contextual diagram of clarity check is below. You can also view pdf version.

More resources: Lesson 1: Problem Tree Analysis.

Diagram

Symptoms vs Root Causes - A Clarity Check

Symptoms vs root causes: a clarity check

graph TB Start["🔍 PROBLEM STATEMENT

What your team describes
as 'the problem'"] Q1{"Is this what people
feel/see directly?"} Symptom["⚠️ SYMPTOM

The visible effect
Example: 'Attendance is low
in after-school programs'"] Why1["❓ ASK WHY #1

Why is attendance low?
'Students do not stay after school'"] Why2["❓ ASK WHY #2

Why do they not stay?
'They have to work or
care for siblings'"] Why3["❓ ASK WHY #3

Why is that happening?
'Household income is unstable
and support systems are thin'"] subgraph Layers["📊 SEPARATE THE LAYERS"] L1["Symptom Layer
Low attendance"] L2["Contributing Factors
Work & caregiving
responsibilities"] L3["Root Causes
Economic instability
Lack of support systems
Scheduling ignores household reality"] end Influence["🎯 NAME WHAT YOU
CAN INFLUENCE

• Design around family schedules
• Provide transportation
• Adjust program timing"] Check["✅ CLARITY CHECK

'If we removed the symptom,
what would still be true?'

Whatever remains is
closer to root cause"] Start --> Q1 Q1 -->|Yes| Symptom Symptom --> Why1 Why1 --> Why2 Why2 --> Why3 Why3 --> Layers L1 --> L2 L2 --> L3 Layers --> Influence Influence --> Check style Start fill:#F6F6F6,stroke:#737373,color:#2A2A2A style Q1 fill:#F8CC1B,stroke:#CA8A04,color:#2A2A2A style Symptom fill:#E12729,stroke:#B91C1C,color:#fff style Why1 fill:#FEF3C7,stroke:#F8CC1B,color:#2A2A2A style Why2 fill:#FEF3C7,stroke:#F8CC1B,color:#2A2A2A style Why3 fill:#FEF3C7,stroke:#F8CC1B,color:#2A2A2A style Layers fill:#F6F6F6,stroke:#737373,color:#2A2A2A style L1 fill:#FCA5A5,stroke:#E12729,color:#2A2A2A style L2 fill:#FDBA74,stroke:#F37324,color:#2A2A2A style L3 fill:#D9F99D,stroke:#72B043,color:#2A2A2A style Influence fill:#007F4E,stroke:#00b369,color:#fff,stroke-width:3px style Check fill:#72B043,stroke:#5b7c37,color:#fff