Beguiling Events
Systems often fool us by presenting only events, the most visible aspect, but understanding requires seeing patterns of behavior over time and the underlying system structure of stocks, flows, and feedback loops.
THE IDEA
Beguiling Events
A system is a big black box
Of which we can’t unlock the locks,
And all we can find out about
Is what goes in and what comes out.
Perceiving input-output pairs,
Related by parameters,
Permits us, sometimes, to relate
An input, output and a state.
If this relation’s good and stable
Then to predict we may be able,
But if this fails us—heaven forbid!
We’ll be compelled to force the lid!
—Kenneth Boulding,2 economist
Systems fool us by presenting themselves—or we fool ourselves by seeing the world—as a series of events. The daily news tells of elections, battles, political agreements, disasters, stock market booms or busts. Much of our ordinary conversation is about specific happenings at specific times and places. A team wins. A river floods. The Dow Jones Industrial Average hits 10,000. Oil is discovered. A forest is cut. Events are the outputs, moment by moment, from the black box of the system.
Events can be spectacular: crashes, assassinations, great victories, terrible tragedies. They hook our emotions. Although we’ve seen many thousands of them on our TV screens or the front page of the paper, each one is different enough from the last to keep us fascinated (just as we never lose our fascination with the chaotic twists and turns of the weather). It’s endlessly engrossing to take in the world as a series of events, and constantly surprising, because that way of seeing the world has almost no predictive or explanatory value. Like the tip of an iceberg rising above the water, events are the most visible aspect of a larger complex—but not always the most important.
We are less likely to be surprised if we can see how events accumulate into dynamic patterns of behavior. The team is on a winning streak. The variance of the river is increasing, with higher floodwaters during rains and lower flows during droughts. The Dow has been trending up for two years. Discoveries of oil are becoming less frequent. The felling of forests is happening at an ever-increasing rate.
The behavior of a system is its performance over time—its growth, stagnation, decline, oscillation, randomness, or evolution. If the news did a better job of putting events into historical context, we would have better behavior-level understanding, which is deeper than event-level understanding. When a systems thinker encounters a problem, the first thing he or she does is look for data, time graphs, the history of the system. That’s because long-term behavior provides clues to the underlying system structure. And structure is the key to understanding not just what is happening, but why.
The structure of a system is its interlocking stocks, flows, and feedback loops. The diagrams with boxes and arrows (my students call them “spaghetti-and-meatball diagrams”) are pictures of system structure. Structure determines what behaviors are latent in the system. A goal-seeking balancing feedback loop approaches or holds a dynamic equilibrium. A reinforcing feedback loop generates exponential growth. The two of them linked together are capable of growth, decay, or equilibrium. If they also contain delays, they may produce oscillations. If they work in periodic, rapid bursts, they may produce even more surprising behaviors.
System structure is the source of system behavior. System behavior reveals itself as a series of events over time.
Systems thinking goes back and forth constantly between structure (diagrams of stocks, flows, and feedback) and behavior (time graphs). Systems thinkers strive to understand the connections between the hand releasing the Slinky (event) and the resulting oscillations (behavior) and the mechanical characteristics of the Slinky’s helical coil (structure).
Simple examples like a Slinky make this event-behavior-structure distinction seem obvious. In fact, much analysis in the world goes no deeper than events. Listen to every night’s explanation of why the stock market did what it did. Stocks went up (down) because the U.S. dollar fell (rose), or the prime interest rate rose (fell), or the Democrats won (lost), or one country invaded another (or didn’t). Event-event analysis.
These explanations give you no ability to predict what will happen tomorrow. They give you no ability to change the behavior of the system—to make the stock market less volatile or a more reliable indicator of the health of corporations or a better vehicle to encourage investment, for instance.
Most economic analysis goes one level deeper, to behavior over time. Econometric models strive to find the statistical links among past trends in income, savings, investment, government spending, interest rates, output, or whatever, often in complicated equations.
These behavior-based models are more useful than event-based ones, but they still have fundamental problems. First, they typically overemphasize system flows and underemphasize stocks. Economists follow the behavior of flows, because that’s where the interesting variations and most rapid changes in systems show up. Economic news reports on the national production (flow) of goods and services, the GNP, rather than the total physical capital (stock) of the nation’s factories and farms and businesses that produce those goods and services. But without seeing how stocks affect their related flows through feedback processes, one cannot understand the dynamics of economic systems or the reasons for their behavior.
Second, and more seriously, in trying to find statistical links that relate flows to each other, econometricians are searching for something that does not exist. There’s no reason to expect any flow to bear a stable relationship to any other flow. Flows go up and down, on and off, in all sorts of combinations, in response to stocks, not to other flows.
Let me use a simple example to explain what I mean. Suppose you knew nothing at all about thermostats, but you had a lot of data about past heat flows into and out of the room. You could find an equation telling you how those flows have varied together in the past, because under ordinary circumstances, being governed by the same stock (temperature of the room), they do vary together.
Your equation would hold, however, only until something changes in the system’s structure—someone opens a window or improves the insulation, or tunes the furnace, or forgets to order oil. You could predict tomorrow’s room temperature with your equation, as long as the system didn’t change or break down. But if you were asked to make the room warmer, or if the room temperature suddenly started plummeting and you had to fix it, or if you wanted to produce the same room temperature with a lower fuel bill, your behavior-level analysis wouldn’t help you. You would have to dig into the system’s structure.
That’s why behavior-based econometric models are pretty good at predicting the near-term performance of the economy, quite bad at predicting the longer-term performance, and terrible at telling one how to improve the performance of the economy.
And that’s one reason why systems of all kinds surprise us. We are too fascinated by the events they generate. We pay too little attention to their history. And we are insufficiently skilled at seeing in their history clues to the structures from which behavior and events flow.
When to use it
Analyzing stock market volatility by moving beyond daily price changes (events) to examine historical trends (behavior) and market mechanisms (structure).
Improving business performance by identifying recurring patterns (e.g., seasonal sales cycles) and designing feedback loops to stabilize growth.
Environmental policy: understanding that events like floods or droughts are part of long-term behavioral patterns driven by underlying structures (e.g., land use, climate systems).
Personal development: recognizing that isolated life events (e.g., a breakup) often fit into behavioral patterns and structural habits, enabling deeper change.
FROM THEORY TO EVERYDAY LIFE
In practice
Slinky
A Slinky illustrates the event-behavior-structure distinction: the hand releasing it (event), the resulting oscillations (behavior), and the helical coil (structure).
Thermostat
A thermostat example: heat flows into and out of a room can be correlated via equations (behavior-level), but changes in structure (opening a window, improving insulation) break the pattern, requiring structural understanding.
Stock Market Commentary
Evening news may explain a market move with an event-level story, such as 'stocks rose because the dollar fell'. Such a story alone does not establish how to predict future moves or change the system’s behavior.
A MOMENT TO REFLECT
Put it to work.
Think of a recent news story about a complex system (e.g., economy, climate). Can you identify the event, the underlying behavioral patterns over time, and the structures that produce those patterns?
When you face a problem at work or in your personal life, do you tend to focus on the immediate events or look for longer-term trends and root causes? How might shifting perspective help?
Why do behavior-based models (like econometric forecasts) often fail in the long run? What role does system structure play in that failure?
Often confused with
References
- Poem on systems — Kenneth Boulding
CONTINUE THE CONVERSATION
Source texts
- Thinking in Systems A Primer