System Thinking Tools

Deep Thinker
--> Systems Thinking
--> --> System Thinking Tools

System Thinking Tools

🧠 Free Recall ❓ Quiz 🔍 Cues 🔮 Simulation 🥷 ShadowBox 📐 Encode Cards

System Thinking as a language

Our language is linear, one-way in thinking. System thinking is circular or mutually causative (self-reinforcing)

We need to be aware of the language we use and if our vocabulary is not reflective of reality then it's us who have to adapt

At the same time, we need a language that still somewhat maps to our reality. Writing partial differential equations to describe clouds misses the mark.

Levels of Understanding

Events
Reactive, require immediate action
Typical Question: What is the fastest way to react to this event NOW

Patterns of Events
Adaptive
Typical Question: What kinds of trends or patterns of events seem to be recurring

System Structure
Creative
Typical Question: What are the mental or organizational structures that create the patterns

Shared Vision
Generative
What are the stated or unstated visions that generate the structures

The process of gaining deeper understanding is not linear, and an understanding of a situation at one level can feedback and inform awareness at another level

Levels of Understanding is important for recognizing the level at which you are operating at. From there you can evaluate action and if it provides the highest leverage for that situation. Each level offers different opportunities for high-leverage action, but also limits. The challenge is to choose the appropriate response for the situation and find ways to alter future occurrences.

Tools

Dynamic Thinking Tools

Behavior Over Time
Can be used to graph the behavior of variables over time and gain insights into any interrelationships between them.

Causal Loop Diagram
Used in conjunction with behavior over time diagrams, can help you identify reinforcing and balancing process

Systems Archetype
Help you recognize common system behavior patterns

Reinforcing and balancing loops are the building blocks of systems thinking and language. With these these two structures an infinite variety of complex systems can come to.

Reinforcing Loops

Reinforcing loops produce growth and decay. They compound change in one direction.

Balancing Loops

Balancing loops bring things to a desired state and keep them there.

Guidelines for Drawing Causal Loop Diagrams

Theme Selection - Narrow the scope to something useful and poignant. At the same time, remember "emergent" properties. Sometimes you need to get the big picture to better understand the problem/issue at hand

Time Horizon - Add the time horizon for an issue. One long enough to see the dynamics play out. Time is a first-class citizen in systems thinking.

Behavior over time charts - Drawing out behavior over time of key variables

Boundary Issues - You have to know when to continue and stop adding to your diagram. Focus on variables that will have significant effects on the issue you're mapping for

Level of aggregation - How detailed should the diagram be

Significant Delays - Make sure you identify links that have significant delays relative to the rest of the diagram. Delays are often the source of imbalances that accumulate in the system. You can use system structures to represent delays such as relief valves that open slowly as pressure builds or opens abruptly when pressure hits a critical value.

Selecting Variable Names
Use nouns when choosing a variable name. Avoid verbs and action phrases because action is conveyed in loop arrows
Use S for same and O for opposite
Use variables that represent quantities that can vary over time. (Happiness not "state of mind")
When possible choose the more positive sense of a variable
Loop Construction 
Think of the possible unintended consequences as well expected outcomes for every course of action included in the diagram. 
All balancing loops are goal seeking processes. Try to make explicit the goals driving the loop
Distinguishing between perceived and actual states is important. Perceptions often change slower than reality does and mistaking the perceived status for current reality can be misleading and create undesirable and results
If variable has multiple consequences, start by lumping them into one term while completing the rest of loop.
Actions almost always have different long term and short term consequences. Draw larger loops as they progress from short to long term processes. 
If a link between two terms requires a lot of explanation to be clear, redefine the variables or insert an intermediate term.
A shortcut to determining whether a loop is balancing or reinforcing is to count the number of "o"s in the loop. An odd number of "o"s indicate a balancing loop. An even number or no "o" means it's a reinforcing loop. 
Use two vertical lines to signal delays.
Place loop goals inside of the loop with the kind of loop (R for reinforcing, B for balancing)
Systems Archetypes At A Glance

Drifting Goals
Drifting performance is a red flag of drifting goals
A critical aspect of avoiding drifting goals is to determine what drives the setting of the goals
Goals located outside the system will be less susceptible to drifting goals pressures
Escalation 
To break an escalation...
What is the relative measure that pits one party against the other and can you change it?
What are the significant delays in the systems that may distort the true nature of the threat
What are the deep-rooted assumptions that lie beneath the actions taken in response to the threat
Fixes that Fail
Breaking a Fixes that fail requires acknowledging that the fix is merely alleviated a symptom and making a commitment to solve the real problem now
A two pronged attack of applying the fix and planning the solution will help ensure that you don't caught in a perpetual cycle of solving yesterday's solutions
Limits To Success
Useful when used to anticipate problems to see how the cumulative effects of continued success might lead to future problems
Use the archetype to explore questions such as "What kinds of pressures are building up in the org as a result of growth"
Look for ways to relieve pressures or remove limits before an organizational gasket blows
Shifting The Burden/Addiction
Problem symptoms are usually easier to recognize than the other elements of the structure
If the side-effect has become the problem you may be dealing with an addiction structure
Whether a solution is symptomatic or fundamental often depends on perspective. Explore the problem from a different perspective in order to come to a more comprehensive understanding of what the solution may be
Success to the Successful
Look for reasons why the system was set up to create just a few winners
Chop off half of the archetype by focusing efforts and resources on one group rather than creating a winner take all competition
Find ways to make collaborators rather than competitors 
Identify goals or objectives that define success at a level higher than the individual players A and B
Tragedy of the Commons
Effective solutions for TotC never lie at the individual level
Ask "What are the incentives for individuals to persist in their actions?" Can the long term collective loss be make more real and immediate to the individual actor
Find ways to reconcile short term and cumulative consequences

