Library / Systems Engineering Principles Framework
Jump to passage
In this reading

Link to current text

Published source confirmed at last check

Source changed 2026-10-03 10:39:28 UTC · snapshot created 2026-10-03 10:40:04 UTC · last check 2026-10-03 11:45:17 UTC

SYSE.21:2 - Problem

Two shortcuts cause expensive errors. The first treats a standard, certification, tool installation, school name, or public claim as proof that engineering practice changed. The second refuses any action until field-wide prevalence and causal effectiveness have been measured.

The first shortcut can impose a fashionable Method that no representative Work enacts. The second can preserve a costly incumbent after local evidence already supports a bounded trial. Both hide the practical questions: which Method is enacted, which relations carry it forward, who may change the arrangement, what burden moves, and what later engineering consequence would justify retaining or stopping it?