The History of Systems Theory in Management

By Victor Hoang · Updated Oct 24, 2026

The problem was visible long before it had a name. By the 1940s, organizations had specialists, charts and rules. They still behaved in ways no single department had planned. Taylor, Fayol and Weber had given managers tools for the parts. Nobody had given them a vocabulary for the whole.

Systems theory entered management in the 1950s and 1960s. The biologist Ludwig von Bertalanffy's open-systems idea of 1950 and Norbert Wiener's cybernetics of 1948 were carried into business schools and consulting rooms. The throughline is a change of question. Instead of asking how to make each part efficient, managers began asking how the parts affect one another. They also asked how the whole exchanges things with the world around it.

This page follows the people who built one, and what happened when they tried to use it. For the wider story, start with the full history of management; for the idea that grew directly from this one, see the history of contingency theory.

Timeline at a Glance

The Organism Idea (494 BCE-1940s)

A body of parts becomes a metaphor for the firm

Picture a camp outside Rome during a secession of the common people, with the senate sending a spokesman to talk them back. Livy, in his history of Rome, tells it as happening in 494 BCE by the traditional dating, and says the envoy, Menenius Agrippa, simply told a fable. The hands, mouth and teeth, angry that everything they produced went to the belly, refused to feed it. The whole body wasted away, and it became clear that the belly "rendered no idle service", because it returned the nourishment to every part.

This is a precursor, not systems theory. Nobody in the camp described feedback, boundaries or inputs. What the fable does show is the oldest documented form of the claim at the center of the later theory: parts that look like a drain may be carrying something the whole needs, and an organization that attacks one part can starve itself. It ran in one direction for centuries. In 1651, Thomas Hobbes wrote in the introduction to Leviathan that the commonwealth is "an Artificiall Man", with the sovereign as its soul, magistrates as its joints and sedition as its sickness. The body was still a metaphor for the state, and not yet a method for running a company.

Two writers then moved the idea toward organizations. Alexander Bogdanov (1873-1928), a Russian physician, philosopher and revolutionary, proposed in his work called Tektology that all the physical, biological and human sciences could be unified by treating them as systems of relationships and seeking the organizational principles underneath. A scholarly review published by H-Russia says his work anticipated Wiener's cybernetics and Bertalanffy's general systems theory in important ways. Because he was attacked in the Soviet Union for his philosophy, the review adds, his influence is hard to trace.

The second was an American executive. Chester Barnard spent nearly forty years at AT&T and its associated telephone companies, and the Harvard University Press page for The Functions of the Executive (1938) says his association with Elton Mayo and his Harvard colleagues had an important bearing on his most original ideas. It quotes a review in the American Journal of Sociology saying the book points the way to more effective "co-operative systems". He wrote about the organization as a whole before the whole had a theory, and his place beside Mayo's circle is told in our history of the human relations movement.

What this means for teams today: The belly fable is still the right first question for a reorganization. Before you cut a function that looks like pure cost, ask what flows through it to the rest of the body.

The Founding Years (1948-1956)

Cybernetics, open systems and a society to hold them

The theory was built in less than a decade. In 1948, the mathematician Norbert Wiener published Cybernetics, which Eden Medina's account in Cabinet magazine summarizes as the study of "control and communication in the animal and the machine". Its central tool was the feedback loop: a system senses what it did and corrects what it does next.

Two years later, Ludwig von Bertalanffy published The Theory of Open Systems in Physics and Biology in Science (13 January 1950, volume 111, pages 23 to 29, per Crossref). An EBSCO research summary dates open systems theory to Bertalanffy's work of 1950 and says he wanted a framework that could be applied to all living things. A living thing is not sealed. It takes in material from its environment, transforms it and sends something back out, and that exchange is what keeps it alive.

