Requisite Variety

Origin. W. Ross Ashby's Law of Requisite Variety (1956), extensively adopted and applied in Soviet organizational cybernetics by Glushkov, Berg, and the OGAS project team. The law states: "Only variety can destroy variety." Soviet cyberneticians used it as a theoretical basis for critiquing over-centralized control and designing distributed systems.

Mechanism. A regulator can control a system only if the regulator's range of responses matches or exceeds the system's range of disturbances. If the environment has N possible states and the controller has M possible responses with M < N, some disturbances must go uncompensated. The law is a statement about information: control requires a channel from disturbance to response with capacity at least log₂(N) bits. Centralized control fails when the center lacks the variety to match the variety it attempts to regulate.

Procedure. Analyze and design control systems through variety matching: (1) Enumerate disturbances — what distinct states can the environment or system being controlled present? Count distinguishable states relevant to the control objective. (2) Enumerate responses — what distinct control actions are available? Count the controller's repertoire. (3) Compare varieties — if the response variety is smaller than the disturbance variety, the controller is under-specified. Some disturbances will not be compensated. (4) Choose a resolution — either expand the response variety (more control actions, more decision-makers, more sensors), reduce the disturbance variety (buffering, filtering, simplifying the environment), or accept that some disturbances will not be regulated. (5) For organizations — decision-making authority must be distributed to match the variety in the environment. Centralization is control under-specification. Push decisions to where the variety exists. (6) Design information channels — ensure information about disturbances can reach the point where responses are generated with sufficient bandwidth and speed.

Applies to. Organization design. API and system interface design. Regulatory design. Distributed versus centralized architecture decisions. Any system where the designer controls the regulator but not the environment.

Limitations. Variety is counted in distinguishable states, and distinguishability depends on purpose. A regulator with high variety that does not align with disturbance dimensions provides no control. Variety can be attenuated (reduced by aggregation) or amplified (increased by disaggregation); the law governs necessary variety at the point of control, not raw variety in the environment. Counting variety is straightforward for finite discrete systems but requires judgment for continuous or open-ended systems.