methodatlas
Session Builder

Plan my session

Plan a concrete work block with agenda, roles, preparation, and a copyable result artifact.

Method session2-6 hWorkshopTheory of Change Map

Session: Theory of Change

The plan translates the method into a concrete facilitated work block. Your inputs flow directly into the session brief and work artifact.

Derived automatically

Method session with 4-12. The plan uses the existing method logic and the runsheet.

Runsheet
Participation logic
Team round, shared work and alignment

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome logic
Finish artifact

The session works directly toward Theory of Change Map. After the session, the artifact should be shareable, reviewable, or reusable.

  1. 1

    Phase 1: Formulate impact

    20-30 min

    Formulate long-term impact as an observable end state (typically 3-5 years). Be specific per stakeholder: which state is intended. Support it with measurable indicators. Hint: Impact is not mission. Mission is direction, impact is observable state. "Improve education" is mission; "reduce school dropout share in region X from 12% to 7%" is impact.

    FacilitatorTheory of Change Map
  2. 2

    Phase 2: Derive outcomes backward

    30-45 min

    For each impact statement, ask which behavior or state changes must happen before it. Build outcomes as a chain (long-term -> mid-term -> short-term). Hint: Outcomes are changes in stakeholders, not what we do. "Parents attend workshops" is output; "parents apply new parenting techniques" is outcome.

    FacilitatorAssumptions
  3. 3

    Phase 3: Outputs and activities

    30-45 min

    For each outcome, note which outputs (countable results of activities) are required and which activities produce these outputs. Defer inputs (resources) until the end. Hint: An activity does not automatically produce an outcome. Check assumptions for every Output -> Outcome connection, because this is where the break usually occurs.

    FacilitatorOutcome Measures
  4. 4

    Phase 4: Mark assumptions explicitly

    30-45 min

    For each arrow in the diagram, mark assumptions with assumption stickers: what must be true for the impact to happen (causal assumption, context assumption, resource assumption)? Hint: Assumptions are where programs usually fail. If no assumptions are marked, the group is documenting a wish, not a theory.

    FacilitatorTheory of Change Map
  5. 5

    Phase 5: Measurement points and risks

    30-45 min

    Define at least one measurement point per outcome and impact: indicator, data source, frequency. For each critical assumption, add a risk sticker with likelihood and damage value. Assign owners for measurement and risk monitoring. Hint: Measurement points without data source are wishful thinking. If data must first be collected, that collection is itself an output, not something that just happens.

    OwnerAssumptions
  6. 6

    Publish artifact

    10 min

    Check the artifact for completeness, define location, set version or status, and name review recipients.

    OwnerTheory of Change Map
Usable artifact

Session Brief

For invitations, boards, tickets, PR descriptions, or workshop notes.

session-brief.md

Session Brief: Theory of Change

Goal

Artifact: Theory of Change Map

Working Question

How do the planned activities lead through outputs and outcomes to long-term impact, and which assumptions and risks do we need to test and measure?

Context

Mission or program idea in one paragraph; existing impact assumptions; known data or studies about comparable programs; time horizon (typically 3-5 years for impact).

Setup

  • Format: Method session
  • Duration: 2-6 h
  • Mode: Workshop
  • Participants: One facilitator with ToC experience; four to twelve participants from program leadership, operations, domain, evaluation; one scribe for assumptions and measurement points.
  • Owner: One facilitator with ToC experience
  • Participation mode: Team round, shared work and alignment
  • Outcome logic: Finish artifact

Participation Logic

Use the session for shared understanding. Contributions are collected visibly, assumptions are aligned, and open differences remain traceable in the artifact.

Outcome Logic

The session works directly toward Theory of Change Map. After the session, the artifact should be shareable, reviewable, or reusable.

Input

Large whiteboard or Miro board with columns from right to left (Impact, Outcomes, Outputs, Activities, Inputs); sticky notes in four colors; markers for assumption stickers and risk symbols; timer.

Preparation

Set up five columns on the board and work from right to left. Keep an example row visible (Activity -> Output -> Outcome -> Impact). Rule: think backward, impact is the starting point, not the endpoint.

