Supply Chain LabRipple EffectLab Home
Risk & Resilience · Disruption propagation

Ripple Effect

This is not the bullwhip. Bullwhip is demand noise amplifying upstream in a healthy network. A ripple is one structural failure - an earthquake, a closed port, a dead DC - propagating downstream like a wave, eating buffer after buffer until shelves go empty. Pick a shock, watch the wave spread across the real network, and spend a limited budget on re-routing and buffers to contain it. Score = service protected minus money burned.

The network - day 0/30

flowing burning buffer down / starved backup lane active · line thickness = flow share

Control room

Service
100%
Budget left
$100k
Outage
-
Score
-
✈️
Air-freight bridgeSuppliers → DCs direct, bypasses the port · covers 60% of need · $3k/day while on
🔁
Cross-dock linkHealthy DC feeds the other's retailers · up to 40% · $3k/day while on
📦
Emergency buffer release+4 days of cover at the port & both DCs · one-off $12k
⏱️
Expedite recoveryCut the outage by 3 days · one-off $15k

Event log

Pick a shock scenario, optionally pre-arm mitigations, then Run. Buffers delay the wave - they don't stop it.

About this game

The Ripple Effect (Ivanov)

The concept

One structural failure propagates downstream, disabling capacity node by node - resilience, not demand noise. Bullwhip amplifies orders upstream; ripple destroys flow downstream.

How it works

Each node holds days-of-cover. When inflow drops, the node burns buffer, then passes the shortage on - the wave's speed is set by buffer depth.

Winning strategy

Buffers buy time; only re-routing stops the wave. Spend early and switch paid lanes off the day the outage ends - TTR beats panic.

resilience = avg service% − mitigation spend / $4k
Ripple effectResilienceTime-to-recoverSingle point of failure
Teaching moment: run the earthquake once with no mitigations, then replay spending early - the class sees why resilience is bought before the disruption, not during.