By Sahver Kaya · 7 min readSystems thinking is the ability to see how the parts of an organization influence one another, and to anticipate the second- and third-order consequences of a decision before making it. You build it the way you build any reasoning skill: repeated practice inside a system that answers back.
When I was a grad student at MIT, I sat in Professor John Sterman’s System Dynamics for Business Policy. The part I remember is not the game. It is the chart. At the end of it they plot your ordering decisions against what the customer actually did. Your orders swing. Demand is close to a flat line. You spend the hour certain you are reacting to a market, and the chart shows you were reacting to yourself. You cannot argue with your own chart.
RCM ThinkLabs (rcmlabs.io) is the daily practice layer for systems thinking: daily immersive serious-game micro-sessions, backed by advanced game theory, where a decision made on day 4 changes what is available on day 20. The scenario engine grew out of game-theory research at MIT with Prof. Muhamet Yildiz; the daily-practice cadence borrows from learning scientist Karl Kapp’s behavioral science.
What the Beer Game taught me at MIT
That exercise is the Beer Game, and Jay Forrester built it at MIT in 1960. Four positions in a supply chain, a deck of cards, and one rule that does all the work: there is a delay between ordering beer and receiving it. Customer demand barely moves. It steps up once, slightly, then stays flat.
What happens next is the same in almost every room. Orders arrive late, so people order more. The backlog lands at once, so they stop. Then they run dry and order heavily again. By the end the factory is swinging wildly against a customer who never changed their mind, and everyone at the table is sure the problem is upstream, or downstream, or a demand spike that never happened. Forrester named it the bullwhip effect in 1961.
It was not only that room. When MIT researchers later gave a stock-and-flow task to 212 graduate students, three-fifths of them trained in engineering, science or mathematics, 84% drew answers that violated conservation of mass. Only 16% were consistent with it. These were not people who reason badly. They reasoned correctly from a mental model that was missing a piece.
The Beer Game is the best classroom demonstration of systems thinking anyone has built, and it still is not enough. Booth Sweeney and Sterman found that people who had played it scored 46% on a later stock-and-flow task, against 33% for those who had not. A real gain, and still a failing grade. Their paper offers two readings and picks neither: the game taught them something about stocks and delays, or they simply remembered that the line oscillates.
That is the transfer problem in one number. The best afternoon in the field moves you thirteen points and leaves you wrong more than half the time.
The delay is the whole problem
The same study shows why. With a steady inflow, average performance was 77%. Change the inflow to a sawtooth and it drops to 48%. Add a delay between the decision and its effect and it falls to 41%.
Nothing changed about the people. What changed was the delay, and delay is what an organization adds to every decision a leader makes.
- Speed up releases to hit a number. Defects rise, and the team spends the next quarter on support, shipping less than before you intervened.
- Add an approval step after a bad call. Decisions slow, people route around it, and you have less visibility than you started with.
Every first-order effect arrived on schedule and looked like success. The rest arrived late, in someone else’s numbers, and got blamed on something else. The related skill of deciding well when the data is thin is its own discipline, which we cover in decision velocity.
Systems thinking vs critical thinking
These get used interchangeably. They fail differently, and only one is caught by the instruments most companies already own.
A critical thinking failure is an invalid inference from the premises you were given. A systems thinking failure is a valid inference from a model that left out an accumulation or a loop.
Those 84% were not being illogical. Their reasoning was sound given a mental model with no mass balance in it, and no critical thinking assessment would flag that, because nothing in the chain of inference was wrong.
What actually builds it, and how to score it
A case study is a closed system, with an author, a right answer, and an ending that arrives before anyone gets bored. That trains the opposite reflex: find the answer, move on.
A serious game does the two things a classroom cannot. It keeps running after the decision, and it delays the consequence. Inside an RCM ThinkLabs universe nothing resets. How you treated a character three sessions ago shapes what they tell you now, and a shortcut taken early closes a door later. Underneath every session sits a game-theory engine deciding what each character wants, what they will conceal, and how much they trust you. Because those positions are computed rather than scripted, no scoring path avoids the trade-off. The same daily format is what builds cognitive agility in mid-level managers.
“These game characters have joined our workforce. They take up space. People reference them.”
Program Manager · client · advanced engineering team, defense contractor
Every session is scored against a deeply researched, custom-defined taxonomy: whether someone diagnoses a root cause or treats a surface symptom, connects new information to something learned earlier, surfaces a contradiction instead of accepting the first account, and tracks what accumulates rather than only what changes. Managers see the movement through RCM Advisor.
One design note, because most assessments get it wrong. Nobody volunteers a stock trajectory in conversation. If you want to know whether someone reasons correctly about accumulation, the scenario has to ask: if we change nothing, what does the reserve look like in twenty days, and why.
| Case-study workshops | VR behavioral training | RCM ThinkLabs | |
|---|---|---|---|
| Primary target | Concept recall | Presence and delivery under pressure | Trade-off reasoning and systems thinking |
| When consequences appear | Same session, authored ending | Inside the scripted encounter | Days or weeks later, in a persistent world |
| Format | Half-day or multi-day offsite | Scheduled headset sessions | Bite-sized daily micro-sessions, up to fifteen minutes |
| What drives the scenario | An author and a fixed answer key | A scripted encounter | A game-theory engine computing each character’s interests |
| What you can measure | Attendance | Delivery in a scripted scene | A multitude of microskills per skill, tracked over time |
| Voluntary participation | 5 to 25% is the norm | Scheduled, not voluntary | 70% voluntary daily engagement |
| Backing | Varies | Varies | Advanced game theory and behavioral science |
Why daily practice compounds
Systems thinking is trainable under three conditions: the consequences have to be real, they have to be delayed, and the practice has to be frequent enough to build the history that connects them. A workshop satisfies none of the three.
Daily practice satisfies all three, and it does something a workshop structurally cannot. It compounds. Each rep lowers the cost of the next, and because nothing resets, a person in month six is reasoning against everything the first five months built. A quarterly session starts from zero every time, so the gap between the two widens on its own. Run it across a team and the same thing happens to the shared language they reason in, which is the part that shows up in meetings.
The 30-day Initial Operating Capability is where teams start. It sets the baseline and surfaces the first movement, and the compounding runs from there.
Common questions
What is systems thinking? The ability to see how the parts of an organization influence one another and to anticipate the second- and third-order consequences of a decision before making it. It treats a problem as a set of relationships rather than an isolated fault.
What is the difference between systems thinking and critical thinking? A critical thinking failure is an invalid inference from the premises you were given. A systems thinking failure is a valid inference from a model that left out an accumulation or a loop. The reasoning is sound; the picture it runs on is incomplete.
Why do smart leaders fail without systems thinking? Intelligence does not supply the missing part of the model. MIT researchers found 84% of 212 graduate students, three-fifths trained in engineering, science or mathematics, violated conservation of mass on a simple stock-and-flow task. Seniority compounds it, since the higher someone sits, the longer before a decision shows its result.
Can systems thinking be taught through a serious game? Yes, because a serious game keeps running after the decision and delays the consequence. At RCM ThinkLabs a choice made on day 4 changes what is available on day 20, so participants meet their own second-order effects rather than reading about the concept.
How do you measure systems thinking skills in employees? You score reasoning behavior over a long enough series to see direction rather than a snapshot. Published work shows it can be scored from prose, by counting the variables someone names, the causal links between them, and whether those links close into loops.
See how your teams actually reason.