On my desk sit two documents. The first looks forward: a guide to building a theory of change, asking how we
think change will happen before we begin. The second looks back: a study that gathers stories of change as it actually occurred, after the programme ends. For years I have watched most organizations hold one of these documents and neglect the other designing with a theory but never measuring it, or measuring without a theory they ever designed against. The truth is that these two documents are not separate. They are the two halves of a single circle.
A theory of change is the promise: our stated narrative of how reality will move. Most Significant Change is the proof: the testimony of those who lived the change, about what actually moved. The first is a hypothesis; the second is a test of that hypothesis. And when we sever them, we lose the most precious thing in development work the ability to learn.
What makes the bridge between them solid is not a rhetorical flourish but a precise conceptual match: both sources use the very same term "domains of change." In a theory of change, we define domains in advance: the three to five arenas where we bet change must happen. In Most Significant Change, domains emerge afterward: the arenas where, from people's stories, we discover change actually happened. The word is identical; the direction is reversed and that is exactly where learning is born.
Imagine you designed a programme assuming the most important domains were economic and academic young people need a job and a degree. Then you gathered their stories, and the personal domain dominated: confidence, courage, a sense of worth. That is precisely what the West Bank study revealed, where the personal domain led 178 stories and was often the seed that preceded economic change. What does that mean? It means your hypothesis was incomplete not wrong, but incomplete. You assumed the road to employment ran through skills; you discovered it runs first through confidence. When that discovery feeds back to revise your theory of change, your next programme becomes smarter.
When the domains you predicted meet the domains you discovered, your hypothesis is confirmed. When they diverge, you have learned. Both are a gain. Convergence gives you confidence in your design; divergence gives you knowledge you did not have. The only failure is not to compare at all to make a promise and never ask whether it was kept.
So the circle closes in steps any leader or organization can walk. We design a theory of change with our community, naming our assumptions and our domains clearly. We implement. We then measure with Most Significant Change, letting the people who lived the experience tell what changed and choose what mattered most. Then the step everyone skips we place the predicted domains beside the discovered ones and ask: where did they match? Where did they diverge? And what does that mean for our assumptions? Finally, we revise the theory and run the cycle again. Specialists call this "adaptive management." It simply means staying in a state of learning while we work.
In the CBR Africa Network, and in our preparations for the Cairo 2026 Congress, I see in this circle more than a technical tool; I see a philosophy for continental work. Networks do not learn merely by collecting quantitative reports, but by connecting what they promised to what people actually lived across many contexts and cultures. This is knowledge management in its purest form: not archiving, but a living cycle of promise, proof, and learning.
A theory of change is a promise we make; Most Significant Change is the proof we seek. The distance between them is not an empty gap to ignore it is the only place where we learn. So ask your organization: do we measure in the same spirit in which we design? And do we have the courage to set our promise beside reality, and learn from the distance between them?
Comments (0)