Formulate Insight: Pattern Analysis Guide

Formulate Insight is Quadrant 2 of the action-learning methodology. This is where you analyze your Ground Truth data to identify themes, patterns, and root causes.

What is an Insight?

Insight = A deeper understanding of why problems exist

• Not just listing problems
• Understanding underlying patterns
• Identifying root causes
• Recognizing “superior interests” (what people really need)

The Analysis Process

Step 1: Consolidate Data

If Individual: Review all your interview notes and voice notes

If Team: Combine research from all team members

• Pool all voice notes
• Share interview summaries
• Compare observation notes
• Look for overlaps and contradictions

Step 2: Identify Themes

Theme = A recurring topic across multiple interviews

How to Find Themes:

1. List all problems mentioned
2. Group similar problems together
3. Name each group (e.g., “Access Issues”, “Cost Barriers”, “Trust Problems”)
4. Count frequency (how many people mentioned this?)

Example Themes:

• Waste Management: “Lack of collection services in low-income areas”
• Transportation: “First-mile/last-mile gaps in public transit”
• Healthcare: “Distrust of formal medical facilities”

Step 3: Find Root Causes

Root Cause = Why the problem exists, not just the symptom

Use “5 Whys” Technique:

Example:

• Problem: Market traders can’t save money
• Why? No banks nearby
• Why? Banks avoid low-income areas
• Why? High operational costs for physical branches
• Why? Traditional banking model not profitable for small accounts
• Root Cause: Banking system designed for high-value customers, excludes low-income earners

Step 4: Identify Superior Interests

Superior Interest = The underlying need beneath surface problems

People might say they want X, but they actually need Y.

Example:

• Surface request: “We need more garbage trucks”
• Superior interest: “We need a system that actually removes waste consistently”
• Better solution might be: Community collection points, waste-to-value programs, or private collection services

Documentation Format

On your team page (/team/[your-team]/formulate-insight), document:

1. Key Themes

List 3-5 major themes with:

• Theme name
• Evidence (quote count, voice note references)
• Affected population

2. Root Cause Analysis

For each theme:

• Surface problem
• Underlying causes
• Contributing factors

3. Superior Interests

What does the community actually need?

• Beyond surface requests
• Validated by research
• Addresses root causes

Quality Checklist

✅ Themes supported by multiple interviews
✅ Root causes go beyond surface symptoms
✅ Evidence cited (quotes, voice notes)
✅ Patterns validated across diverse interviewees
✅ Superior interests clearly articulated

Common Mistakes

❌ Jumping to Solutions - “The insight is that they need an app”
❌ Superficial Analysis - Stopping at first-level problems
❌ Ignoring Contradictions - Cherry-picking data that fits your bias
❌ Weak Evidence - “We think…” instead of “Data shows…”
❌ Over-generalizing - “Everyone wants…” based on 3 interviews

Example: Good vs. Bad Insight

❌ Bad Example

“Our insight is that people need a better waste management app. We’ll build one.”

Problems: This is a solution, not an insight. No root cause analysis.

✅ Good Example

“Theme: Waste accumulation in markets. Root cause: Municipal services prioritize residential areas over commercial markets due to budget constraints. Merchants willing to pay for private collection but lack coordination. Superior interest: Reliable, consistent waste removal they control, even if not free.”

Strengths: Clear theme, root cause identified, superior interest defined, implies solution direction without prescribing it yet

Analysis Tools

Affinity Mapping

1. Write each problem/quote on separate note
2. Group similar items together
3. Name each cluster
4. Identify patterns across clusters

Fishbone Diagram (Ishikawa)

         Problem
            |
    --------.--------
    |       |       |
  Cause   Cause   Cause
    |       |       |
  Detail  Detail  Detail

Map contributing causes to understand complexity

Moving Forward

Once you have solid insights:

1. Document thoroughly on your team page
2. Validate with mentors during check-ins
3. Move to Quadrant 3: Formulate Hypothesis

Formulate Hypothesis Guide →

Remember: Good insights reveal why problems exist, not just what problems are. This understanding guides better solutions.