STEP UP – Decision‑Making Guide

A Guide to Using Findings for Decision‑Making

Turning monitoring insights into smarter planning, stronger delivery, and better outcomes.

Build a culture of adaptive management where evidence drives every improvement.

Illustration: Evidence‑to‑Action Pipeline

Visualize how data flows from monitoring into analysis, decisions, and improved implementation.

Graphic placeholder: Pipeline diagram with stages: “Collect Data → Analyze → Discuss → Decide → Implement Adaptations”. Icons for charts, insights, decisions, and actions.

Leveraging monitoring insights for program improvement

Monitoring is more than tracking—it generates insights that fuel adaptive management. Findings from the PMEF, field visits, and studies should systematically inform improvements across the project.

1. Improving program design

  • Identifying and addressing barriers: Consultants must monitor achievements and propose technical solutions when barriers arise. If a training module underperforms, the team analyzes why and redesigns it.
  • Refining interventions in real time: GESI activities, STEM Framework rollout, and OpenEMIS adoption can be adjusted immediately based on monitoring findings.
  • Piloting and scaling up: The 30‑school STEM Framework pilot will be monitored to refine the model before national rollout.
  • Establishing feedback systems: PRESET feedback loops ensure teacher training insights feed into curriculum and delivery improvements.
Graphic: Adaptive Design Loop

Circular loop showing “Monitor → Reflect → Adjust → Implement → Monitor”. Each step includes examples from STEP UP (e.g., CPD refinement, STEM pilot adjustments).

2. Optimizing resource allocation

  • Evidence‑based budgeting: DMF and GAP progress informs the AWPB. Effective interventions can be scaled; underperforming ones reconsidered.
  • Targeted support: Disaggregated data highlights provinces, schools, or groups needing additional support.
  • Informing procurement: Monitoring EdTech usage ensures future procurement matches real needs and capacity.

3. Enhancing project planning

  • Realistic target setting: Early findings help refine future targets.
  • Adaptive risk management: Monitoring identifies new risks and tests mitigation measures.
  • Capturing lessons learned: Required by the ToR to inform future planning and sector learning.
  • Informing quarterly and annual plans: Reports become the basis for next‑period planning.
Graphic: Evidence‑Driven Planning Cycle

Wheel diagram showing “Monitor → Analyze → Plan → Implement → Monitor” with arrows looping continuously.

Format for a ‘Learning and Adaptation’ meeting

Regular Learning and Adaptation meetings institutionalize evidence‑based decision‑making and ensure findings translate into concrete improvements.

Meeting title:

STEP UP Quarterly Learning and Adaptation Meeting

Frequency:

Quarterly (aligned with reporting cycle)

Participants:

  • PMU leadership
  • PIU heads
  • PIC Team Leaders (International & National)
  • M&E Specialists
  • Technical specialists (GESI, EdTech, STEM)
  • Implementing Agency representatives
Graphic: Meeting Participation Map

Diagram showing PMU at center with spokes to PIUs, IAs, consultants, and specialists.

Meeting agenda (90–120 minutes)

1. Performance review: progress against key indicators (20 mins)

  • Shared understanding of performance using dashboards.
  • Highlight achievements and underperformance.
  • Present disaggregated data (gender, beneficiary group, province).

2. Deep dive: insights from the field and studies (25 mins)

  • Findings from field missions.
  • Results from impact studies or evaluations.
  • Success stories and testimonials.
  • Feedback from PRESET and other systems.

3. Analysis: barriers, bottlenecks, lessons learned (25 mins)

  • Root cause analysis of challenges.
  • Identify replicable successes.
  • Discuss barriers hindering achievements.

4. Decision‑making: proposing and agreeing on adaptations (30 mins)

  • Refine CPD modules.
  • Reallocate specialist support.
  • Adjust quarterly work plans.
  • Propose technical solutions (e.g., simplified reporting templates).

5. Action planning and communication (10 mins)

  • Document decisions and assign owners.
  • Set deadlines and communication plan.
  • Confirm next meeting date.
Graphic: Learning & Adaptation Workflow

Flowchart showing “Review → Discuss → Decide → Assign → Communicate → Implement”.