Definition
Assumptions are conditions, circumstances, or events outside the programme's direct control that must remain true for the programme's results chain to work as intended. If assumptions fail, the programme may not achieve its goals even if it implements perfectly. Assumptions are different from inputs and activities; they're not something the programme provides, but rather background conditions that must exist. In logframes, assumptions typically appear in a column beside the results chain showing which assumptions support the link between each level (from inputs to activities to outputs to outcomes).
Why It Matters
Making assumptions explicit is powerful because it forces you to think beyond your control. A health education programme might assume that beneficiaries have access to the health services being promoted; if that assumption fails (clinics are too far away, too expensive), promoting those services is pointless. An agriculture programme assumes beneficiaries have land to farm; in contexts of land insecurity, that assumption may not hold. By naming assumptions upfront, you can: (1) monitor whether they remain true, (2) design programme activities to address critical assumptions that might fail, and (3) decide if the context is appropriate for your approach. Ignoring assumptions is risky; programmes often fail not because of poor implementation but because core assumptions didn't hold.
In Practice
When developing a logframe, you work through each level and ask: "For this to happen, what must be true?" For example: "If we train health workers and they return to their communities, what must be true for them to actually use their training?" Assumptions might include: "health workers are valued in their communities," "they have time to use new practices," or "they won't be pressured to use only cheap treatments." You then identify which assumptions are critical (meaning if they fail, the whole programme fails) and design monitoring around those. Some programmes actively address assumptions. If the assumption is "beneficiaries can afford the improved practice," the programme might include a component addressing affordability. Others simply monitor and adapt if assumptions prove false.
Related Topics
- Theory of Change, assumptions are explicit in well-developed ToCs
- Logframe, assumptions column sits alongside the results chain
- Risks, related concept covering threats to success
- Adaptive Management, adjusting approach when assumptions fail
- Monitoring, tracking whether assumptions remain valid