Systems thinking · 4/6
See delays: why repeated adjustments can overshoot
Separate observation and response delays and choose review intervals.
About 15–20 minutes. The following cases are fictional.
Record your first judgment
New staff need two weeks of training; a manager escalates again after one day without improvement.
Understand the judgment process
Action and effect may be separated in time. Unobserved effects are not necessarily zero; repeated escalation may accumulate excess response.
Our simulator schedules capacity using an older queue observation. It is not a training model or a staffing recommendation.
Checks you can perform
- Date the intervention.
- Estimate when effects become observable.
- Set monitoring and stop conditions during the wait.
- Separate demand changes from the response process.
Guided practice
Training is expected to work in two weeks, but the queue grows on day three. Is it a failure?
Explore the explanation
Not on that observation alone. Check implementation, demand shocks and safety or quality thresholds.
Apply it in a new context
A soil sensor updates late after watering. What can repeated watering do?
Compare after attempting
Repeated response to the same stale reading may overwater. Check timestamps, drainage and moisture instead of abandoning watering altogether.
Preserve an intervention record
Waiting is not ignoring signals. Clear risks can justify action before an expected delay ends.
Check whether you supplied inspectable evidence, a feasible next step and intervention conditions. Revealing an answer is not mastery.
Source and scope
Donella Meadows — Leverage Points: Places to Intervene in a System
The source provides conceptual or methodological background. Cases, steps and exercises are authored here; they are not the original experiment or evidence of this course’s effectiveness.
Completion is a personal record, not proof of mastery or certification.