SYSE.9:1 - Problem Frame

Whole-System decisions combine results from unlike practices. For example, controller selection may depend on refrigeration performance, electrical protection, control stability, maintainability, acoustics, and safety. Each specialist result can concern a different boundary, configuration, interval, characteristic, evidence standard, and authority relation.

A project loses these differences when it exchanges department names and documents. Recurring examples are an architect assumed to decide every cross-cutting question, a safety specialist asked to approve a design beyond the available evidence, an AI Agent’s report treated as the decision, and a scheduled review treated as completed Work.

The opposite failure is administrative overload. For example, a small calculation acquires a responsibility matrix, fixed role catalogue, approval workflow, and document template, yet the receiving engineer still cannot say what result would change the decision. The remedy begins with the engineering question, not with an organization chart.