Integration Goal
Integration Workflow Overview
How your Phase 4 themes integrate into your Problem Tree, in three steps:
graph TB
%% Top Tier: Synthesis Themes from Affinity Process
THEMES["<strong>SYNTHESIS THEMES</strong><br/><br/>Output from Phase 4: Synthesize<br/>(6-8 named themes with supporting quotes)"]
%% Individual Theme Examples (from Nigeria Youth example)
T1["<strong>Theme 1:</strong><br/>Skills-Market Disconnect"]
T2["<strong>Theme 2:</strong><br/>Economic Barriers"]
T3["<strong>Theme 3:</strong><br/>Gender-Specific Challenges"]
T4["<strong>Theme 4:</strong><br/>Community Assets Untapped"]
T5["<strong>Theme 5:</strong><br/>Training Quality Issues"]
T6["<strong>Theme 6:</strong><br/>Transportation Barriers"]
%% Middle Tier: 3-Step Integration Process
STEP1["<strong>STEP 1: MAP THEMES</strong><br/><br/>Match themes to existing<br/>Problem Tree elements"]
STEP2["<strong>STEP 2: VALIDATE & REFINE</strong><br/><br/>Determine what to keep,<br/>revise, or add"]
STEP3["<strong>STEP 3: DOCUMENT CHANGES</strong><br/><br/>Update tree with traceability<br/>to stakeholder quotes"]
%% Bottom Tier: Outcomes
OUTCOMES["<strong>PROBLEM TREE OUTCOMES</strong>"]
OUT1["<strong>✅ Validated Assumptions</strong><br/><br/>Assumptions (A) confirmed<br/>by stakeholder evidence<br/><br/>Convert to Evidence (E)"]
OUT2["<strong>➕ New Elements Added</strong><br/><br/>New causes or effects<br/>discovered through synthesis<br/><br/>Tag as Evidence (E)"]
OUT3["<strong>🔄 Refined Elements</strong><br/><br/>Partially validated assumptions<br/>requiring adjustment<br/><br/>Revise wording, keep as (E)"]
OUT4["<strong>❌ Challenged Assumptions</strong><br/><br/>Contradicted by stakeholder<br/>evidence<br/><br/>Remove or reframe entirely"]
%% Final Output
FINAL["<strong>REFINED PROBLEM TREE</strong><br/><br/>Evidence-based analysis ready for<br/>Theory of Change (Lesson 1.4)"]
%% Connections
THEMES --> T1
THEMES --> T2
THEMES --> T3
THEMES --> T4
THEMES --> T5
THEMES --> T6
T1 --> STEP1
T2 --> STEP1
T3 --> STEP1
T4 --> STEP1
T5 --> STEP1
T6 --> STEP1
STEP1 --> STEP2
STEP2 --> STEP3
STEP3 --> OUTCOMES
OUTCOMES --> OUT1
OUTCOMES --> OUT2
OUTCOMES --> OUT3
OUTCOMES --> OUT4
OUT1 --> FINAL
OUT2 --> FINAL
OUT3 --> FINAL
OUT4 --> FINAL
%% Styling
style THEMES fill:#72B043,stroke:#059669,stroke-width:4px,color:#fff
style OUTCOMES fill:#10B981,stroke:#059669,stroke-width:4px,color:#fff
style FINAL fill:#D1FAE5,stroke:#10B981,stroke-width:4px
style T1 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style T2 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style T3 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style T4 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style T5 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style T6 fill:#ECFCCB,stroke:#72B043,stroke-width:2px
style STEP1 fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff
style STEP2 fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff
style STEP3 fill:#10B981,stroke:#059669,stroke-width:3px,color:#fff
style OUT1 fill:#D1FAE5,stroke:#10B981,stroke-width:2px
style OUT2 fill:#DBEAFE,stroke:#3B82F6,stroke-width:2px
style OUT3 fill:#FED7AA,stroke:#F59E0B,stroke-width:2px
style OUT4 fill:#FEE2E2,stroke:#DC2626,stroke-width:2px
Reading the Integration Workflow
Step-by-Step Integration Process
Integration connects your synthesis work to the Lesson 1.1 Problem Tree, completing the evidence trail.
Step 1: Map Themes to Problem Tree Elements
For each affinity theme, identify:
Which Problem Tree element(s) it relates to
Whether it validates existing elements or suggests new ones
Whether it challenges or refines your original analysis
Step 2: Convert Assumptions to Evidence
Review items marked (A) in your original Problem Tree from Lesson 1.1:
- Convert validated assumptions to (E) when stakeholder insights confirm them
- Reframe or remove assumptions stakeholders contradicted
- Add evidence notes referencing the theme and quotes that validate each element
Remember the Nigeria Youth Livelihood Example
Step 3: Add New Elements
Affinity analysis often reveals what desk research missed:
New causes stakeholders identified but desk research missed
Effects the community emphasized that you hadn't considered
Contextual factors unique to this community
Step 4: Refine Problem Statement
Sometimes stakeholder insights suggest adjustments to your core problem statement:
- Adjust language to reflect community priorities
- Refine scope to match what you learned
- Keep it focused, not so broad it loses clarity
Integration Documentation Template
Document how each affinity theme connects to your Problem Tree using this template:
## AFFINITY THEME: [Theme Name]
**Source insights:** [Number] insights from [Number] stakeholders
**Key stakeholder groups:** [List primary contributors]
### Problem Tree Integration:
**Validates existing elements:**
- [Original element] → Supported by theme evidence
**Challenges existing elements:**
- [Original element] → Contradicted/refined by stakeholder input
**Adds new elements:**
- [New cause/effect] → Revealed through community insights
### Supporting Evidence:
**Key quotes:**
- "[Stakeholder quote 1]" - [Source]
- "[Stakeholder quote 2]" - [Source]
**Pattern strength:** High/Medium/Low
**Action implications:** [What this suggests for project design]
Example Integration: Youth Employment Problem Tree
Here's how affinity themes refine a preliminary Problem Tree element:
Original Problem Tree Element
Root Cause: Limited access to vocational training (A)
Affinity Theme from Synthesis
Theme: "Skills-Market Disconnect: Training Misaligned with Employer Needs"
Based on: 8 stakeholder insights from employers, training providers, and unemployed youth
Key finding: Training programs exist, but they're disconnected from what employers actually need and what workplaces actually look like.
Integration Outcome
Refined Root Cause: Skills training exists but is disconnected from employer needs and workplace realities (E)
├─ Vocational programs teach outdated techniques (E)
├─ Training focuses on theory without practical application (E)
├─ Employers prioritize soft skills not addressed in programs (E)
└─ No structured employer-training provider collaboration (E)
Supporting evidence:
- "Vocational graduates can't solve real workplace problems" - Manufacturing Owner
- "Training programs teach outdated techniques" - Skills Provider
- "Students learn theory but have never seen actual workplaces" - Recent Graduate
What Changed
Added Elements from Affinity Analysis
Stakeholder conversations revealed an entirely new root cause not in the original Problem Tree:
New Root Cause: Previous program failures created stakeholder skepticism (E)
├─ Community has low confidence in training programs based on past experience
├─ Employers reluctant to engage due to poor previous partnerships
└─ Youth prefer informal pathways due to formal program disappointments
Supporting evidence:
- "We've tried this before and it didn't work" - 6 different stakeholders
- "Employers don't trust training partnerships anymore" - NGO Partner
- "Young people see training as a waste of time" - Community Leader
Why This Matters
Visual Integration: Before & After
Before Synthesis
v1.0 (Desk Research)
- • 60% assumptions, 40% evidence
- • Missing context, not community-validated
After Synthesis
v2.0 (Community-Validated)
- • 85% evidence, 15% remaining assumptions
- • New causes, context-specific interventions
Integration Checklist
What's Next
Next, the complete step-by-step guide bringing all four phases together.
Next: Complete Step-by-Step Guide
Detailed instructions with time estimates for each phase.
Implementation Guide →