Meanwhile a field study in Britain showed the same logic in a workplace. In 1951, Eric Trist and Ken Bamforth published a study of the longwall method of coal-getting in Human Relations. As a discussion of the paper summarizes it, mechanization along a very long face replaced the old hand-got method, in which small teams worked closely together as autonomous units, and the change broke up the social structure of the workers it was meant to help. Technical and social systems had to be considered together, a point that fed the sociotechnical approach.

The thinkers then built an institution. The International Society for the Systems Sciences records that the society was conceived in 1954 at the Stanford Center for Advanced Study in the Behavioral Sciences by Bertalanffy, Kenneth Boulding, Ralph Gerard and Anatol Rapoport. A meeting of about seventy people was held in Berkeley in December 1954 under the American Association for the Advancement of Science, the name became the Society for General Systems Research in fall 1955, and with James Grier Miller it was formally established as an AAAS affiliate in 1956. That same year, Boulding published General Systems Theory: The Skeleton of Science in the journal Management Science, pitching the idea at the people who study organizations.

What this means for teams today: The feedback loop is the simplest useful import. For any process you run, ask where the output of one cycle becomes the input of the next, and who sees it.

The Management Import (1957-1972)

Business schools turn a biology idea into a model of the firm

Management got systems theory by two routes. The first was a simulation tool. Jay Forrester's Industrial Dynamics (1961) is a founding text of what the System Dynamics Society now describes as a computer-aided approach for strategy and policy design, using feedback loops to capture how the parts of a system interact and produce a pattern of behavior over time. The firm stopped being only a chart and became a set of feedback loops that a manager could run forward on a computer and argue about.

The second route was social psychology. In 1966, Daniel Katz and Robert Kahn published The Social Psychology of Organizations. An EBSCO summary says they argued that scholars had overlooked the study of behavior in the context of organizations, and that open systems theory gave them a tool for looking past the individual. By December 1972, George Kast and James Rosenzweig were describing applications of general system theory to organization and management in the Academy of Management Journal. The idea had entered the textbooks.

The result was a way of seeing, not yet a method. It showed up in the field studies that produced contingency theory, because a firm that exchanges things with its environment will need to be shaped by that environment. That link is the subject of the history of contingency theory, and the school-by-school context is in the schools of management thought, in order.

What this means for teams today: Draw your team as a system on a whiteboard, with inputs, outputs and the loops between them. If you can't say what the environment changes about your work each quarter, you're treating a living system as a machine.

The Cybersyn Experiment (1971-1973)

A cybernetician tries to run an economy's factories in real time

This era overlaps with the last, because the biggest test of the theory happened while the textbooks were still being written. In July 1971, Stafford Beer received a letter from Fernando Flores, a young Chilean engineer working for Salvador Allende's government, as Eden Medina recounts. Flores asked how to apply cybernetics to the nationalized part of the economy. Beer replied that he believed Chile "is really going to do it", and arrived four months later as a consultant.

Beer brought the Viable System Model, which Medina describes as built to describe the balance between centralized and decentralized control in organizations and based on the human nervous system. It supplied the framework for what became Project Cybersyn: a telex network, software to detect economic anomalies, an economic simulator and an operations room. By January 1973 the team had built a working prototype of each part except the simulator. On 11 September 1973 the Chilean military launched a coup, and it stopped work on the project, abandoning or destroying what the team had completed.

Cybersyn is easy to caricature, as a dream of control or a lost utopia. The documented record is plainer. A management theory built on the body was used to ask how much authority should sit at the center and how much with the factory floor, and the answer was cut off by politics rather than disproved.

What this means for teams today: Beer's question survives any change of tool: which decisions need the center, and which belong to the people closest to the work? Write the answer down before you buy the dashboard.

The Soft Systems Years (1970s-1990)

Checkland discovers that managers' problems are not engineering problems

The systems approach had come from engineering and biology, and it worked best where the goal was clear. Peter Checkland set out to test whether the Systems Engineering approach, highly successful in technical problems, could be used by managers coping with organizational life. The publisher's description of Systems Thinking, Systems Practice says the straightforward transfer was not possible. His research group instead developed Soft Systems Methodology, which treats the inquiry into a messy situation as itself a system for learning.

