Theories of change have become a ritual in the non-profit and development sectors. Every new program needs one. Every grant proposal requires one. They are drawn up in workshops, approved by boards, and then quietly filed away — consulted once at midterm evaluation, if at all.
This is a shame, because a well-constructed theory of change is one of the most powerful tools an organization can have. It forces clarity about assumptions, surfaces risks before resources are committed, and provides a framework for learning. The problem is not the tool. It is how most organizations build and use it.
The Funder-Driven Trap
Most theories of change are written backward. They start with the funder's requirements and work toward the organization's actual program. The result is a plausible-sounding narrative that satisfies a proposal review panel but provides no real guidance for program staff. It describes what the organization hopes will happen, not what it is actually doing to make it happen.
One education NGO we worked with had a beautiful theory of change mapping how teacher training led to improved student outcomes. The causal chain was elegant. The problem was that the program was actually delivering one-day workshops with no follow-up support — a design that virtually every education study shows has negligible impact on practice. The theory of change and the program logic were living in parallel universes.
Rigor Meets Usability
A useful theory of change passes three tests. First, the causal logic is explicit and evidence-based — each link in the chain should be grounded in research or direct organizational experience. Second, it is brutally honest about assumptions, identifying which links are well-supported and which are bets. Third, it is operational — program staff can look at it and know what they should be doing differently this week.
The organizations that get this right treat their theory of change as a living document, reviewed quarterly against implementation data and adjusted when reality diverges from expectation. It becomes a tool for organizational learning rather than a compliance artifact. And that, ultimately, is the difference between a theory of change that decorates and one that drives.