Scenario Testing for Supplier Failure

A supplier failure scenario rehearses what happens when a provider that a service depends on stops, degrades, or cannot be reached, and the firm must still serve its customers. The test is not whether the supplier failed, since that is given in the story, but whether the firm has a credible alternative, a clear order of priorities, and honest communication while the alternative is put in place. Many services depend on suppliers for processing, data, communications or infrastructure, and the failure may be partial rather than total, which makes decisions harder. A scenario that assumes a perfect substitute appears immediately will teach very little, while one that forces a choice between a slow alternative and a pause in service will teach a great deal.

Supplier failure takes several forms, and each form tests different decisions. A sudden outage tests workarounds and customer communication. A gradual degradation tests thresholds: at what point does a slow or inaccurate feed become unusable, and who makes that call? A supplier under its own cyber incident tests trust, since the firm may receive data or files it cannot verify. A supplier that exits a market tests longer term substitution and contract arrangements. Consider a card processing service that relies on a single gateway for authorisations. A scenario in which the gateway degrades during a busy trading period forces a different set of choices from a scenario in which the gateway announces withdrawal, and the firm should rehearse both kinds rather than treating supplier failure as one generic event.

A substitute is credible only if it has been thought through in advance. The scenario should ask whether the alternative can handle the volume, whether customer data can move safely, whether staff know how to operate it, and whether contracts and access are already in place. A substitute that exists on paper but needs new credentials, new testing or new customer instructions is not ready, and an exercise is the place to discover that. Participants should also consider partial substitution: serving the most urgent customer needs through an alternative while less urgent work waits. That kind of prioritisation is uncomfortable, but it is often the most realistic response, and rehearsing it in advance makes it easier to explain to customers when it matters.

Concentration changes a supplier scenario because failure may affect several services at once, or several firms at once. A widely used cloud region, a common data provider, or a shared messaging network can create a single point of failure that individual service maps understate. The scenario writer should therefore look beyond the direct supplier to shared dependencies underneath it. If two apparently separate suppliers rely on the same infrastructure, the loss of that infrastructure is the scenario, not the loss of either supplier alone. Exercises that bring together owners of affected services can reveal competition for the same substitute, conflicting priorities, and communication that must be coordinated rather than sent service by service.

Communication in a supplier failure scenario involves the supplier, customers, and sometimes other firms that depend on the same chain. The firm needs to establish what the supplier can and cannot confirm, and to avoid repeating supplier assurances that have not been verified. Customers need a plain account of what is affected and what alternative, if any, is available. Internal communication matters too: front line staff need approved wording before customers contact them, otherwise each member of staff improvises. An exercise should rehearse the sequence of those messages, including what happens when the supplier goes quiet. Silence from a supplier is itself information, and the scenario should force a decision about how long to wait before acting without it.

After a supplier failure exercise, change should be visible in the service arrangements, not only in the exercise report. Possible changes include a revised workaround, a clearer threshold for switching to an alternative, an updated contact route, a contract discussion, or a decision to reduce dependence on a single provider. Each change needs an owner and a way of checking that it has happened. If the exercise revealed that a substitute cannot work, that finding should not be softened in the report. A supplier scenario that ends with a list of comfortable actions and no difficult decision has probably been designed to succeed, which is the pitfall this cluster warns against throughout.