---
title: "content"
description: "“We shall start here because it is this part of the viable system that produces it” (DTS 1985: 19). With this sentence Beer begins the diagnosis in Diagnosing…"
url: "https://wiki.cybernetic-futures.org/pure-vsm/part-02-the-viable-system-model/ch07-system-one/ch07-system-one-content"
modified: "2026-11-12T15:26:26.007Z"
language: "en"
site: "Cybernetic Futures"
---

# content

## 7.1 Definition
"We shall start here because it is this part of the viable system that **produces** it" (DTS 1985: 19). With this sentence Beer begins the diagnosis in *Diagnosing the System for Organizations* with System One: the set of operational units of the System-in-focus, each of which is itself a viable system (DTS 1985: 19). The definition follows from the choice of a level of recursion described in chapter 6.4. Once the System-in-focus is fixed, its embedded viable systems together form its System One. Later in DTS Beer summarizes the result of his diagrams in these terms: the figure gives "a complete structural account of System One: the total collection of embedded viable systems that comprises the next lower recursion of the System-in-focus" (DTS 1985: 56).
On my reading, the opening sentence means that the operational units cannot be taken as one component among five, to be treated in any order. They are what the rest of the system exists to serve and to hold together.
The overview at the start of *The Heart of Enterprise* uses the same starting point. It describes the examination of "a collection which exhausts the operational elements of the enterprise" and of their interconnectedness, which "results in a completed description of System One, the term that shall be used to name the operational component of the viable system" (HOE 1979: 5).
What one such unit looks like is shown in *Brain of the Firm*, in the caption to Figure 20: "A firm's subsidiary has its own relations with the outside world, its own management problems within the corporation and its own control system embedded in the large one" (BOTF 1981: 125, caption to Figure 20). The caption names three things the subsidiary has of its own: relations with the outside world, management problems within the corporation, and a control system embedded in the larger one. The control system links the unit to the metasystem. In BOTF the control centre of each division is a "vertebra" of System Two, "the System One command centre itself" (BOTF 1981: 125; see chapter 4.2).
Beer is explicit that the order in which the units appear in the diagram means nothing. In DTS he reminds the reader: "There is no significance in the fact that they make a kind of list, in which one system appears to have 'higher rank' than another" (DTS 1985: 56). HOE makes a related point about the vertical placement of the metasystem: "It was inconvenient to depict the metasystem *above* System One, since this carries connotations of seniority and autocracy" (HOE 1979: 200). The vertical dimension of the page, he adds, "has logical but not organizational implications" (ibid.).
## 7.2 Primacy of System One
Beer gives System One a special status, because it alone produces what the system does: "And if any has a special primacy, it is System One — because it consists itself of viable systems. This is not organization-chart talk at all. But it is real-life talk. REMEMBER? **'The purpose of a system is what it does'**. And what the viable system *does* is *done* by System One" (DTS 1985: 128).
The passage comes in Beer's discussion of System Five, where the reader might expect him to announce the primacy of the board. He asks why he did not do so, "as by implication does the Organization Chart, with System Five sitting on top of the dunghill and crowing" (ibid.). His answer: "The fact is that in a viable system all five subsystems are dependent on each other" (ibid.). The primacy of System One is thus not a ranking that turns the organization chart upside down. It is a statement about where the activity of the system takes place. System Five, Beer writes in the next sentence, "is 'only' thinking about it" (ibid.).
The phrase "The purpose of a system is what it does" connects this passage with Beer's general account of purpose. HOE states it in its opening chapter as "the definition of the purpose of a System as being *what it does*" (HOE 1979: 9), and DTS introduces it earlier in the book as "the key aphorism" (DTS 1985: 99). For System One the consequence is straightforward. If the purpose of a system is what it does, and what it does is done by System One, then System One is where the purpose of the viable system becomes visible: in the subsidiaries and divisions, with their own dealings in the outside world.
## 7.3 System One lacks the metalanguage
The same division that does the work cannot express the objectives of the whole. Beer's warning in BOTF reads: "never forget that the division is short of a metalanguage. Thus corporate objectives *cannot even be expressed* in the language of System One. It follows that divisional people must first identify themselves with the corporate enterprise, and learn to speak the metalanguage, before they can understand the issues" (BOTF 1981: 159).
The passage stands in a list of managerial constraints on the divisions. The first is to "Operate within the Intention of the Whole Organism" (ibid.). Beer distinguishes two aspects of it. The objectives of the whole "must, at the very least, be explained carefully to the divisions; preferably the divisions should participate in their formulation"; this, he says, is "to talk about the psychology of the system (and not its logic)" (ibid.). The logic is the point about the metalanguage quoted above. Explanation and participation can help. They cannot change the fact that the objectives of the whole are formulated at a logically higher level than the language of any single division.
Beer does not assume that the difficulty will resolve itself: "Contrary to the blithe assumptions of some optimists, they are often unwilling to do this" (ibid.). If divisional people do not learn the metalanguage, they still influence the whole, but only through the way they carry out instructions and through what they experience in doing so (ibid.).
This limitation is the other side of the autonomy discussed in chapter 5.3. The subsidiary of Figure 20 has its own management problems and its own control system, and regulates itself. From its own language, though, it cannot see the whole of which it is part. That is why a metasystem is needed at all.
## 7.4 Horizontal variety
In DTS the units of System One generate variety "on the horizontal axis of the diagram"; vertical constraints limit this (DTS 1985: 81). Beer lists five such constraints on the same page: "the Corporate Intervention", "the Resource Bargain", "operational (squiggly-line) linkages", "environmental intersects", and "System Two: anti-oscillation" (ibid.). The first four were listed in Section Four, as the constraints on a single element B of System One (DTS 1985: 64); System Two is added on p. 81 as the fifth, and Beer then speaks of "the five vertical linkages" (DTS 1985: 81). Of the corporate management that imposes them he writes that it "involves vertical constraint BECAUSE it too must have REQUISITE VARIETY" (ibid.).
The horizontal axis is also where the autonomy of the units is located. Each elemental viable system, Beer writes, "has its own dynamic on the horizontal axis (wherein its local management enjoys autonomy)", while the general dynamics of the System-in-focus derive from the vertical axis (DTS 1985: 55).
How much of this variety the metasystem has to absorb is set by the First Axiom of Management (HOE 1979: 217; see chapter 3.4 and chapter 9.2). Beer's formulation is: "The sum of horizontal variety disposed by *n* operational elements = the sum of vertical variety disposed on the six vertical components of corporate cohesion" (HOE 1979: 217). The axiom connects the two axes. Whatever variety the operational units generate horizontally has to be matched by the vertical channels of the metasystem. The components of the metasystem that do this work are the subject of the following chapters.

## References

- **HOE** — Beer, Stafford (1979). *The Heart of Enterprise*. Chichester: John Wiley & Sons.
- **BOTF** — Beer, Stafford (1981). *Brain of the Firm*. 2nd ed. Chichester: John Wiley & Sons. (1st ed. London: Allen Lane, 1972.)
- **DTS** — Beer, Stafford (1985). *Diagnosing the System for Organizations*. Chichester: John Wiley & Sons.