The Law of Requisite Variety

Written by

Sergio Caredda

Posted on

May 8, 2026

Key Implications of the Law of Requisite Variety

1. Complexity and Control

The law implies that to effectively manage or control a complex system, the controller itself must possess a level of complexity that matches the system it seeks to regulate. If the controller lacks sufficient variety, it will be unable to cope with all possible states of the system, leading to failures or inefficiencies.

This is the biggest limit to monolithic organisational models, which fail to show resilience over time when faced with a variety of conditions. It is also one of the reasons centralised empires have historically suffered, and why democracy continues to work as a system: it operationalises variety by design.

In a business context, the same logic applies. A company operating in a highly dynamic and competitive market needs a diverse set of strategies, tools and decision-making processes to handle different market conditions. A rigid, one-size-fits-all approach is unlikely to be effective. I have seen this pattern in large-scale ERP harmonisations: programmes that eliminated local process variations across multiple countries because the differences looked like inefficiency. The operating model became beautifully uniform. Customer responsiveness deteriorated in markets where those local variations existed for genuine reasons. The "complexity" that had been removed was, in fact, requisite variety the business needed.

2. Adaptive Systems — and the Difference Between Variety and Complication

This law also highlights the importance of adaptability and flexibility in systems design. Systems that are too rigid or too simple may fail to manage more complex or unpredictable environments, whereas systems that can adapt their internal structures or processes to meet environmental challenges are more likely to succeed.

One word of care, though: variety does not mean complication. The two are easily confused and the confusion is expensive. In several cases, variety produces a level of complexity that can only be managed through simplified processes. Complication drives rigidity; what you actually want is adaptability. This is the distinction most managerial responses to complexity get wrong: they reach for either standardisation (which destroys variety) or proliferation (which adds complication). Neither is the right move. Variety is about the range of responses the system can produce; complication is about how complicated the internal mechanism is. You can have one without the other.

For example, in IT security, a system that can only detect and respond to known threats is less effective than one that can adapt to new, unknown threats. A more adaptive security system, capable of recognising patterns rather than enumerating signatures, is required to manage the variety of potential cyber threats — and it does so without becoming more complicated to operate.

3. Organisational Model

The law is often applied to organisational design, where it suggests that an organisation must have sufficient internal diversity — in skills, processes, decision-making structures — to respond to the diversity of challenges it faces in its environment. This diversity might take the form of different functions, specialised teams, cross-functional squads or flexible work processes.

For example, a global corporation operating across multiple countries needs a diverse and flexible organisational structure that can adapt to the unique economic, cultural and regulatory conditions of each market. A centralised, uniform approach may not be sufficient. The practical implication is that distributed decision rights, cross-functional teams and network forms are not organisational fashion. They are structural responses to the variety problem. They exist because someone — explicitly or intuitively — recognised that the environment demanded more variety than the existing hierarchy could produce.

Hamel and Zanini make exactly this argument in Humanocracy, contending that hierarchies structurally lack the variety to regulate complex environments, and that distributed authority is therefore not a progressive preference but a necessity of system design.

4. Decision-Making

In decision-making, the law implies that to make effective decisions in complex situations, a decision-maker needs access to a variety of perspectives, tools and strategies. A decision-making process that lacks variety is likely to be inadequate when addressing complex problems.

More and more, this element of variety has been traced back to the diversity of team members, especially in decision-making contexts. Again, the warning about complication is worth repeating: variety in perspective is what helps; multiplying procedural layers is not.

For example, in crisis management, a team composed of members with different areas of expertise and experience is more likely to devise effective solutions than a homogeneous team with limited perspectives.

5. Systems and Environments

The law also emphasises the interdependence between systems and their environments. For a system to remain viable, it must respond to the variety of challenges presented by its environment. This means that systems must evolve and increase their internal complexity in response to external changes — without sliding into complication for its own sake.

