Patterns · Feedback · Leverage
Learn Systems Thinking
Systems thinking is the disciplined practice of understanding how relationships, feedback, delays, boundaries and perspectives interact to produce patterns and outcomes that no single part explains alone.
Builds your Adaptability and Critical Thinking capability.
Start here · one first move
Choose a recurring problem and describe its behavior over time.
Field guide 03
Understand
A working definition
In practice
Maps actors and relationships, looks for patterns over time, tests system boundaries, traces reinforcing and balancing loops, and seeks leverage rather than treating symptoms.
Why this matters now
AI can optimize a local task while shifting cost, risk or workload elsewhere. Systems thinking helps people see what the optimization changes across the wider human and organizational system.
It is
- Relational and dynamic.
- Concerned with patterns over time.
- Explicit about boundaries and perspectives.
- Interested in consequences and leverage.
It is not
- Making a diagram for its own sake.
- Treating everything as equally connected.
- Avoiding decisions because complexity exists.
- Assuming one model is the whole reality.
The capability loop
Move from events to leverage.
Complex outcomes become more understandable when the inquiry moves beyond the visible event.
- 1
Frame whole
What system and outcome are we trying to understand?
- 2
Map
Which actors, resources, rules and relationships matter?
- 3
Trace
What patterns, feedback loops and delays produce the behavior?
- 4
Test
What changes across time, perspectives and system boundaries?
- 5
Leverage
Where could a focused intervention alter the pattern?
Go deeper
The full field guide
8 connected capabilities+
A system becomes visible through relationships, patterns, feedback, boundaries and purpose.
- Interconnection recognition
- Identifies direct, indirect and reciprocal relationships.
- Pattern identification
- Recognizes recurring behavior and change over time.
- Boundary awareness
- Chooses and tests what the analysis includes or excludes.
- Feedback loop analysis
- Distinguishes reinforcing and balancing dynamics.
- Perspective integration
- Examines how the system appears to different stakeholders.
- Level shifting
- Moves between local detail and wider structures.
- Change anticipation
- Explores delays, ripple effects and unintended consequences.
- Leverage identification
- Finds places where focused change may alter the pattern.
The components strengthen one another. Development depends on how they are combined in context—not on maximizing one behavior in isolation.
Behaviour map+
01
Before
- Name the pattern Describes what repeats or changes over time.
- Set a boundary States what is included, excluded and why.
- Invite perspectives Identifies who experiences the system differently.
- Question the event Avoids treating the latest incident as the whole problem.
02
During
- Map relationships Connects actors, rules, resources, information and incentives.
- Trace feedback Looks for cycles that reinforce or balance behavior.
- Notice delay Separates immediate effects from consequences that arrive later.
- Shift levels Checks how local action interacts with wider structures.
03
After
- Test ripple effects Explores who gains, loses or carries new work.
- Choose leverage Targets a relationship, rule, flow or information gap.
- Run a probe Uses a bounded experiment instead of claiming certainty.
- Update the map Changes the model when reality returns new evidence.
Case story · composite+
When AI shortens calls but lengthens the customer journey.
The local optimization was working.
The challenge.
A service organization uses AI prompts to reduce call duration.
The target improves, yet repeat contacts, employee escalation and customer frustration rise. 1 · Frame whole The team reframes success from short calls to resolved customer needs. 2 · Map They connect prompts, call targets, agent discretion, handoffs and repeat contacts. 3 · Trace A reinforcing loop appears: shorter calls create unresolved issues, which create more calls and pressure. 4 · Test Customer and frontline perspectives reveal that complex cases need continuity, not more speed. 5 · Leverage The pilot protects human discretion and measures first-contact resolution and total journey effort.
Capability in practice The local optimization was working.
The wider system was producing the failure.
Leadership and learning culture+
- Frame Define success across the full human and operational journey.
- Connect Bring functions and affected stakeholders into the same inquiry.
- Map Make assumptions, feedback loops and delays discussable.
- Probe Use safe experiments and watch for displacement or rebound effects.
- Learn Update policies and metrics when the system behaves differently than expected.
Why we protect this skill — HI · FRI · IMPACT+
Human Core
How central should human agency, judgment and responsibility remain?
uman leads
▰▰▰▰▱
Future Readiness
How strongly does this help people learn and act as roles and technology change?
Foundational
▰▰▰▰▰
Safeguard Value
How strongly does this protect capability from over-reliance, deskilling and loss of agency?
Critical safeguard
▰▰▰▰▰
They describe why the capability matters—not how advanced a learner is. AI can help map variables and simulate scenarios. People must choose the boundary, include affected perspectives, interpret meaning and own interventions in the real system.
Practice
WIDEN the view.
Use this short structure in real work, reflection or coaching. Keep the action specific enough to observe.
- W
Whole
What larger system and pattern are we trying to understand?
- I
Interactions
Which actors, rules, resources and relationships matter?
- D
Dynamics
What reinforces, balances or delays change?
- E
Effects
Who experiences intended and unintended consequences?
- N
Next leverage
Where might a focused experiment alter the pattern?
One-minute start: “The event is ... The repeating pattern is ... The relationship we should examine is ...” The protocol supports practice. It does not remove the need for context, expertise, ethical judgment or appropriate human support.
Seven-day experiment
Map one persistent pattern in seven days.
0 of 7 days marked · saved on this device
Prove it
Five stages of systemic inquiry.
The progression describes increasingly contextual, dynamic and socially useful analysis - not intelligence or the ability to make a complicated diagram.
L1
Connect
Recognizes obvious relationships and simple consequences with support.
L2
Map
Identifies several actors, influences, perspectives and a workable boundary.
L3
Explain
Uses patterns, feedback and delays to explain why an outcome persists.
L4
Anticipate
Tests boundaries and explores second-order effects across levels and time.
L5
Enable
Helps groups build shared system insight, locate leverage and learn from interventions.
Use the progression well Ask for the next observable behavior—not a label for the person.
Ask Markku-AI about Systems Thinking
Pick a question. Markku-AI answers from the Skills Pathfinder material.
Read the full minibook
Systems Thinking
The printed A5 field guide — same content, typeset for paper.