Here is a pattern that plays out across the development sector: an organisation invests weeks developing a beautiful Theory of Change. Stakeholders are consulted. Pathways are mapped. Assumptions are identified. The ToC is printed in colour for the proposal. And then it sits in a drawer for three years until someone asks for it during the evaluation.
This pattern represents one of the sector's most expensive forms of waste. Not because the ToC was wrong—but because it was never used.
Why ToCs Die
The most common reason is simple: nobody builds in a process for reviewing them. Once the programme starts, operational pressures take over. Monthly reports track activities and outputs against indicators. Quarterly reviews focus on burn rates and deliverables. The strategic questions that the ToC is designed to answer—Is our theory of change still valid? Are our assumptions holding? Are we seeing the changes we expected?—never get asked.
A second reason is fear. If the ToC turns out to be wrong — perhaps falling into one of the common ToC pitfalls — what does that mean for the programme? For the team? For the relationship with the donor? The honest answer—that learning your theory is wrong is valuable information—requires a level of psychological safety that many organisations lack.
The Adaptive Management Approach
Adaptive management treats programme implementation as a series of learning cycles rather than a fixed plan to be executed. The core cycle is: act → observe → reflect → adapt → act again.
DFID (now FCDO) pioneered adaptive programming through initiatives like the Global Learning for Adaptive Management (GLAM) programme. USAID's Collaborating, Learning, and Adapting (CLA) framework provides a structured approach to building adaptation into programme design.
The key insight is that adaptation is not a sign of failure—it is a sign of learning. Programmes that never change course are not well-managed; they are rigid. For programmes operating in complex environments, this flexibility is not optional — it is essential.
Building Review Triggers
- Time-based: Quarterly ToC reviews built into the programme calendar
- Evidence-based: Automatic review when monitoring data shows unexpected patterns
- Context-based: Review when significant external changes occur (policy shifts, crises, elections)
- Milestone-based: Review at key programme transitions (pilot to scale, phase changes)
What a ToC Review Looks Like
A quarterly ToC review need not be elaborate. In 2-3 hours, a programme team can address: Which assumptions have we tested or observed? What evidence supports or contradicts our causal pathways? What unexpected changes are we seeing? What should we do differently?
The discipline is in asking these questions regularly and acting on the answers. Document decisions and their rationale. Track adaptations over time. Share learning with stakeholders, including donors. Systematically testing your assumptions provides the evidence base for these reviews.
"The best Theory of Change is one that has been proven wrong in several places and updated accordingly. That's not failure—that's the scientific method applied to development."
When to Pivot vs Persist
Not every piece of contradictory evidence warrants a change in strategy. The challenge is distinguishing between signal and noise—between evidence that your theory is fundamentally wrong and evidence that implementation needs adjustment.
Persistence is warranted when: the evidence is preliminary, the theory is supported by strong prior evidence, and the contradictory signal could be explained by implementation factors. Pivoting is warranted when: multiple sources of evidence converge, the assumptions underlying your pathway have clearly failed, and continuing the current approach would waste resources.
Making It Practical
Start with what you have. You do not need a perfect adaptive management system to begin. Schedule your first ToC review. Ask the hard questions. Document what you learn. Share it with your donor. Most funders are more receptive to honest learning than practitioners assume. And use tools like ImpactMojo's ToC Builder to make the review process visual and collaborative.
The goal is not perfection. It is a habit of asking whether your understanding of change still matches reality—and having the courage to update it when it does not.