See at three levels: event, pattern, and structure

Ask "what pattern produced this event?" and then "what structure is producing that pattern?"

Why it works

Event-level thinking (reacting to what just happened) is the default but misses the structural cause. Pattern-level thinking asks what has been happening over time — often revealing a trend or cycle. Structure-level thinking asks what circular relationships, delays, and accumulations produce that pattern. Senge argues that lasting interventions almost always operate at the structural level; event-level fixes typically just move the problem around.

How to do it

1. Name the event: what specifically happened?
2. Ask: "Has this happened before? What pattern does this event fit?"
3. Ask: "What feedback loops or structural relationships could reliably produce this pattern?"
4. Identify whether your proposed fix addresses the event, the pattern, or the structure — and plan accordingly.

Evidence

The three-level model (event, pattern, structure) is foundational to system dynamics as a discipline, developed at MIT through Forrester’s and Senge’s work. Organizational case studies document structural causes of recurring problems that event-level interventions failed to solve. (mechanistic)

Controlled empirical studies on systems thinking training in organizations are limited; most evidence is case-based and observational. The framework is powerful but does not guarantee correct structural diagnosis.

Sources

• Senge (1990), The Fifth Discipline — the iceberg model as a framework for system levels

Common mistake

Identifying a structural cause but then implementing an event-level fix anyway because it is faster — this is called "treating symptoms" and is one of Senge’s core system archetypes (fixes that fail).