Viable system model — Organizational Development

Stafford Beer's viable system model (VSM) comes from management cybernetics. It specifies the five functions any organization must perform to remain viable — that is, to survive as an independent entity in a changing environment — and it is recursive: every viable unit contains viable units and is contained in one.

Evidence: Weak. Internally coherent and derived rigorously from cybernetics, with almost no independent empirical validation as a predictive or diagnostic model. Ashby's law of requisite variety is a formal result and is sound; the mapping from it to five organizational systems is an argument, not a finding. Case reports of VSM diagnosis are largely written by advocates.

Use when: diagnosing why an organization is slow to respond, why decisions escalate constantly, or why a "self-managing teams" model is failing.

Do not use when: you need something a general audience will absorb quickly. VSM has the steepest learning curve of any model here.

The five systems

System 1 — Operations: the units that actually do the primary work and produce value. Each System 1 unit is itself a viable system.
System 2 — Coordination: damping oscillation and conflict between System 1 units. Schedules, standards, shared protocols, rotas. Anti-oscillatory, not commanding. Weak System 2 shows up as units tripping over each other.
System 3 — Control: day-to-day management of the whole set of operations; resource allocation, accountability, synergy between units. Looks at the inside and now.
System 3* — Audit: sporadic direct inspection of System 1 that bypasses the normal reporting line. Without it, System 3 knows only what System 1 chooses to report.
System 4 — Intelligence: looking outside and forward. Environment scanning, strategy, adaptation, research.
System 5 — Policy: identity, purpose, values, and the balancing of System 3 (now) against System 4 (future).

Key principles

Requisite variety (Ashby's law): only variety can absorb variety. A regulator must be at least as varied as the thing it regulates. Organizations fail either by attenuating variety badly (ignoring signals) or by trying to handle all of it centrally (overwhelming the center).
Recursion: the same five systems must exist at every level — team, department, division, enterprise. A missing level is a diagnosis.
Autonomy within cohesion: System 1 units get maximum autonomy consistent with the whole remaining viable. Centralization beyond that point destroys local variety-handling capacity.

Diagnostic questions

Which units are genuinely System 1 — producing value, not supporting it?
Is there a real System 2, or do units coordinate by escalating to a manager?
Does System 3 dominate System 4? (Almost always yes: today's numbers crowd out tomorrow's adaptation.)
Does System 3* exist, or does leadership see only filtered reports?
Is System 5 doing identity work, or has it collapsed into System 3?
At which recursion level is a function missing?

Examples by audience

Health care: a hospital's System 4 is often the weakest — service development crowded out by operational pressure. System 3* exists as audit and inspection but is frequently experienced as punitive rather than informational, which corrupts the channel.
Software: platform teams are System 2 when they provide standards that reduce inter-team friction, and become bottlenecks when they are misused as System 3 control. Naming which one is intended settles a lot of arguments. See team-topologies.
Executive: a board that spends every meeting on this quarter's numbers has collapsed System 5 into System 3. Nobody is holding identity or the now/future balance, and the organization will be surprised by its environment.

Limitations

Heavy vocabulary; requires investment before it pays.
Little empirical validation as a predictive model.
Cybernetic framing can read as mechanistic to people-centered audiences.

Questionnaire

A paired, copy-and-use diagnostic instrument for this model: viable-system-model-questionnaire.