Agenda

  1. Phase 1: Formulate impact (20-30 min) Owner: Facilitator Action: Formulate long-term impact as an observable end state (typically 3-5 years). Be specific per stakeholder: which state is intended. Support it with measurable indicators. Hint: Impact is not mission. Mission is direction, impact is observable state. "Improve education" is mission; "reduce school dropout share in region X from 12% to 7%" is impact. Output: Theory of Change Map

  2. Phase 2: Derive outcomes backward (30-45 min) Owner: Facilitator Action: For each impact statement, ask which behavior or state changes must happen before it. Build outcomes as a chain (long-term -> mid-term -> short-term). Hint: Outcomes are changes in stakeholders, not what we do. "Parents attend workshops" is output; "parents apply new parenting techniques" is outcome. Output: Assumptions

  3. Phase 3: Outputs and activities (30-45 min) Owner: Facilitator Action: For each outcome, note which outputs (countable results of activities) are required and which activities produce these outputs. Defer inputs (resources) until the end. Hint: An activity does not automatically produce an outcome. Check assumptions for every Output -> Outcome connection, because this is where the break usually occurs. Output: Outcome Measures

  4. Phase 4: Mark assumptions explicitly (30-45 min) Owner: Facilitator Action: For each arrow in the diagram, mark assumptions with assumption stickers: what must be true for the impact to happen (causal assumption, context assumption, resource assumption)? Hint: Assumptions are where programs usually fail. If no assumptions are marked, the group is documenting a wish, not a theory. Output: Theory of Change Map

  5. Phase 5: Measurement points and risks (30-45 min) Owner: Owner Action: Define at least one measurement point per outcome and impact: indicator, data source, frequency. For each critical assumption, add a risk sticker with likelihood and damage value. Assign owners for measurement and risk monitoring. Hint: Measurement points without data source are wishful thinking. If data must first be collected, that collection is itself an output, not something that just happens. Output: Assumptions

  6. Publish artifact (10 min) Owner: Owner Action: Check the artifact for completeness, define location, set version or status, and name review recipients. Output: Theory of Change Map

Closeout

  • Update result artifact: Theory of Change Map
  • Define location, version, and review recipients.
  • Define owner, next step, and review date.
Usable artifact

Work artifact

Pre-filled starting point based on the matching template.

work-artifact.md

Theory of Change Map: Theory of Change

Working Question

How do the planned activities lead through outputs and outcomes to long-term impact, and which assumptions and risks do we need to test and measure?

Context

Mission or program idea in one paragraph; existing impact assumptions; known data or studies about comparable programs; time horizon (typically 3-5 years for impact).

Participants

  • Owner: One facilitator with ToC experience
  • Participants: One facilitator with ToC experience; four to twelve participants from program leadership, operations, domain, evaluation; one scribe for assumptions and measurement points.

Input

Large whiteboard or Miro board with columns from right to left (Impact, Outcomes, Outputs, Activities, Inputs); sticky notes in four colors; markers for assumption stickers and risk symbols; timer.

Template

Theory of Change Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Theory of Change Map:
  • Assumptions:
  • Outcome Measures:

Open questions

  • ...

Next step

Owner, date, success signal.

Completion Check

  • Theory of Change Map is complete enough for review:
  • Location:
  • Version / status:
  • Review by:
  • Next step:

Next Step

  • Review result
  • Mark open questions
  • Schedule review or decision
Template base

Theory of Change Working Template

View templateCompact working template for Theory of Change with context, input, output artifacts, and next step.
canvas

theory-of-change-working-template.md

Compact working template for Theory of Change with context, input, output artifacts, and next step.

Theory of Change Canvas

Context

What is this method used for?

Core question

Which question should be answered at the end?

Input

Which data, observations, or materials are available?

Working area

  • Area 1:
  • Area 2:
  • Area 3:
  • Relationships / patterns:

Output artifacts

  • Theory of Change Map:
  • Assumptions:
  • Outcome Measures:

Open questions

  • ...

Next step

Owner, date, success signal.

Ready to use when
  • Working question, owner, and target artifact are visible.
  • The result fits Theory of Change Map.
  • Own ToC per program with date. Annual reviews with update section (which assumptions were confirmed, refuted, modified). On strategy change, create a new version and keep the old one as snapshot.
  • Open questions are noted as follow-ups.
  • The next review or decision point is scheduled.