Theory of Change, Explained — Without the Jargon

Every time a new grant call opens, someone on the team reopens the theory of change document from the last submission and tries to retrofit it. It never quite works, and reviewers can tell.

A theory of change is not a format. It is a way of thinking about cause and effect that reviewers are trained to pressure-test. Here is the short, honest version.

What a theory of change is actually for

A theory of change answers one question: if we do these activities, what is the chain of events that leads to the impact we are claiming?

It is not a list of activities. It is not a logframe. It is the causal story behind both.

The four layers

1. Activities. What we actually do — train, build, fund, convene.
2. Outputs. The direct, countable results — number of people trained, schools built, grants disbursed.
3. Outcomes. The changes in behavior, policy or systems that follow from the outputs.
4. Impact. The long-term change in condition — lower mortality, higher literacy, higher income.

Most bad theories of change conflate outputs with outcomes. "We trained 500 health workers" is an output. "Those workers now correctly diagnose malaria in 85% of under-5 cases" is an outcome. Reviewers hate it when teams can't tell the two apart.

The assumptions line is where proposals live or die

Between each layer sits a set of assumptions — things that must be true for the next layer to happen. A theory of change that names these honestly is much stronger than one that pretends they don't exist.

Examples:

• Between training and behavior change: workers must have the tools, supplies and supervisor support to apply what they learned.
• Between outcome and impact: the improved diagnosis must translate into treatment, which requires functioning supply chains.

If an assumption is actually fragile in your context, say so. Describe how you will monitor and mitigate it. Reviewers reward that honesty.

Three common traps

1. The jump. Going from "we train 500 teachers" straight to "literacy improves 20%" with no connecting tissue.

2. The checklist. A theory of change padded with activities that don't actually relate to the claimed outcomes — usually because internal stakeholders want their work represented.

3. The unfalsifiable. A theory of change so general it could justify any activity. If your theory of change works for your program and your competitor's, it is too broad.

How to pressure-test yours

Before submission, run each claim past three filters:

• Counter-example. Can I describe a situation where my activities happen but the outcome does not? If so, name the assumption that fills the gap.
• Evidence. Is there published research, programmatic evidence or internal data behind the claimed link? Cite it.
• Reversibility. Is there a way the causal chain could run backwards or sideways? (E.g., training improves knowledge, but knowledge doesn't always predict behavior.)

Fix the weak ones. Don't hope the reviewer won't notice.

One page, then expansion

Start with a one-page theory of change: activities → outputs → outcomes → impact, with assumptions between. Expand only where needed. Reviewers prefer a tight one-pager to a decorative three-page diagram nobody can read.

Writing a major proposal? We build theories of change that defend themselves, alongside full proposals and logframes. Brief us on the grant.