← Applying business knowledge to a critical problem

Internal operational failures (technology, stock control, order fulfilment)

A recurring problem TYPE distinct from an external threat: something breaks INSIDE the business's own processes, and the fix must attack the internal cause.

Reading an operational-failure scenario

• IDENTIFY THE SYMPTOM: what customers or staff are actually experiencing (missing order confirmations, wrong or incomplete orders, slow deliveries).
• IDENTIFY THE CAUSE: usually named or strongly implied in the resource — an outdated or incompatible system, insufficient stock control, unclear internal processes, or under-trained staff.
• TRACE THE SUSTAINABILITY IMPACT: repeated failures cause customers to cancel orders and switch to competitors, directly damaging both current revenue and the brand's longer-term reputation for reliability — a genuine threat to ECONOMIC SUSTAINABILITY, not just a one-off inconvenience.
• SOLUTIONS should attack the SYSTEM causing the failure (upgrading or replacing incompatible software, improving stock-tracking processes, retraining staff) rather than just apologising to affected customers after the fact.

Worked example Explaining why an outdated ordering system threatens sustainability A furniture manufacturer's online ordering system cannot cope with rising order volume, causing missing confirmations, incorrect orders, and deliveries taking four to six weeks instead of the advertised one week. Explain how this could affect the business's ability to operate as a sustainable business. IMMEDIATE PROBLEM: customers experience unreliable ordering and slow delivery, well outside what was advertised. CUSTOMER RESPONSE: frustrated customers cancel orders and switch to competitors who can deliver reliably. REVENUE IMPACT: lost sales reduce current revenue, while refunds/cancellations add administrative cost. LONGER-TERM SUSTAINABILITY: word-of-mouth and reviews about unreliable service damage the brand's reputation for future customers too, making the problem compound over time rather than staying a one-off issue — threatening the business's ability to keep operating profitably. ✓ The strongest answers trace the chain all the way from the specific technical symptom (order errors) through to the LONG-TERM sustainability consequence (compounding reputational damage), not just "customers will be unhappy". ✕

Proposing a customer-facing fix without addressing the underlying system

A solution like "apologise to affected customers" or "offer a discount" treats the SYMPTOM, not the CAUSE. The schedule rewards solutions that fix the actual system failure (e.g. upgrading incompatible software, improving stock-tracking) — a customer-facing gesture alone will not stop the same failures recurring.

Symptom	Likely underlying cause
No order confirmation / error messages	Incompatible or overloaded ordering software
Incorrect or incomplete orders	Poor stock-control or data-entry processes
Slow delivery vs advertised timeframe	Warehouse/logistics capacity not scaled to demand

Practice for this standard covers the whole topic — flashcards and quiz.