Systems Thinking and Holistic Analysis
Domain 2 tests holistic analysis: setting system boundaries, recognizing emergence, and reasoning about feedback instead of decomposing a problem into isolated parts and assuming the parts explain the whole.
Core rules and concepts
- A system is a set of interacting elements organized to achieve one or more stated purposes. The boundary is a modeling choice; the environment contains everything that interacts across that boundary.
- Emergence means system-level properties appear that no element possesses alone-safety, latency, throughput, usability.
- Hierarchy means systems contain subsystems and sit inside supersystems. Each level has its own objectives, interfaces, and evidence.
- Feedback, delays, and nonlinearity produce counterintuitive behavior. Reductionism is useful for analysis but insufficient for interaction effects.
Worked example
A city retimes traffic lights to reduce average wait at each junction. Isolated junction delays fall, but arterial progression degrades and total corridor travel time rises. A holistic analysis models the corridor as a queueing network with platoon dispersion. It shows the local optimum trades against the system objective. Reasoning: the metric and the boundary must match the purpose. Optimizing junction wait is not the same as optimizing mobility.
Traps that cost marks
- Drawing the boundary around the org chart rather than around the interactions that matter.
- Optimizing a local metric and declaring system success.
- Ignoring feedback, delays, and human behavior in the operational environment.
- Confusing a diagram with a validated system model.
- Treating emergence as a surprise instead of a design concern.
Key points
- Boundary is a purposeful choice.
- Emergence creates system-level properties.
- Hierarchy changes objectives and evidence.
- Feedback defeats local optimization.
- Match the metric to the system purpose.