Protecting revenue when the operating system breaks
How companies can design for revenue and value continuity when shocks disrupt customers, channels, technology or supply.
Read articleWho knows something the business cannot afford to lose?
Critical knowledge is rarely identical to seniority or job title. It often lives with the person who understands an exception, maintains a trusted relationship, recognises a weak signal or knows why a process was designed around a constraint that documentation no longer mentions.
Map knowledge through outcomes. For each essential decision or service, ask what must be known, who can apply it unaided, how long replacement would take and what happens if it is unavailable. Prioritise knowledge that is both critical and vulnerable�a principle made explicit in the 2026 draft revision of ISO 30401.
Observe work under variation. Interviews capture stated procedure; incident reviews, complex cases and handovers reveal tacit judgement. Record not only steps, but cues, trade-offs, contacts, source authority and stop conditions. A runbook that omits rationale lets a successor repeat actions without knowing when they are wrong.
Reduce dependency through pairing, shadowing, rotation, communities of practice, decision logs and deliberate succession. Give another qualified person real responsibility while the expert is available to correct the system. Protect external knowledge held by contractors and suppliers with access, continuity and transfer provisions.
Test resilience by removing the key person from an exercise and measuring decision delay, errors and escalation. Track single-qualified roles, time to competence, stale documentation and coverage of critical cases. The goal is not to copy everything one individual knows; it is to make the organisation capable of acting when that individual cannot be reached.
Related macro
Articles
How companies can design for revenue and value continuity when shocks disrupt customers, channels, technology or supply.
Read articleWhy enterprises need to shift from static recovery plans to adaptive systems that connect operations, suppliers, people and critical dependencies.
Read articleFocus
Reputational resilience begins with understanding which expectations matter enough that violating them could materially change trust or behaviour.
Crisis governance must make authority explicit before several teams begin making overlapping decisions from different versions of the situation.
Strategic challenges
Changes in systems, suppliers, locations and responsibilities can quietly invalidate recovery assumptions long before the next formal review.
Demand, pricing, currencies, financing costs and supplier pressures can reinforce one another and create consequences larger than isolated sensitivities imply.
POV
Readiness comes from exercising decisions, dependencies and recovery actions, not from approving a document and storing it.
Sales can return while customer trust, market position or recurring economics remain permanently weaker after prolonged disruption.
Strategic impact
Maintaining credible alternatives can create value when conditions move beyond the assumptions embedded in the original operating model.
Distributing essential capabilities across more than one person or team gives the organisation credible alternatives when normal capacity disappears.
What we observe
We frequently see recovery priorities based on process criticality without quantifying which failures create the greatest commercial loss.
We frequently see supplier assessments overlook the shared technologies, facilities and upstream dependencies that determine actual continuity.