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 05:29:54 UTC · snapshot created 2026-10-03 05:30:57 UTC · last check 2026-10-03 06:00:20 UTC

SYSE.25:4.2 - Locate the burden without inventing its cause

Separate active practitioner work, waiting, error, rework, diagnosis and assistance. Follow the burden across users and providers rather than optimizing one team’s visible time. Preserve missing observations; do not turn an unobserved abandoned attempt into a success.

Ask what actually obstructed the result. Possibilities include an unavailable enabler, an unreliable technical operation, unclear interaction, inadequate capacity, a missing authorized decision, an invalid Method or an unsettled desired result. These lead to different work.

Ask the person authorized to grant the missing permission. Return a missing professional Method or acceptance meaning to the relevant engineering specialist. Consider platform repair when the enabling System or supported use can change the observed difficulty. Use SYSE.12 when the broader platform’s actual participation, capability or provision must first be established.