Example scenarios

Inspect the reasoning.

Three representative scenarios show how requirements, observations, dependencies and open questions can shape a practical resilience decision.

About these examples

Each scenario uses representative information to show how the method works. No client organization is named.

01Business service resilience

Customer orders cannot be processed for one working day

Which customer orders must still be processed if the order platform is unavailable for one working day?

Information considered

01Customer commitments due today
02Sales and dispatch share one order platform
03Manual process supports limited volume
04Priority-order rules not yet agreed
Current resultPriority decision neededReady for leadership discussion
Situation

Sales, customer service and warehouse dispatch depend on the same order platform. A staff sign-in failure makes the platform unavailable, while the manual workaround can handle only a limited share of normal volume.

Practical direction

Protect urgent and contract-critical orders, activate a controlled manual process, restore the order platform and coordinate customer updates.

Illustrative output

Business impact view, prioritized orders, workaround actions and a concise leadership report.

Open the interactive case study
02Third-party resilience

A critical supplier cannot deliver for three days

Which products or services can continue if a critical supplier cannot deliver for three days?

Information considered

01Critical input supplied from one source
02Available stock covers limited demand
03Alternative supplier not yet confirmed
04Activation owner and deadline unclear
Current resultActivation decision neededReady for leadership discussion
Situation

One supplier provides an input used across several products or services. Available stock is limited, and the alternative supplier has not been confirmed for timing, capacity or quality.

Practical direction

Reserve available stock for priority commitments, confirm alternative capacity and quality, and set a clear activation deadline.

Illustrative output

Affected commitments, inventory choices, supplier options and prioritized actions.

03Recovery assurance

The recovery plan promises four hours, but testing shows eleven

Can the organization rely on a four-hour recovery target when the latest end-to-end test took eleven hours?

Information considered

01Approved recovery target: 4 hours
02Latest end-to-end test: 11 hours
03System restoration completed earlier
04Business validation and partner delay recorded
Current resultRecovery gap confirmedReady for leadership discussion
Situation

The system itself returned sooner, but data checks, specialist availability and a downstream partner extended full business-service recovery to eleven hours.

Practical direction

Keep four hours as the business requirement, address the delays found in testing and retest the full service before reporting the target as proven.

Illustrative output

Target-versus-test comparison, recovery bottlenecks and an integrated retest plan.

Apply the pattern

Bring one real resilience decision into focus.

We will shape the information and analysis around your situation rather than reuse a fixed template.

Book a 30-minute consultation