16-Step Logframe Development Process
A workflow turning Module 1 work into an operational Logframe.
Process Structure
- Phase 1: Foundation Review (30-40 min) - Steps 1-3
- Phase 2: Structure Development (45-60 min) - Steps 4-6
- Phase 3: Indicator Development (60-90 min) - Steps 7-10
- Phase 4: Verification Planning (45-60 min) - Steps 11-13
- Phase 5: Validation (30-45 min) - Steps 14-16
Phase 1: Foundation Review and Integration
Time: 30-40 minutes
Step 1: Gather All Module 1 Materials
Gather Problem Tree tags, stakeholder map, affinity themes, and Theory of Change.
Step 2: Review Community Validation Results
Extract stakeholder feedback and priorities from validation sessions.
Step 3: Prepare Integration Workspace
Set up your Logframe template and sort insights by level.
Phase 2: Logframe Structure Development
Time: 45-60 minutes
Step 4: Map Theory of Change to Logframe Levels
Theory of Change Impact → Logframe Goal
"{{Your impact statement from Lesson 1.4}}"
↓
Logframe Goal: "{{Same impact statement with refinements from community validation}}"
Theory of Change Primary Outcome → Logframe Purpose
"{{Your main outcome from Theory of Change}}"
↓
Logframe Purpose: "{{Primary outcome with enhanced specificity based on community input}}"Step 5: Translate Outputs with Community Specificity
Theory of Change Output: "{{Generic output statement}}"
↓
Logframe Output: "{{X number of [specific population] complete [specific intervention] meeting [quality standards] and [community-defined criteria]}}"Step 6: Detail Activities Using Problem Tree Logic
Theory of Change Activity: "{{General activity description}}"
↓
Logframe Activities (addressing specific root causes):
1.1 {{Activity component addressing root cause A}}
1.2 {{Activity component addressing root cause B}}
1.3 {{Activity component addressing root cause C}}
1.4 {{Activity component leveraging stakeholder relationship X}}
1.5 {{Activity component incorporating community asset Y}}Phase 3: Community-Informed Indicator Development
Time: 60-90 minutes
Step 7: Develop Goal-Level Indicators
Create 1-2 indicators grounded in regional statistics: "Youth unemployment decreases from 45% to 35% by project end."
Step 8: Create Purpose-Level Indicators
Develop 2-3 indicators guided by affinity analysis.
Step 9: Specify Output-Level Indicators
Create 1-2 indicators per output, within your control.
Step 10: Design Activity-Level Indicators
Track implementation quality with indicators for funder and community.
Phase 4: Verification and Assumption Planning
Time: 45-60 minutes
Step 11: Plan Community-Appropriate Verification Methods
| Element | Specify For Each Indicator |
|---|---|
| Primary Method | Data collection approach building on stakeholder relationships (surveys, interviews, observations, records review) |
| Secondary Source | Verification leveraging existing community systems (official records, third-party reports, participatory validation) |
| Frequency | Timing that respects community rhythms and capacity (monthly, quarterly, annual) |
| Cost-Effectiveness | Approaches that don't overwhelm community partners or project budget |
Step 12: Convert Theory of Change Assumptions to Risk Management
Make each assumption observable and assign a mitigation action.
Step 13: Integrate Stakeholder Relationships into Monitoring
Assign monitoring to the stakeholders best placed to track it.
Phase 5: Validation and Finalization
Time: 30-45 minutes
Step 14: Test Logframe Logic
Four Logic Tests
- Vertical Logic: Activities lead to outputs, to purpose, to goal.
- Horizontal Logic: Indicators measure each objective.
- Community Logic: Framework reflects community priorities.
- Implementation Logic: Realistic given your resources.
Step 15: Community Validation of Complete Logframe
Confirm indicators reflect stakeholder definitions of success.
Step 16: Document Integration and Prepare for Activity Design
Document Problem Tree-to-Logframe connections for Activity Design.