Laws of Software Engineering · Saying
Saying
Outcome over Output
Build to change something in the world, not to ship a feature.
How to use it. Every piece of work should have a specific change in user behaviour, business result, or system property attached. If shipping it would not change any of those, the work is decoration.
How it gets misused. Stretched to refuse all delivery commitments. Outputs still matter, because outcomes do not happen without them. The success metric is "something changed because we shipped".
Related
- Pattern Build-Measure-Learn Build the smallest thing that tests your idea. Measure what happens. Learn what to do next.
- Framework Jobs To Be Done People do not buy products. They hire products to do a job. Understand the job.
Clusters
- The Lean Product cluster - How to build the right thing.