outcome-based engineering

noun
UK /ˈaʊt.kʌm beɪst ˌen.dʒɪˈnɪə.rɪŋ/
US /ˈaʊt.kʌm beɪst ˌen.dʒəˈnɪr.ɪŋ/

A way of building things where you first decide what result you want, then design it to make that result happen.

The team used outcome-based engineering to make sure their new playground would help kids play together more.


OTHER MEANINGS

2. An engineering approach that judges success by measurable results rather than by the steps taken to get there.

Outcome-based engineering meant the bridge was graded on how safe it was, not on how many materials were used.

3. A method in software and product development where features are planned around the user results they should produce.

With outcome-based engineering, the app team started by asking what users should be able to do, not what code to write.

4. A style of project management that ties engineering decisions to specific, checkable end goals.

Outcome-based engineering kept the project on track because every choice had to point to a clear final result.