top of page
nuAgility Glossary

What is the Viable System Model?

The Viable System Model (VSM), developed by Stafford Beer, describes the functions and relationships an organization needs to remain viable as its environment changes. It helps leaders examine how operational autonomy, coordination, internal management, adaptation, and shared identity work together.


System 1: Operations. These are the operational units that carry out the organization's primary activities and create value. Each needs enough autonomy to respond to its local environment while remaining part of the larger organization.


System 2: Coordination. This function helps operational units work together without destabilizing one another. Shared information, agreed routines, and ways to resolve scheduling conflicts help reduce friction.


System 3: Internal management and synergy. This function looks across current operations, manages shared resources, and supports cooperation so the organization achieves more than its units could separately. System 3* provides an additional audit or monitoring channel into operational activity.


System 4: Intelligence and adaptation. This function looks outward and ahead, exploring changes in customers, technology, markets, and the wider environment. It develops options for the future in dialogue with the demands of current operations.


System 5: Policy and identity. This function establishes the organization's purpose, values, and overall policy. It maintains coherence and balances the needs of present operations with future adaptation.



The five systems are functions, not necessarily five departments or management layers. The pattern is recursive: an operational unit can itself be a viable system within a larger one.


Further reading: Metaphorum's introduction to the Viable System Model


Related Article: Viable Organisations with Beer


Why it matters


The model helps leaders examine how local autonomy, coordination, current operations, and future adaptation fit together.


Example


Imagine a service business with several regional teams. Each needs discretion to serve local customers, yet competing schedules repeatedly overload shared specialists. Leaders use the Viable System Model to examine operational autonomy, coordination, resource management, attention to future demand, and shared purpose. They establish a scheduling agreement, clarify decisions regional teams can make, and create a regular conversation between people managing today's service and those exploring future needs. They also check operational reality beyond summary reports. The model helps identify missing relationships and functions; it does not require the business to create five new departments or remove local autonomy.


Common misunderstanding


The VSM's five systems can be mistaken for five departments that must be created. The model describes functions and relationships needed for viability, not a prescribed organization chart. Several people or groups may contribute to a function, and viable units can exist within other viable units.


Examine where operational autonomy, coordination, internal management, adaptation, and policy actually occur. Creating labels or committees does little if those functions cannot communicate or balance competing demands. Use the model to identify missing or strained relationships, not merely to rename existing departments.


Related terms


Systems Thinking · Business Agility · Complex Adaptive Systems


Explore questions like this with other practitioners through the Agile Community Network, nuAgility's free live community event and podcast.

bottom of page