Design tips

Outputs vs outcomes: a clarity check

A short note to deepen Lesson 4: Theory of Change.

Abayomi Ogundipe

Abayomi Ogundipe

2 min read
Outputs vs outcomes: a clarity check

Many project plans mix outputs and outcomes. Outputs are what you deliver. Outcomes are what changes because of it. If you confuse the two, your Theory of Change will look impressive but fail in practice.

I use this approach in my own project design work, and it helps teams stay aligned as the project evolves.

Use this check.

Ask: Can we count it immediately?

  • If yes, it is likely an output.
  • If it requires time and behavior change, it is likely an outcome.

Examples:

  • "300 teachers trained" is an output.
  • "Improved teaching quality" is an outcome.

Ask: Who is responsible?

  • Outputs are mostly in your control.
  • Outcomes depend on how people use what you deliver.

Try this exercise: list three lines from your ToC and label each as output or outcome. If you hesitate, add a time marker. Outputs happen during delivery. Outcomes show up after delivery.

Once you label them correctly, you can design activities that actually support change. It also helps you choose the right indicators later.

In Lesson 4 🎥, I walk through this inside the toolkit. Watch the lesson video to learn more.

Outcomes should describe change in behavior, capacity, or conditions. A simple pattern is "people are able to" or "systems are able to." If you cannot write it that way, it is likely still an output. Another check: outcomes should take longer than the activities that produce them. If you can complete it in a day, it is not an outcome. Add a time marker to keep yourself honest.

If you are unsure, write the statement and add "so that" after it. If a behavior change follows, it is an outcome.

Diagram

Outputs vs Outcomes - A Clarity Check

graph TB Statement["📋 YOUR ToC STATEMENT

Is this an output
or an outcome?"] Q1{"Can we count it
immediately?"} Q2{"Who is
responsible?"} Q3{"When does it
show up?"} subgraph OutputBox["📦 OUTPUT"] OutputDef["What you DELIVER

• In your control
• Happens during delivery
• Can complete in a day"] OutputEx["Example:
'300 teachers trained'"] end subgraph OutcomeBox["🎯 OUTCOME"] OutcomeDef["What CHANGES because of it

• Depends on how people use
what you deliver
• Shows up after delivery
• Requires time and behavior change"] OutcomeEx["Example:
'Improved teaching quality'"] end Pattern["📝 OUTCOME PATTERN

'People are able to...'
'Systems are able to...'

If you cannot write it
this way, it is likely
still an output"] SoThatTest["🔗 'SO THAT' TEST

Add 'so that' after
your statement

If a behavior change follows,
it is an outcome"] Exercise["✅ TRY THIS

List 3 lines from your ToC
Label each: Output or Outcome

If you hesitate, add a time marker
Outputs = during delivery
Outcomes = after delivery"] Statement --> Q1 Q1 -->|Yes| OutputBox Q1 -->|No, requires time| OutcomeBox OutputBox --> Q2 OutcomeBox --> Q2 Q2 -->|Mostly your control| OutputBox Q2 -->|Depends on others| OutcomeBox OutcomeBox --> Q3 Q3 -->|During activities| OutputBox Q3 -->|After activities| Pattern Pattern --> SoThatTest SoThatTest --> Exercise style Statement fill:#F6F6F6,stroke:#737373,color:#2A2A2A style Q1 fill:#F8CC1B,stroke:#CA8A04,color:#2A2A2A style Q2 fill:#F8CC1B,stroke:#CA8A04,color:#2A2A2A style Q3 fill:#F8CC1B,stroke:#CA8A04,color:#2A2A2A style OutputBox fill:#FED7AA,stroke:#F37324,color:#2A2A2A style OutputDef fill:#FDBA74,stroke:#F37324,color:#2A2A2A style OutputEx fill:#FDBA74,stroke:#F37324,color:#2A2A2A style OutcomeBox fill:#D9F99D,stroke:#72B043,color:#2A2A2A style OutcomeDef fill:#BBF7D0,stroke:#72B043,color:#2A2A2A style OutcomeEx fill:#BBF7D0,stroke:#72B043,color:#2A2A2A style Pattern fill:#FEF3C7,stroke:#F8CC1B,color:#2A2A2A style SoThatTest fill:#FEF3C7,stroke:#F8CC1B,color:#2A2A2A style Exercise fill:#007F4E,stroke:#00b369,color:#fff,stroke-width:3px