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 05:40:05 UTC

SYSE.17:2 - Problem

Stakeholder lists are commonly built from cues such as visibility, power, contracts, interfaces, or organization charts. Those cues can miss, for example, quiet, weakly represented, future, indirect, non-human, or cross-boundary consequence bearers. The opposite error is to call every mentioned party affected without naming a change, evidence basis, or decision use.

Diagrams create another error: a plausible arrow from a proposed change to a possible bearer is reported as an actual relation or causal effect. Treat the arrow as a representation and ground its participants and predicate separately. Scale words such as person, team, organization, society, and ecosystem provide candidate scopes; recover actual Systems, whole–part relations, causal relations, and observed changes from their own evidence.

Too little discovery exports cost or harm. Unbounded discovery makes action impossible because every imaginable consequence appears equally real and authoritative.