For example, an ecosystem such as a rainforest is highly resilient because of its diversity of species and interactions. This diversity allows it to absorb and adapt to a wide range of environmental changes, maintaining its stability over time. The rainforest is varied; it is not, in any meaningful sense, complicated.

Variety as a Discipline, Not a Metaphor

What has been missing from the management conversation, until recently, is a method. Ashby gave us the principle. Beer extended it through the Viable System Model. But the practical question — how do you engineer variety in an organisation? — has remained surprisingly underdeveloped.

That is starting to change. Schwaninger and Ott published a formal treatment of variety engineering in 2024, defining the twin moves explicitly: attenuate external variety (filter what comes in) and amplify internal variety (expand what you can respond with). In practice, this means something concrete. A regional team that buffers headquarters from local market noise is an attenuator. A cross-functional squad that can reconfigure around a new customer segment is an amplifier. The fact that it took nearly seventy years for Ashby's principle to receive a formal methodological companion should tell you something about how resistant the management discipline has been to this line of thinking.

The AI Angle: A Variety Amplifier Misused

There is one contemporary application of this law worth naming directly. AI has the potential to be a variety amplifier of unprecedented scale: it can extend the response repertoire of a human-machine system without proportionally increasing headcount. New product configurations, new customer segments, new operating models become approachable in ways they were not before.

But most organisations are deploying AI to do the opposite — to standardise, to automate, to reduce the number of distinct responses their systems produce. They are deploying a variety amplifier as a variety reducer. The micro-productivity trap is, at bottom, a requisite variety failure. I have written elsewhere about the design gap — the disconnect between AI capability and organisational redesign — and Ashby's law frames it precisely. The capability is real. The willingness to use it as variety, rather than as further compression, is not.

Applications: Where Requisite Variety Matters in Practice

The concept of requisite variety has, unfortunately, often been applied with a strict focus on control systems. Several large organisations have responded by building large internal control towers — finance, audit, procurement, compliance — sometimes far beyond what the value at stake justifies. This is a distortion of the law: it focuses on complication mirroring, not variety matching. The point is not to replicate complexity; it is to match it with appropriate response capacity.

That is why I would emphasise four areas where this law deserves more deliberate application in organisation design work:

Organisational Flexibility. Build flexibility into structures and processes to handle a wide variety of challenges. This includes cross-functional teams, decentralised decision rights, and a deliberate move away from rigid role design toward skill-based models.
Systems Design. When designing technological or management systems, ensure the system can handle the full range of plausible scenarios. Build in redundancy, design for adaptive feedback, and avoid over-specifying paths that the environment will not respect.
Risk Management. Diversify strategies and tools to cope with the variety of risks. Relying on a single approach leaves the system vulnerable to challenges that fall outside its design assumptions.
Learning. Develop educational and development programmes that equip individuals with a broad range of skills and perspectives, enabling them to adapt to different situations and solve diverse problems. The variety of the organisation is, ultimately, the variety of the people in it.

The “Laws of Organisation Design” Collection. This article belongs to a series focused on the different principles and laws that govern organisational behaviours, decision-making and group work, and that should be taken into account in organisation design projects.

The Laws of Organisation Design

Coming Soon

Law of Alignment
Law of Self-Similarity
Law of Synergy
Law of Minimizing Interface Complexity

Conclusion

The Law of Requisite Variety is a key principle in understanding how systems can effectively manage complexity and change. It asserts that to cope with a complex environment, a system — whether an organisation, a technological system, or a decision-making process — must have sufficient internal variety to match the external variety it faces.

The principle emphasises the need for flexibility, adaptability and diversity within systems to ensure they can respond effectively to a wide range of challenges. The hidden danger, which I keep coming back to, is to veer from variety into complication — something we need to guard against constantly. Variety is the goal. Complication is the trap. The discipline is keeping the two distinct, and treating requisite variety as a design constraint on the same level as cost, governance and scalability when we decide how organisations work.

Ignoring it does not make the constraint disappear. It only makes the failures harder to diagnose.