Outcome versus output
Framing work as the change wanted in the world (outcome) instead of the thing to be built (output). Outcomes define success and leave the path open; outputs do neither. This is the central translation move of engineering strategy.
Evidence grade: practice A widely adopted practitioner model with clear provenance.
Use it when
Setting goals at every level; testing a roadmap item by asking why it is there; writing objectives that are not task lists.
Where it stops working
Some work is legitimately shaped as output, such as compliance or contractual deliverables. And an outcome nobody can influence is a wish rather than a goal.
Where the standard uses it
- SV-1Engineering strategyTranslating business goals into technical direction, and writing it down.
Used alongside it
- Strategy, vision, and roadmap practice
- The connecting thesis practice
- Writing the strategy down practice
Cite this model
Chicago, BibTeX and licence →Engineering Management Academy. (2026). Outcome versus output. In Engineering Management Academy Body of Knowledge (Version 3.1, TEC.outcome-versus-output). https://www.engineeringmanagement.academy/body-of-knowledge/techniques/outcome-versus-output