From logframe to learning: making your theory of change useful

A theory of change describes how you believe change will happen. A logframe summarises what you will measure. The gap between the two is where most MEL systems lose their value.

The problem with a static diagram

Many theories of change are drawn for a proposal and never revisited. They list outputs, outcomes and assumptions in boxes, with arrows that imply certainty. Reality is messier.

A useful theory of change is a set of testable claims: if we do this, and if these conditions hold, then we expect this change. Each claim can be checked.

Turn assumptions into questions

Take each assumption in your logframe and write it as a question the project can answer during implementation.

• Assumption: local government will share routine data.
• Question: are the agreed monthly data submissions arriving on time, and if not, why?

• Assumption: trained staff will remain in post.
• Question: what proportion of trained staff are still in their roles after six months?

Those questions belong in your quarterly review, not in an annual report.

Use the logframe as a map, not a cage

The logframe is a summary, not the whole system. Keep a short learning log alongside it where the team records surprises, adaptations and the evidence behind them. Over a project cycle, that log is often the most useful document you have.

Review the diagram once a year

At least annually, bring the team together and ask which arrows in the theory of change still hold. Update the diagram and note what changed. This keeps the model honest and gives you material for donor conversations about adaptation.

If you are starting from scratch, our [logical framework template](/product/logical-framework) and [MEL plan template](/product/monitoring-evaluation-and-learning-mel-plan-template) are designed to work together.