A theory of change lays out the logical chain between what an organization does and the change it’s trying to produce — the assumptions, activities, and conditions that connect a program’s actions to its intended outcomes. For NGOs and social enterprises across MENA and Africa, a clear theory of change is often what funders look for before evaluating anything else in a proposal.
Making Assumptions Explicit
The most valuable part of a theory of change is often the assumptions it forces an organization to state explicitly — why a given activity is expected to lead to a given outcome. Leaving these assumptions implicit makes it harder to diagnose why a program isn’t producing expected results. When a program underperforms, an explicit assumption gives a specific, testable place to start looking — was the assumption wrong, or was the assumption right but the activity poorly executed? Without that specificity, review conversations tend to default to general explanations that don’t actually point toward a fix.
Distinguishing a Theory of Change From a Logframe
A theory of change and a logframe often get treated as interchangeable, but they serve different purposes. A logframe is typically a compact grid mapping activities to outputs to indicators — useful for tracking and reporting, but thin on the reasoning that connects one to the next. The change model itself is where that reasoning lives: the narrative and causal logic explaining why an activity is expected to produce a given result. Organizations that build a logframe without ever building the underlying model behind it often end up with indicators that look reasonable individually but don’t add up to a coherent explanation of how the program is actually meant to work.
Avoiding an Overly Linear Model
Real change rarely moves in a straight line from activity to outcome. A theory of change that accounts for external factors and feedback loops — rather than presenting a purely linear causal chain — holds up better under funder scrutiny and better matches how change actually happens in complex environments. Context shifts — a policy change, an economic shock, a shift in community leadership — can alter how an activity translates into an outcome partway through a program’s life, and a rigid linear model has no natural place to register that shift. Building in room for external factors from the outset makes it easier to explain a change in results later without the whole framework looking like it failed.
Common Failure Points in Practice
A few patterns show up repeatedly in models that don’t hold up under scrutiny. One is scope that’s too broad — trying to explain how a single program contributes to a sweeping, multi-year outcome, with so many intervening steps that the connection becomes unfalsifiable either way. Another is an outcome level pitched too high relative to what the organization can actually influence, let alone control, which sets up a mismatch between what’s claimed and what can realistically be evidenced. A third is treating the exercise as a one-time document produced to satisfy a funder’s proposal template, then filed away and never referenced again once the program is underway.
Who Should Be in the Room When It’s Built
The quality of a theory of change often depends less on the format used than on who was involved in building it. A model built solely by senior leadership, without input from program staff who deliver the work day to day, tends to miss operational realities that only show up at the point of delivery. Involving field staff, and where possible the communities a program serves, surfaces assumptions that wouldn’t otherwise get questioned — about what a target population actually wants, or how a proposed activity is likely to be received in a specific context. This doesn’t have to slow the process down significantly, but skipping it tends to produce a model that reads well on paper and performs less predictably in practice.
Connecting Theory of Change to Measurement
A theory of change is only useful if it’s tied to specific indicators at each stage — otherwise it remains a conceptual diagram disconnected from actual program data. Impactedia’s Insights Lab works with clients to build measurement frameworks directly off this kind of model rather than treating the two as separate exercises. This alignment matters because measurement frameworks built independently of the underlying logic tend to track what’s easy to count rather than what the model actually claims is happening — a gap that only becomes obvious once funders start asking why the indicators don’t seem to explain the results.
Using a Theory of Change to Align Multiple Programs
Organizations running several programs at once sometimes build a separate model for each one, with little connection between them. A higher-level version — one that shows how individual program-level models ladder up to the organization’s broader mission — helps leadership see where programs reinforce each other and where they’re working at cross-purposes without anyone having noticed. This is particularly useful during strategic planning or when deciding where to allocate limited resources across competing programs, since it makes the trade-offs between programs visible in a way that isolated, program-specific documents don’t.
Revisiting the Theory as Evidence Accumulates
A theory of change built at a program’s launch should be revisited as real data comes in — some assumptions will hold, others won’t. Organizations that treat it as a living document, rather than a one-time proposal artifact, adapt program design more effectively over time. A model that hasn’t changed after several years of program data usually isn’t evidence that the original thinking was perfect — more often it’s a sign nobody went back to check.