Why do simple rules so often fail to control complicated situations? A cybernetician named W. Ross Ashby gave a precise answer in the 1950s, and it has quietly shaped how people think about control ever since. His law of requisite variety states that only variety can absorb variety. To manage a system, your range of possible responses must match the range of situations the system can throw at you. When it does not, control breaks down.
What variety means here
In this context, variety means the number of distinct states something can be in. A light switch has two states. A weather system has an enormous number. Ashby law says that to regulate a system with many possible states, the controller needs a comparable number of possible responses. If the environment can surprise you in a hundred ways and you have only three moves, ninety-seven of those surprises will get through.
Why oversimplified control fails
This is why rigid rulebooks struggle in fast-changing conditions. A single fixed procedure has low variety, so it can only handle the situations it was written for. The moment reality produces something outside that list, the procedure has no matching response and the system slips out of control. Adding more rules helps only up to a point, because a long list of rigid rules is still brittle when the world does something none of them anticipated.
Two ways to restore the balance
Ashby law implies two paths back to control. You can increase your own variety, giving yourself more and more flexible responses through skilled people, adaptable tools, and the discretion to improvise. Or you can reduce the variety the system throws at you, by simplifying the environment, setting standards, or filtering out disturbances before they reach you. Effective organizations use both, matching their internal flexibility to the complexity they choose to take on.
A practical lens
The law offers a sharp diagnostic question. When something feels out of control, ask whether the situation has too much variety, or whether your responses have too little. A support team drowning in unusual cases either needs more capable agents with more latitude, or a product simple enough to generate fewer strange cases. Naming which side of the balance is broken points you toward the right fix instead of simply demanding more effort.
Requisite variety is a reminder that control is a relationship, not a property. You do not control a system by being powerful. You control it by being at least as varied as the thing you are trying to manage.
Discussion