16-Step Logframe Development Process

Phase 1: Foundation Review and Integration

Time: 30-40 minutes

Step 1: Gather All Module 1 Materials

Pull together Problem Tree (E)/(A) tags, stakeholder map, affinity themes, and Theory of Change.

Step 2: Review Community Validation Results

Extract stakeholder feedback and priorities from your validation sessions, noting that employment can include self-employment and informal work.

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

Translate your Theory of Change into Logframe hierarchy:

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

Convert outputs into measurable outputs with community-defined criteria:

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

Break activities into steps that address a root cause from your Problem Tree:

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: "70% secure livelihoods above living wage within 6 months," balanced by employer confidence in local youth.

Step 9: Specify Output-Level Indicators

Create 1-2 indicators per output, within your control: "300 youth (60% female) complete training" and "80% achieve certification."

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

For each indicator, specify approaches that build on stakeholder relationships:

Step 12: Convert Theory of Change Assumptions to Risk Management

Make each assumption testable: "Government remains supportive" becomes "District office maintains MOU and quarterly meetings."

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

Step 15: Community Validation of Complete Logframe

Walk stakeholders through the framework and confirm indicators reflect their success.

Step 16: Document Integration and Prepare for Activity Design

Document connections from Problem Tree to Logframe, and organize materials for Activity Design.