Skip to main content

Outcome Map

What does success look like — in terms anyone can explain without reading the document?

OUTCOME MAP
════════════════════════════════════════════════════════════

DESIRED OUTCOME

├── Contributing Factors (what enables success)

├── Obstacles (what prevents it)

├── Investigations (questions before committing)

├── Success Measures (binary: did we or didn't we?)

├── Roles (RACI: who decides, who does)

└── Next Actions (momentum within 48 hours)

════════════════════════════════════════════════════════════

The Outcome Map is the first of four flow engineering maps. No execution until the outcome is crisp.

Structure

SectionQuestionQuality Test
Desired OutcomeWhat's the future state?Explainable in 1-3 sentences
Contributing FactorsWhat existing strengths help?Each has evidence
ObstaclesWhat could prevent success?Each has a mitigation
InvestigationsWhat must we answer first?No execution until answered
Success MeasuresHow do we know it worked?Objective and binary
Roles (RACI)Who decides, who does?One Accountable per decision

Gate

Before moving to Value Stream Map:

  • Desired outcome is crisp (1-3 sentences)
  • Contributing factors have evidence
  • Obstacles have mitigations assigned
  • Investigation questions have owners
  • Success measures are objective and binary
  • RACI is complete
  • Next actions are assigned

If any gate is empty, do not proceed.

Context