Simple system

The Devil’s Advocate™ →Go uptown Simple systems: simple systems are situations where essentially inanimate objects interact with each other in ways that are fully understood. Lego is a simple system. So is a cake recipe, or a bungee jump. The components of a simple system don’t fight back. Simple systems are therefore predictable. They can only go wrong if components fail or you don’t follow instructions. In either case they fail in predictable ways. As such, simple systems are suitable for checklists, recipes etc, where algorithms can overcome the hubris that will surely rain down on the heads of those who treat simple processes as trivial. Disinfecting your instruments before performing heart surgery, for example, is a simple step to take, but not a trivial one. In which the curmudgeonly old sod puts the world to rights. Index — Click ᐅ to expand: The Devil’s Advocate Tell me more Sign up for our newsletter — or just get in touch: for ½ a weekly 🍺 you get to consult JC. Ask about it here.

in the pantheon of controlled systems, simple systems are the easiest. They are fully scoped out, “solved” systems where inanimate objects may interact with each other, but do so according to settled maxims, and even component failures can be anticipated and pre-solved. Other than when components fail (for example, a snapped bungee rope, or stale yeast that doesn't rise) the components interact in linear, binary ways.

Managing a simple system involves no greater skill than competently following a comprehensive set of instructions in time to accommodate any actions or reactions in the system. There is usually limited “if/then” conditionality (except where a component fails. On operator doesn’t typically have to react “depending on what the system does”, and so skill, experience and expertise are of limited additional value, beyond bringing greater speed and efficiency to operation of the process.

Simple systems can form part of or interact with complicated and complex systems. It is here where the fun begins.