---
title: "What is Systems Thinking?"
description: "Systems Thinking is seeing how the parts of an organisation interconnect — the feedback loops, the delays, and the second-order effects a local fix sets off elsewhere. It shows as anticipating where a change will surface as somebody else's problem, and designing for the whole rather than optimising one function into trouble."
canonical: https://www.assessall.com/framework/systems-thinking
updated: 2026-08-30
source: AssessAll
---

# What is Systems Thinking?

Systems Thinking is seeing how the parts of an organisation interconnect — the feedback loops, the delays, and the second-order effects a local fix sets off elsewhere. It shows as anticipating where a change will surface as somebody else's problem, and designing for the whole rather than optimising one function into trouble.

_Thinking & Judgment domain, AssessAll Capability Framework. Last reviewed 2026-08-30._

<!-- #levels -->
## What systems thinking looks like at four levels

- **Developing (0–39)** — You tend to focus on the direct, first-order effect of a change and get surprised by the knock-on consequences. Training yourself to ask 'and then what?' twice more will prevent a lot of avoidable problems.
- **Emerging (40–59)** — You consider some ripple effects but mainly within your own area. The growth is in tracing consequences across teams and over time.
- **Strong (60–79)** — You routinely anticipate second-order effects and how a change in one place shows up elsewhere. You design for the system, not just the symptom.
- **Exceptional (80–100)** — You see the whole system — feedback loops, delays, and unintended consequences — and intervene at the points of real leverage rather than the obvious ones.

<!-- #anti-signals -->
## Signs it is missing

- Solves a problem in one team and creates a larger one two teams away, repeatedly.
- Treats a recurring failure as a series of unrelated incidents.
- Optimises a metric until the behaviour it was proxying disappears.

<!-- #evidence -->
## Evidence to look for

- Describe a fix you made that caused a problem somewhere else. When did you see it coming?
- What is a metric your organisation optimises that you think is quietly distorting behaviour?
- Take a recurring incident in your area and tell me what actually keeps producing it.

<!-- #develop -->
## How to develop it

- For your next decision, list who is affected who isn't in the room, and what they'll do in response.
- Practise the 'and then what?' chain: push every proposed fix two consequences deep before approving it.
- When a problem recurs, look for the structure or incentive producing it rather than treating the instance.

---

Source: https://www.assessall.com/framework/systems-thinking