Protocol

Move from the event down the systems iceberg

The visible incident may be the smallest part of the problem.

About 1 min read

Before you use it

Use when
  • A recurring problem keeps producing local fixes without changing the pattern.

Keep this limit in mind

  • Do not present an inferred 'mental model' as a fact about another person; verify assumptions and prefer observable structures first.

An idea to explore.

Try this idea.

Inspect the example, try the idea in your situation, then check your next move.

Keep reading

Why it matters

Start with the event, then ask what pattern appears over time, what structures make that pattern likely, and what assumptions or mental models help preserve those structures. Treat each deeper layer as a hypothesis to check against evidence. The point is to widen the intervention space beyond repairing the latest occurrence.

Steps

  1. The analysis produces at least one structural hypothesis that could be tested or changed beyond the immediate event.

An example

Repeated urgent data fixes may point beyond individual mistakes to ownership, validation and release structures that keep producing them.

Check your result

The analysis produces at least one structural hypothesis that could be tested or changed beyond the immediate event.

Save and practise this idea

My learning

Read. Recall. Repeat.

Save this idea and return to it on any device.

Use email
Keep exploring

Connected ideas

You are readingMove from the event down the systems iceberg

Evidence and sources
Supports

The Donella Meadows Project presents the iceberg model as connecting a visible event to patterns of behavior, system structures and underlying mental models.

The deeper layers are prompts for investigation and should not be presented as established causes without evidence.

Systems Thinking Resources · The Iceberg Model

All sources (1)
Edition and review

Version 0.1.0

No review details are supplied for this edition.

Read this idea as JSON · Release details