When a disruption hits, the cost isn’t fixed at the moment it happens. It accumulates while you work out what to do. Two organisations facing the same port closure can end up with completely different outcomes, and the difference is usually response time rather than contingency planning.
Why Response Is Slow
The delay is almost never a lack of options. It’s the time taken to establish what’s actually affected.
News arrives that a lane is closed. Someone has to work out which shipments were on that lane, which materials those shipments contained, which production orders need those materials, which customer orders depend on those production runs, and which of those customers will accept a delay. In most manufacturers this takes days of phone calls and spreadsheet work, spread across people who each hold one piece.
By the time the picture is assembled, the good alternatives have been taken by faster competitors. Air freight capacity is booked. The alternate supplier has committed their spare volume. You’re now choosing between expensive options rather than sensible ones.
What Fast Response Requires
Connected data is the whole game. If shipments, materials, production orders, and customer commitments live in one linked model, the impact chain resolves in seconds rather than days. That’s not an analytics feature — it’s a data architecture question, and it has to be true before the disruption, not arranged afterwards.
Pre-evaluated alternatives are the second requirement. Knowing that a component has a qualified second source is useful. Knowing their current lead time, their available capacity, and their price is what lets you act within the hour. Keeping that information current for critical items is unglamorous work that pays for itself the first time you need it.
Pre-agreed decision authority is the third and most overlooked. If rerouting a shipment at a four-times freight premium requires approval from someone who’s travelling, the delay is organisational, not informational. Set thresholds in advance: below this cost, the planner decides; above it, escalate. Written down, before anything happens.
Choosing Well Under Pressure
Not every disruption warrants an expensive response. Some delays are absorbable — the customer has buffer, the order isn’t due for six weeks, the finished goods stock covers it. Paying a large premium to protect a date that didn’t need protecting is a common and avoidable error made in the first hour of panic.
The useful question isn’t how to fix the delay. It’s what the delay actually costs if you do nothing, compared to what fixing it costs. Answering that requires visibility of downstream commitments, which loops back to connected data.
Practising
Run the exercise cold. Pick a supplier or a lane and ask your team to produce the impact picture as though it had failed this morning. Time them. The first attempt usually takes far longer than anyone expects, and the bottlenecks it exposes are precisely what to fix.
ticktick.ai links shipments, materials, production orders, and customer commitments in one model, so impact traces through in seconds and rerouting options can be compared against what the delay would actually cost.