That work established the distinction between "hard" systems thinking, where parts of the world are taken to be systems that can be engineered, and "soft" systems thinking. The book appeared in 1981, with Soft Systems Methodology in Action following in 1990. For a manager, the practical difference is large. A hard approach asks what the best design is for a known goal. A soft approach asks whose view of the goal we are using, and whether the people involved even agree on the problem.

What this means for teams today: Before modeling a problem, check that the room agrees on what the problem is. Many "system" failures are disagreements about purpose that nobody has said aloud.

The Learning Organization (1990-present)

Systems thinking becomes a habit that managers are told to build

In 1990, Peter Senge published The Fifth Discipline. Its subtitle is The Art and Practice of the Learning Organization, and the publisher's page prints Harvard Business Review's verdict: "One of the seminal management books of the past seventy-five years." The same page quotes W. Edwards Deming recommending it as a good place to begin on optimizing a system. Senge's move was to package a body of theory as a discipline that individuals and teams could practice. The reengineering movement of the same year took the opposite route, redesigning processes from a blank sheet; its story is in the history of business process reengineering.

Complexity became its own field in parallel. In 1984, George Cowan, David Pines, Murray Gell-Mann and others established the Santa Fe Institute, an independent center focused on complexity at all scales. By 2007, David Snowden and Mary Boone were arguing in the Harvard Business Review that previously successful leadership approaches fail in new situations because different contexts call for different approaches. The "it depends" that contingency theorists had measured became advice to executives about how to decide.

The current version is mostly a skill rather than a school. The System Dynamics Society still teaches feedback modeling, and the competency frameworks in business now list the ability to see interconnections as something to assess and develop. See systems thinking as a business competency, the organizational maturity model for systems thinking and the individual five-level path. The coordination of people and software together, the question the pillar article closes on, is a systems question again. For the process side, see business process management.

What this means for teams today: Make one loop visible each quarter: a delay, a handoff or a reinforcing cycle your team is inside. Naming a single loop teaches more than a poster of the whole system.

Key People

Key Facts

Key Facts: Systems Theory in Management

• Bertalanffy's paper on open systems appeared in Science on 13 January 1950.
• The Society for General Systems Research was conceived in 1954 and became an AAAS affiliate in 1956; it took its current name, the International Society for the Systems Sciences, in 1988.
• Beer's team had working prototypes of Cybersyn's components, except the simulator, by January 1973; the coup came on 11 September 1973.
• Checkland's Soft Systems Methodology separated hard from soft systems thinking for managers.
• The Santa Fe Institute was established in 1984 to study complexity.
• Deming recommended The Fifth Discipline as a good place to begin on optimizing a system, according to the publisher.

The Pattern Behind the History

This is our synthesis of the record, not a research result. We call it the Metaphor-to-Method Pattern, and it has four moves.

1. The whole is seen before it is measured. Livy's fable, Hobbes's Leviathan and Barnard's executive all saw the organization as one body decades or centuries before anyone had tools for it.
2. A theory is imported, then reshaped. Biology and mathematics supplied the concepts, and business schools and consultants rebuilt them as models for firms.
3. Hard tools meet soft problems. Forrester's loops and Beer's control model worked best where the goal was agreed, and Checkland's work began where it wasn't.
4. The model stays a guide, not a ruler. Cybersyn's best use was as a framework for deciding who decides. When the model is mistaken for the organization, the people disappear from the picture.

What It Teaches Teams Today

• Ask what flows through the part you are cutting. The belly fable still describes most bad reorganizations.
• Make loops visible. Draw one feedback cycle your team is inside and decide who watches it.
• Agree on the purpose before you model the process. Checkland's soft systems work starts with the question of whose view counts.
• Decide where decisions live. Beer's central question, center or edge, is still the first design choice in any organization.
• Treat the map as a guide. A dashboard is a view of the system, not the system. Keep people close enough to the work to see what the model leaves out.