What Theory of Change Is
Theory of Change maps the pathway from your inputs to your desired impact, linking analysis to solution design through explicit assumptions.
Strategic Thinking Tool
What Theory of Change Isn't
❌ Not a Project Plan
Strategic logic, not an implementation timeline.
❌ Not Static Document
It evolves without losing its community grounding.
Core Components Overview
Six connected elements:
INPUTS → ACTIVITIES → OUTPUTS → OUTCOMES → IMPACT
↑
ASSUMPTIONS
(How/why this pathway creates change)
Visual Framework
How the components connect, with assumptions as the foundation:
graph TB
%% Top: Inputs
INPUTS["<strong>INPUTS</strong><br/>What You Invest<br/><br/>💼 Resources<br/>💼 Partnerships<br/>💼 Community Assets"]
%% Activities
ACTIVITIES["<strong>ACTIVITIES</strong><br/>What You Do<br/><br/>⚙️ Concrete Actions<br/>⚙️ Services Delivered<br/>⚙️ Systems Built"]
%% Outputs
OUTPUTS["<strong>OUTPUTS</strong><br/>What You Produce<br/><br/>📦 Immediate Results<br/>📦 Measurable Products<br/>📦 Direct Deliverables"]
%% Outcomes
OUTCOMES["<strong>OUTCOMES</strong><br/>What Changes<br/><br/>🎯 Behavior Shifts<br/>🎯 Knowledge Gains<br/>🎯 Condition Improvements"]
%% Impact
IMPACT["<strong>IMPACT</strong><br/>What Transforms<br/><br/>🌟 Long-term Change<br/>🌟 Systemic Shifts<br/>🌟 Community Transformation"]
%% Assumptions Foundation
ASSUMPTIONS["<strong>ASSUMPTIONS</strong><br/><br/>🔍 Why This Pathway Works<br/>🔍 What Needs to Be True<br/>🔍 Testable Hypotheses"]
%% Main Flow
INPUTS --> ACTIVITIES
ACTIVITIES --> OUTPUTS
OUTPUTS --> OUTCOMES
OUTCOMES --> IMPACT
%% Assumptions Connect to All
ASSUMPTIONS -.-> INPUTS
ASSUMPTIONS -.-> ACTIVITIES
ASSUMPTIONS -.-> OUTPUTS
ASSUMPTIONS -.-> OUTCOMES
ASSUMPTIONS -.-> IMPACT
%% Styling
style INPUTS fill:#DBEAFE,stroke:#3B82F6,stroke-width:3px,color:#2A2A2A
style ACTIVITIES fill:#ECFCCB,stroke:#72B043,stroke-width:3px,color:#2A2A2A
style OUTPUTS fill:#FEF3C7,stroke:#F59E0B,stroke-width:3px,color:#2A2A2A
style OUTCOMES fill:#FED7AA,stroke:#F59E0B,stroke-width:3px,color:#2A2A2A
style IMPACT fill:#D1FAE5,stroke:#10B981,stroke-width:4px,color:#2A2A2A
style ASSUMPTIONS fill:#E5E7EB,stroke:#6B7280,stroke-width:3px,color:#2A2A2A
Reading the Theory of Change Flow
- Vertical Progression: Inputs to long-term impact, in one chain
- Assumptions Foundation: Dotted lines show every stage rests on an assumption
Component Definitions
Each component:
💼 INPUTS: What You Invest
Resources you mobilize: funding, staff time, facilities, relationships, and knowledge.
⚙️ ACTIVITIES: What You Do
Concrete actions using your inputs: training, services, advocacy.
📦 OUTPUTS: What You Produce
Measurable results you control: people trained, materials produced.
🎯 OUTCOMES: What Changes
Shifts in knowledge, behavior, or systems over time.
🌟 IMPACT: What Transforms
Long-term, systemic change (5-10+ years), never from one project alone.
🔍 ASSUMPTIONS: Why This Works
Beliefs about why the pathway works: contextual, behavioral, strategic.
How Components Connect: Youth Employment Example
**INPUTS:**
- $200K funding from foundation
- 3 staff (training coordinator, employer liaison, M&E)
- Partner relationships with 15 local employers
- Community training space and equipment
- Local knowledge about youth barriers and employer needs
**ACTIVITIES:**
- Market-responsive skills training (6-month program)
- Employer partnership development and job matching
- Ongoing mentorship and job placement support
- Soft skills and workplace readiness coaching
**OUTPUTS:**
- 120 youth complete market-responsive training annually
- 15+ active employer partnerships maintained
- 100+ job placements facilitated per year
- 80+ youth receiving 6-month follow-up support
**SHORT-TERM OUTCOMES (0-12 months):**
- Youth gain technical and soft skills valued by employers
- Youth build confidence and workplace readiness
- Employers recognize program quality and hire graduates
**MEDIUM-TERM OUTCOMES (1-3 years):**
- 70% of graduates secure employment within 6 months
- Employed youth maintain jobs and increase incomes
- Employers expand partnerships and hiring commitments
**LONG-TERM OUTCOMES (3-7 years):**
- Sustained employer-training provider collaboration model
- Increased quality employment access for rural youth
- Shifted perceptions about youth workforce potential
**IMPACT (5-10 years):**
"Young people in rural communities have sustainable livelihood opportunities that enable them to thrive locally"
**KEY ASSUMPTIONS:**
- Market-responsive training + employer partnerships lead to employment (not training alone)
- Youth will complete programs if they see real job opportunities (motivation assumption)
- Employers will hire trained youth if skills match needs (employer behavior assumption)
- Economic conditions remain stable enough for job creation (contextual assumption)
Theory of Change vs. Logic Models
How Theory of Change differs from a logic model:
| Aspect | Logic Models | Theory of Change |
|---|---|---|
| Primary Focus | Logical sequence of project elements | Context, assumptions, and change narratives |
| Structure | More linear and structured | Accommodates complexity, uncertainty, multiple pathways |
| Assumptions | Often implicit or briefly noted | Explicit, detailed, and central to framework |
| Community Voice | May or may not incorporate stakeholder input | Emphasizes community priorities and validation |
| Adaptability | Generally static once established | Designed to evolve as learning occurs |
| Best Use | Project management and reporting | Strategic thinking and adaptive management |
Three Levels of Outcomes Explained
Realistic outcome timeframes:
Short-term Outcomes (0-12 months)
What changes: Knowledge, awareness, and skills
Example: Youth gain workplace-ready technical and soft skills.
Necessary, not sufficient, for behavior change.
Medium-term Outcomes (1-3 years)
What changes: Behavior and access
Example: Trained youth secure and maintain employment.
Your project's influence is strongest here.
Long-term Outcomes (3-7 years)
What changes: Systems and norms
Example: Sustained employer-training collaboration systems.
Your project contributes, but rarely controls, this.
Making Assumptions Explicit and Testable
Making assumptions explicit lets you monitor and test them:
❌ Implicit Assumptions (Weak)
- "Communities will support the project"
- "Training will lead to behavior change"
Too vague to test or monitor.
✅ Explicit Assumptions (Strong)
- "Community leaders will actively promote participation and at least 60% of target population will engage"
- "Participants who complete training and receive 3 months follow-up support will adopt practices at 70%+ rates"
Specific enough to monitor and adjust.
Next Steps
Explore how to build your theory:
- From Problem Tree to Change Logic - Translating your analytical work
- Incorporating Community Insights - Using stakeholder wisdom
- Step-by-Step Guide - 15-step development process