Structural Thinking Tools

Graphical Function Diagram

Captures the way which one variable affects another, by plotting the relationship between the two over the full range of relevant values

Graphical functions allow us to expand exploration of a system to include policies and interrelationships between variables

When using graphical function diagram its better to get it 60 percent right very quickly and spend time modifying it than spending a great deal of effort trying to get it right 100 percent right of time

To create a GFD ask
What do you know from the outset about the causal relationship between the two variable
Are there neutral zones where the variable of the y axis is not affected by change in the x variable
What are the extreme value

Structure-Behavior Pair
Consists of the basic dynamic structures that can serve as building blocks for developing computer models

Accumulators help us visualize concepts that accumulate in quantitative 
Flows - Helps us explain how quantities move throughout a system

We are less interested in correlational relationships and more interested in the causal structures that produce the observed behavior

Flows are easy to keep track of because they involve easy to measure action. Many accumulators are hard to identify

For every flow locate if there is an accumulator. If you look at the situation from the accumulator viewpoint and trace out the reinforcing loop, it becomes clear why typical stress reduction efforts do not work.

When trying to create change, think of how inflows and outflows are affected (increased, decreased) and how that relates to the connected accumulator. It will open a ton of different ideas on how to improve a system

hidden accumulators are accumulations of stock not originally intended by the organization. For example, # of shoppers has hidden or sub accumulators of # of people in checkout, # of people in customer service, # of people in aisles, heck, even # of people in bathrooms/lunch areas

Accumulator Management
Accumulation
Acquisitions
Depletions
Desired Accumulations
Corrective Action

There is almost always some delay between corrective action and the acquisition because it takes time to actually store data or clear out data once decided to do so. The faster and more accurate that relevevant data can get to the accumulating flow/function, the more closer the accumulator will be to the desired accumulator

One of the most challenging aspects of managing accumulations are delays. Identifying and characterizing the nature and source of delays often plays a critical role in managing accumulations effectively. A big problem is that we have little control over the supply line delay.

Accumulator Management Questions
Where are the supply line delays and how are they changing
What factors are determining what Desired Accumulations should be?
How do current policies and decisions feed back into this system to produce the results observed.

Whenever there are significant delays in a system you can bet that there are accumulators involved.

Aging Chain Structure - Delays in the system that depend on the inherent nature of that system and those delays cannot be shortened expect within some narrow bounds.  Trying to shorten the inherent time delay by pushing things through the accumulators faster can wreak havoc on the system

A production chain is a diagram showing an acquisition going through different stages of the production process, represented by accumulators.

The key different in production chains is the illustration of time delays, upsetting the flow rate of accumulators

S-shaped Growth and Diminishing Returns

Diminishing Returns - When more effort yields fewer results than it did originally.

A heuristic for S-shaped growth is "Steady, Steep, Steady"

Unless you can somehow change the inherent delays built into the various stages of a production process, the best expediting action one can take may be do nothing and wait

The ability to see similar structures occurring in diverse settings is referred to as genetic thinking and the structures are referred to as generic structures.

Policy Structure Diagram
A conceptual map of the decision-making process embedded in the organization. Focuses on the factors that are weighed for each decision and can be used to build a library of generic structures

Complexity

emergence is when an entity of a system have properties that its parts don't posses on its own

Pattern of change in a system
coherence - beginning state
disruption - breaking of the status quo
differentiation - innovation and distinctions amongst parts
coherence - new complex state appears

Emergence can’t be manufactured. It often arises by drawing from individual and collective intuition. It can't be forced but it can be fostered.

Complexity increases as more diversity, connectivity, interdependence, or interactions become part of a system.

Three questions can help us think about how to work with change:
How do we disrupt coherence compassionately?
How do we engage disruption creatively?
How do we renew coherence wisely?

Principles of Emergence

No one is in charge. No conductor is orchestrating orderly activity (ecosystems, economic systems, activity in a city).
Simple rules engender complex behavior. Randomness becomes coherent as individuals, each following a few basic principles or assumptions, interact with their neighbors (birds flock; traffic flows).
Feedback. Systems grow and self-regulate as the output from one interaction influences the next interaction. (We talk to a neighbor, who talks to a neighbor, and suddenly everyone in town knows a story.)
Clustering. As we interact, feeding back to each other, like attracts like, bonding around a shared characteristic. (Small groups of women meeting in living rooms grow into the women’s movement.)So if emergence occurs through these dynamics, what are the implications for how we engage with it?

