Process Overview
The Four-Phase Workflow
How the four phases connect, and what each produces:
graph TB
%% Start
START(["<strong>START</strong><br/>Stakeholder Conversations Complete"])
%% Phase 1: CAPTURE
PHASE1["<strong>PHASE 1: CAPTURE</strong><br/>Extract Individual Insights"]
C1["Review conversation notes<br/>and transcripts"]
C2["Extract discrete insights<br/>(one per card)"]
C3["Maintain source attribution<br/>and context"]
C4["<strong>OUTPUT:</strong> 40-60 insight cards"]
%% Phase 2: CLUSTER
PHASE2["<strong>PHASE 2: CLUSTER</strong><br/>Group Related Insights"]
CL1["Look for natural affinities<br/>(not predetermined categories)"]
CL2["Create clusters of<br/>5-10 related insights"]
CL3["<strong>OUTPUT:</strong> 6-8 insight clusters"]
%% Decision Point 1
DECISION1{"Themes<br/>emerging?"}
%% Phase 3: THEME
PHASE3["<strong>PHASE 3: THEME</strong><br/>Name Insight Clusters"]
T1["Create descriptive headers<br/>for each cluster"]
T2["<strong>OUTPUT:</strong> 5-8 named themes<br/>with supporting evidence"]
%% Phase 4: SYNTHESIZE
PHASE4["<strong>PHASE 4: SYNTHESIZE</strong><br/>Integrate with Problem Tree"]
S1["Map themes to<br/>Problem Tree elements"]
S2["Convert assumptions (A)<br/>to evidence (E)"]
S3["<strong>OUTPUT:</strong> Refined Problem Tree"]
%% Decision Point 2
DECISION2{"Integration<br/>complete?"}
%% End
END(["<strong>END</strong><br/>Evidence-Based Problem Tree"])
%% Main Flow
START --> PHASE1
PHASE1 --> C1 --> C2 --> C3 --> C4
C4 --> PHASE2
PHASE2 --> CL1 --> CL2 --> CL3
CL3 --> DECISION1
DECISION1 -->|Yes| PHASE3
DECISION1 -.->|No<br/>Re-cluster| CL1
PHASE3 --> T1 --> T2
T2 --> PHASE4
PHASE4 --> S1 --> S2 --> S3
S3 --> DECISION2
DECISION2 -->|Yes| END
DECISION2 -.->|Refine| T1
%% Styling
style START fill:#E5E7EB,stroke:#6B7280,stroke-width:3px,color:#2A2A2A
style END fill:#D1FAE5,stroke:#10B981,stroke-width:4px,color:#2A2A2A
style PHASE1 fill:#10B981,stroke:#059669,stroke-width:4px,color:#fff
style PHASE2 fill:#10B981,stroke:#059669,stroke-width:4px,color:#fff
style PHASE3 fill:#10B981,stroke:#059669,stroke-width:4px,color:#fff
style PHASE4 fill:#10B981,stroke:#059669,stroke-width:4px,color:#fff
style C1 fill:#ECFCCB,stroke:#72B043,stroke-width:2px,color:#2A2A2A
style C2 fill:#ECFCCB,stroke:#72B043,stroke-width:2px,color:#2A2A2A
style C3 fill:#ECFCCB,stroke:#72B043,stroke-width:2px,color:#2A2A2A
style C4 fill:#D1FAE5,stroke:#10B981,stroke-width:3px,color:#2A2A2A
style CL1 fill:#FEF3C7,stroke:#F59E0B,stroke-width:2px,color:#2A2A2A
style CL2 fill:#FEF3C7,stroke:#F59E0B,stroke-width:2px,color:#2A2A2A
style CL3 fill:#FED7AA,stroke:#F59E0B,stroke-width:3px,color:#2A2A2A
style T1 fill:#FED7AA,stroke:#F59E0B,stroke-width:2px,color:#2A2A2A
style T2 fill:#FEF3C7,stroke:#F59E0B,stroke-width:3px,color:#2A2A2A
style S1 fill:#ECFCCB,stroke:#72B043,stroke-width:2px,color:#2A2A2A
style S2 fill:#ECFCCB,stroke:#72B043,stroke-width:2px,color:#2A2A2A
style S3 fill:#D1FAE5,stroke:#10B981,stroke-width:3px,color:#2A2A2A
style DECISION1 fill:#9CA3AF,stroke:#6B7280,stroke-width:3px,color:#2A2A2A
style DECISION2 fill:#9CA3AF,stroke:#6B7280,stroke-width:3px,color:#2A2A2A
Reading the Four-Phase Flowchart
Phase 1: CAPTURE (Individual Insights)
Objective: Extract every important insight onto individual cards, without interpretation.
The Capture Process
- Review stakeholder documentation from Lesson 1.2, one at a time
- Extract discrete insights, one per card
- Use stakeholder language, not your interpretation
- Include context markers: stakeholder, conversation, question
- Maintain insight integrity, don't combine points
Quality Standards for Captured Insights
One distinct insight per card
Clear source attribution, language preserved
Supportive and challenging insights included
Examples of Well-Captured Insights
"Transportation costs eat up 30% of potential daily wages for rural youth"
[Source: Community Focus Group, Rural Employment Discussion]
"Employers say vocational graduates lack practical problem-solving skills"
[Source: Private Sector Interview, Manufacturing Company Owner]
"Young women face family pressure not to travel outside village for work"
[Source: Women's Group Discussion, Gender and Employment]
"Previous training programs failed because they didn't connect to actual job opportunities"
[Source: NGO Partner Interview, Skills Development History]
Phase 2: CLUSTER (Natural Groupings)
Objective: Group related insights by natural affinity, not preset categories.
The Clustering Process
- Spread all cards where you can see them
- Look for natural relationships between insights
- Trust your instincts about what belongs together
- Start with obvious clusters, then subtler ones
- Allow for outliers that don't cluster
- Iterate and refine as patterns clear
Clustering Guidelines
Size Flexibility
2-15 cards, overlap allowed.
Outlier Respect
Singletons still matter.
Natural Emergence
Let groupings emerge; don't force categories.
Example Clustering Process
Initial Scatter: 47 individual insights from stakeholder conversations
First Pass Clustering:
- Cluster A: 8 insights about skills-job mismatch
- Cluster B: 6 insights about transportation and access
- Cluster C: 5 insights about gender and cultural barriers
- Cluster D: 12 insights about previous program failures
- Cluster E: 4 insights about successful examples
- Outliers: 12 insights that don't clearly cluster yet
Second Pass Refinement:
- Split Cluster D into "Program Design Issues" vs "Implementation Issues"
- Merge some outliers with existing clusters as patterns become clearer
- Identify 2 remaining singleton insights that represent unique perspectives
Clustering Tip
Phase 3: THEME (Pattern Identification)
Objective: Identify the common thread uniting each cluster.
The Theming Process
- Examine each cluster individually
- Ask "What's the common thread?"
- Create descriptive theme headers
- Test theme accuracy against every insight
- Refine cluster boundaries if needed
- Document theme descriptions with evidence
Theme Quality Indicators
Accurate and specific: represents every insight, suggests action
Grounded and distinct: multiple stakeholders, no overlap
Community voice: reflects stakeholder language
Example Theme Development
Cluster: 8 insights about skills-job mismatch
Sample insights:
- • "Vocational graduates can't solve real workplace problems"
- • "Training programs teach outdated techniques"
- • "Employers need soft skills but schools focus on technical skills"
- • "Students learn theory but have never seen actual workplaces"
❌ Initial theme attempt: "Skills Problems"
Too vague - doesn't suggest action
⚠️ Refined theme: "Skills-Market Disconnect: Training Misaligned with Employer Needs"
Better - specific and actionable
✅ Final theme description:
"Current skills development programs are disconnected from actual employer needs and workplace realities. Graduates have theoretical knowledge but lack practical problem-solving skills, exposure to real work environments, and the soft skills that employers prioritize."
Phase 4: SYNTHESIZE (Pattern Analysis)
Objective: Analyze cross-theme patterns for strategic insight.
The Synthesis Process
- Map relationships between themes
- Identify priority themes by frequency
- Look for surprises challenging assumptions
- Note contradictions between stakeholders
- Extract implications for your design
- Prepare integration into your Problem Tree
Key Synthesis Questions
🔍 Which themes appeared most frequently, or surprised you?
🔍 How do themes reinforce or contradict each other?
🔍 Which themes highlight barriers or risks you hadn't considered?
🔍 What themes suggest interventions, or reveal assets to build on?
Synthesis Goal
Process Summary
| Phase | What You Do | Output | Time |
|---|---|---|---|
| 1. Capture | Extract individual insights from stakeholder documentation | 30-100+ insight cards | 45-60 min |
| 2. Cluster | Group related insights by natural affinities | 5-10 insight clusters | 30-45 min |
| 3. Theme | Identify common threads and create descriptive headers | 5-8 theme descriptions | 30-40 min |
| 4. Synthesize | Analyze patterns across themes for strategic insights | Synthesis summary | 20-30 min |
What's Next
Next, integrate your themes into your Problem Tree.