Problem Tree Brainstorming Questions

❓ Guiding questions

🌳 Trunk — Define the Core Problem

• What is the one problem your project aims to address (no solutions, no causes)?

• Who is most affected, and where?

• Why is this urgent to address now?

• What evidence shows this is a real, present problem (baseline or statistic)?

• Working problem statement (1–2 lines): ____________________________________________

🌱 Roots — Identify Root Causes (ask “Why?” 2–3 times)

Think across categories: systems/policy, economic/resources, information/skills, access/geography, social/cultural norms, governance/coordination.

• What deeper conditions or mechanisms create or sustain the problem?

• Which causes are supported by evidence (E) vs assumptions (A)?

• What indicators typically evidence each cause (name • unit • possible source)?

• Where are the knowledge gaps?

🍃 Branches — Identify Effects/Consequences

• What near‑term symptoms are visible now?

• What medium‑term and long‑term consequences emerge if nothing changes?

• Who experiences these effects differently (gender, age, location)?

• Which indicators reflect these effects?

🔎 Evidence & Indicators (quick prompts)

• Which existing datasets or reports can you reuse (national stats, UN, regulator, reputable NGO, peer‑reviewed)?

• Is the indicator measurable (unit, frequency, feasible source)?

• What would a baseline look like for your context?

🗣️ Stakeholder Questions (to validate later)

• Which barriers are most acute here—and for whom?

• What supports already exist? Who accesses them, who does not, and why?

• Which seasonal/policy/market factors change this picture?

• What unexpected effects are we missing?

• What would success look like for you in 6–12 months?

🧩 Working Areas (Print or Digital)

9KB

festa-problem-tree-svg-1.svg

image

Open

B) Indicators Mini‑Table

Indicator	What it measures	Unit/Frequency	Possible sources	Notes

C) Citation Log (for proposals & ToC later)

#	Publisher/Author	Year	Title/URL	Note on how you used it
1
2

D) Top Questions to Validate (6–10)

---

🎨 Layout Prototype (for InDesign)

Page size: Letter or A4, orientation: Landscape Margins: 16–20 mm; Grid: 12‑column, 8‑row Sections:

1. Header band (Lesson title, version, date)

2. Three zones stacked: Branches (top) • Trunk (center) • Roots (bottom) with generous note space

3. Right sidebar for Indicators, Citations, Top Questions

4. Small footer with page number + “Preliminary — to be validated”

Visual cues:

• Roots zone tinted light neutral; branches slightly brighter; trunk white.

• Add tiny (E) and (A) chips to mark Evidence vs Assumption.

• Include icons (leaf/branch/root) for quick scanning.

• Provide light sticky‑note placeholders (dotted rectangles) sized ~60×60 mm.

Accessibility:

• Minimum body text 10.5–12 pt, high contrast, avoid red‑green pairs.

• Leave space for handwritten notes if printed.

---

✅ Micro‑Checklist (print on the page)

• Problem is stated without causes or solutions

• At least 2–3 levels of causes explored

• Effects mapped (short/medium/long‑term)

• Each item tagged (E) evidence or (A) assumption

• Indicators and Citations logged

• 6–10 questions drafted for stakeholders

---

🗂️ Version Block

• Project / Team: ______________________________

• Version / Date: ______________________________

• Prepared by: ______________________________

• Sources consulted (top 3): ______________________________

Keep this sheet with your project record. You’ll reuse it in Theory of Change, Logframe, Activity Design, and Proposal Writing.