System Archtypes

Starred

Dunk (exclude from study)

What is the mental, actionable, atomic checklist you would apply to everything you do that requires almost no thinking to go through just truthfulness and awareness.

# The Executive Systems Checklist

**Before any action:**

## 1. LEVERAGE CHECK
- What's the smallest intervention point that cascades through the entire system?
- Am I solving a symptom or redesigning a structure?

## 2. LOOP IDENTIFICATION
- What reinforcing loop am I triggering? (Will this compound positively or negatively?)
- What balancing loop will resist this? (What's the natural pushback?)

## 3. DELAY AWARENESS
- When will consequences actually show up?
- What am I measuring *now* that's actually a lagged indicator of something I did months ago?

## 4. SECOND-ORDER EFFECTS
- What does this change *next*?
- What breaks when this succeeds?

## 5. BOUNDARY EXPANSION
- Am I looking at a big enough system, or optimizing a subsystem while degrading the whole?
- Whose problem am I creating by solving mine?

## 6. STOCK VS FLOW
- Am I changing accumulation (stock) or rate of change (flow)?
- Which actually matters here?

## 7. MENTAL MODEL CHECK
- What assumption am I making that's invisible to me right now?
- What would someone with opposite constraints see immediately?

---

**The real question beneath all of these:**
## "What system am I *actually* in, and what game am I *actually* playing?"

Most errors come from misidentifying the system boundary. Get that right, the rest follows.

Continue Conversation...

Get Action Items

I am setting up a weekly Monday cadence meeting. What actions, activities, ideas, exercises, questions, etc. do you think should be in it?

# Engineering Your Monday Cadence Meeting: A Systems-Based Approach

Your question appears simple but contains deep systems implications. A cadence meeting isn't just a meeting - it's a critical feedback mechanism within your organizational operating system.

## First Principles Analysis

Before prescribing activities, consider what function this meeting serves in your broader system:
- Is it for information flow optimization?
- Decision acceleration?
- Problem-solving coordination?
- Team alignment reinforcement?

## High-Leverage Design Elements

1. **Systems Review (15 min)**
- Track key metrics as behavior-over-time graphs
- Identify emerging patterns before they become problematic events
- Ask: "What feedback loops are strengthening or weakening?"

2. **Constraint Identification (10 min)**
- What's limiting system performance this week?
- Is it a resource stock, information flow, or mental model constraint?

3. **Decision Velocity Mechanism (15 min)**
- Clear blocking decisions with explicit ownership
- Document decision criteria to strengthen organizational memory

4. **Proactive Loop Detection (10 min)**
- What potential unintended consequences might emerge from last week's decisions?
- Are we building reinforcing loops that could accelerate out of control?

5. **Close with System Reflection (5 min)**
- "What mental models shifted today?"
- "Where might we be blind to interconnections?"

The meta-goal: Design this meeting to be self-reinforcing rather than energy-draining. A poorly designed cadence meeting creates a negative feedback loop that diminishes engagement over time.

Remember - the meeting itself is an intervention point in your broader system. Design it accordingly.

Continue Conversation...

Get Action Items

What should be the starting point of goal-oriented action?

From a systems thinking perspective, the starting point of goal-oriented action should emphatically not be the goal itself. This common approach is a dangerous oversimplification that ignores the complex web of interconnections in which our goals exist.

Instead, the critical starting point should be a comprehensive systems analysis. Here's what you should do:

1. Map the system: Begin by identifying all relevant elements, stakeholders, and environmental factors related to your goal. Draw out the connections between these elements, paying special attention to feedback loops and delays.

2. Identify mental models: Uncover the underlying assumptions and beliefs that shape the current system. These often invisible factors can have profound effects on system behavior.

3. Analyze system behavior over time: Look at historical trends and patterns. What has the system been doing? Why? This will help you understand the system's inherent tendencies and resistance to change.

4. Look for leverage points: Identify areas within the system where small changes could lead to significant shifts. These are often not where conventional wisdom would suggest.

5. Anticipate unintended consequences: Consider how changes in one part of the system might affect other areas, potentially in counterintuitive ways.

6. Question the goal itself: Is your initial goal actually addressing the root issue, or is it merely targeting a symptom? The systems analysis may reveal that your original goal needs to be revised or completely changed.

7. Plan for continuous learning and adaptation: Recognize that your understanding of the system will always be incomplete. Plan to regularly reassess and adjust your approach based on new information and emerging system behavior.

Remember, jumping straight to action without this thorough systems analysis is likely to result in ineffective interventions or, worse, actions that exacerbate the very problems you're trying to solve. Avoid the temptation to rush towards a solution. In systems thinking, the quality of your initial analysis and system understanding is paramount to achieving lasting, positive change.

Continue Conversation...

Get Action Items