The Necessary Tangle

Systems thinking · Start here

Why does this keep happening?

The waiting list grows. Another reorganisation leaves the same tensions. Everyone meets their target, yet the service gets harder to use.

Systems thinking helps you investigate how a situation is produced and kept going: the relationships, rules, habits, resources, and feedback that shape what people can do. It also asks how your own position affects what you notice and what you can change.

You can begin with a real situation and a few careful questions. The methods become useful as the inquiry needs them.

Try a ten-minute inquiryFollow a guided journey

What to pay attention to

01 · Patterns over time

Look beyond the latest incident

What keeps returning? What builds up, drains away, or gets passed on? Compare accounts and records over time before settling on an explanation.

Explore feedback
02 · Relationships and consequences

Follow what happens next

A decision changes someone else’s work. Their response changes yours. Ask where the consequences return, how long that takes, and who absorbs the extra work.

Follow a feedback journey
03 · Boundaries and power

Ask whose situation this is

People disagree about the purpose, the problem, and who should decide. Your map has an edge. Someone affected by the decision may be outside it.

Explore boundaries
04 · Your part in it

Include yourself

Your questions, measures, authority, and interventions affect the situation. Ask what you’re helping to reproduce, and invite someone else to challenge your account.

Explore the observer

A waiting list that keeps growing

This is an illustrative service example. It suggests things to investigate; it doesn’t diagnose a particular service.

  1. A service introduces a response-time target. Staff can meet it by sending an acknowledgement.
  2. People still need an answer, so they call again. Some send a second application because they don’t know what happened to the first.
  3. Checking duplicates and answering chasers takes time from completing the original work. The queue grows.
  4. The dashboard reports faster responses. People experience longer waits.

A useful inquiry would follow several requests from first contact to resolution, count repeat contacts, ask people what they needed, and check how the target changes staff decisions.

A small test might give one team time and authority to resolve a defined group of requests. Track completed work, repeat demand, staff workload, and effects elsewhere. Agree when to review or stop the test.

The system boundary changes the judgement: an acknowledgement can count as success for a team and leave the person’s purpose entirely unmet.

Try a ten-minute inquiry

Take something that has happened more than once. Use paper, or talk these questions through with someone who sees a different part of it.

  1. Name the pattern. What keeps happening? Separate what you’ve observed from what you think explains it.
  2. Follow the consequences. What happens next? What comes back? What accumulates? Where are the delays?
  3. Hear another account. Who experiences this differently? Who is affected but has little say?
  4. Locate your influence. Which decisions, rules, relationships, or resources can you alter? Where do you need somebody else’s agreement?
  5. Make one move and learn. What could you try? Who will carry any downside? What would you watch, and when would you reconsider?

Keep the account provisional. If it explains every possible outcome, it isn’t helping you distinguish what is happening.

Take your question into the atlas. The atlas suggests entries and connections for you to inspect.

Three overlapping fields

Systems thinking
Ways of working with relationships, wholes, purposes, and boundaries. Different traditions offer different accounts of what a system is and how we can know it.
Cybernetics
Inquiry into communication, regulation, learning, and how systems respond. Some traditions explicitly include the observer and the effects of observing.
Complexity
Work on interacting processes that produce patterns across scales, often with nonlinear effects and limits to prediction. Saying ‘it’s complex’ still leaves the mechanism to investigate.
Systems practice
Using ideas and methods in a particular situation, with judgement about purpose, participation, power, evidence, and consequences. Systems leadership, change, convening, and weaving make further distinctions.

Choose an approach for the work

These are starting points. Each approach has assumptions, limits, and a body of practice worth learning. Several may help with the same situation.

People disagree about the problem

Soft Systems Methodology helps people explore different purposeful accounts and find changes they can work with. Don’t use a diagram to pretend the disagreement has vanished.

A recurring pattern has delays and accumulations

System Dynamics helps examine stocks, flows, feedback, and behaviour over time. A plausible loop diagram still needs evidence; a simulation needs defensible assumptions.

An organisation can’t respond to what it faces

The Viable System Model helps examine operations, coordination, management, adaptation, and identity at several levels. Start with what the organisation must cope with.

Some people define success for everybody else

Critical Systems Heuristics helps question who benefits, who decides, whose knowledge counts, and whose concerns are excluded.

You need to learn across organisational boundaries

Systems convening works with relationships, legitimacy, identity, and social learning. Attendance at a meeting tells you little about whether people can act together.

You can’t reliably predict the response

Explore adaptation and emergence. Design bounded experiments with the people affected, observe more than the intended result, and agree how to stop or change course.

Keep going

Join the wider conversation

Systems Community of Inquiry carries current writing, papers, arguments, and events across systems | cybernetics | complexity.