Control and complexity: tension in systems design
Fred Hebert: teams pick control or complexity as a worldview, usually without noticing, and that choice quietly sets their code review, SLOs, and incident response. A table to argue with.
Hebert's table sets two worldviews side by side across training, safety, reliability, incident response, and feature work: decompose and control, or accept emergence and steer. His claim is that most organisations never choose; they inherit control, and when it fails they answer with more analysis, which buys fewer but larger incidents. The alternative, expanding complexity-aware mechanisms outward from the parts that resist decomposition, costs an admission that the business is not in control. He leaves three questions for the next design review: if you bet on control, how do you know your observations still describe the system; if on emergence, how do you tell adaptation from drift; and in either transition, what depends on the behaviour you are about to change. We could not answer the first one for our own SLOs.
Comments
Loading comments…