Chapter 5
Recovery and Stabilisation
Chapter 5
Recovery and Stabilisation
Recovery does not start when the crisis ends. It starts when control is restored.
This distinction matters because it changes when the organisation acts. An organisation that waits for the crisis to end before beginning recovery will find that the crisis does not end cleanly, it fades gradually, leaving behind a trail of unresolved exceptions, informal workarounds and process adaptations that were appropriate during the crisis and are inappropriate after it. By the time the organisation declares the crisis over, the damage to its processes has already been done.
An organisation that begins recovery at the moment control is restored does not wait for the crisis to end. It identifies the point at which it has enough capacity and enough stability to start the structured work of returning its processes to their designed state and it begins that work immediately, while the crisis is still fading, before the adaptations made during the crisis become permanent.
Recovery restores structure. It is not about returning to the exact state the organisation was in before the crisis, that state had weaknesses that the crisis exposed. Recovery is about restoring the organisation to a state of controlled, consistent, documented operations and using what was learned during the crisis to make those operations more resilient than they were before.
Stabilisation follows recovery. It is the sustained period of consistent operation that confirms the recovery is complete, that the exception rates have returned to normal, that the workarounds have been resolved, that the process adaptations have been reviewed and either formalised or reversed.
Neither recovery nor stabilisation happens automatically. Both require deliberate management.
Key Takeaway:
Recovery begins when control replaces reaction. The organisation that waits for the crisis to end before beginning recovery will find the damage already done. The organisation that begins recovery at the moment control is restored will limit that damage.
"Recovery starts when decisions become controlled again."
MarvinPro_|_March_2026
marvinpro.com
During a crisis organisations operate reactively. Decisions are made in response to immediate pressures rather than according to defined processes. Actions are taken to resolve the most urgent problems rather than to address the underlying causes. The team's energy is consumed by the present moment, there is no capacity to think about what comes next.
This reactive mode is appropriate during the acute phase of the crisis. When the situation is changing rapidly and the consequences of inaction are immediate, reaction is the correct response. The structured, deliberate decision-making that characterises normal operations is too slow for a crisis environment.
The problem is that reactive mode does not switch off automatically when the acute phase ends. The team that has been operating reactively for days or weeks does not spontaneously shift back to structured operations when the immediate pressure subsides. The habits formed during the crisis persist. The informal decision-making continues. The workarounds remain in place. The team continues to operate reactively because reactive mode worked, the crisis was managed, the operation continued, the immediate problems were resolved.
The shift from reaction to structure requires a deliberate intervention. Someone must make the decision that the acute phase is over and the recovery phase has begun. The immediate decisions that were appropriate during the crisis must be converted into repeatable actions, documented, assigned and governed. The workarounds that were created during the crisis must be evaluated, which ones should be formalised as process improvements, which ones should be reversed now that the crisis has passed. The escalations that multiplied during the crisis must be reduced through clarity, by defining the handling for the scenarios that generated them, so that the next occurrence is resolved at the process level rather than the escalation level.
Structure does not slow operations. It enables consistency. The team that is operating according to defined processes is faster and more reliable than the team that is making individual decisions for every scenario it encounters even if it does not feel that way in the moment.
Key Takeaway:
Recovery requires a deliberate shift from reactive decisions to structured processes. This shift does not happen automatically, it requires a decision, an intervention and the discipline to maintain the structured approach even when the reactive habits of the crisis period are still fresh.
"Reaction solves the moment. Structure stabilises the system."
MarvinPro_|_March_2026
marvinpro.com
Every crisis creates accumulation. Transactions that could not be processed during the acute phase. Decisions that were deferred because the team had no capacity to make them. Exceptions that were logged but not resolved. Workarounds that were created and then abandoned without closure. Cases that were opened by customers who did not receive a response and opened again and again.
This accumulation, the exception backlog is the most tangible legacy of the crisis. It is visible, measurable and actionable. And it must be addressed systematically, because the organisation cannot stabilise while the backlog remains.
The instinctive approach to a backlog is to work through it in the order it arrived, oldest first, newest last. This approach feels fair and logical. It is almost always wrong.
The correct approach is to prioritise by cost of delay, not by age, not by urgency and not by the volume of customer contacts associated with each item. Cost of delay asks a specific question: what is the cost of leaving this item unresolved for one more day? The answer to that question determines the sequence in which items should be resolved.
Some items have a high cost of delay. They are generating downstream consequences, duplicate contacts, escalations, financial impacts, compliance risks, that compound with every day they remain unresolved. These items should be addressed first regardless of when they arrived.
Some items have a low cost of delay. They are self-contained, their consequences are limited and resolving them tomorrow costs no more than resolving them today. These items can wait.
Within the high cost of delay category, the fastest items should be resolved before the slowest ones because clearing fast items quickly reduces the visible size of the backlog, frees capacity for the slower items and demonstrates momentum to the team and to stakeholders who are monitoring the recovery.
Duplicate items, the same case opened multiple times by the same customer should be identified and consolidated before processing begins. Working through duplicates sequentially without consolidating them wastes capacity and risks resolving the same case twice.
Key Takeaway:
Unresolved exceptions do not disappear, they accumulate and delay recovery. Prioritising the backlog by cost of delay rather than age or urgency produces faster recovery and lower total cost than any other approach.
"Every unresolved exception becomes tomorrow’s problem."
MarvinPro_|_March_2026
marvinpro.com
Stabilisation is the sustained period of consistent, controlled operation that follows recovery. It is not a single event — it is a state that the organisation reaches gradually as exception rates decrease, process adherence increases and the team's confidence in the restored processes grows.
Achieving stabilisation requires active management across four dimensions.
The standard process flows must be reinstated explicitly and completely. This means reviewing every adaptation made during the crisis and making a documented decision about each one. Adaptations that represent genuine process improvements should be formalised — documented, approved and incorporated into the standard process. Adaptations that were appropriate only for crisis conditions should be reversed, the workaround removed, the informal approval path closed, the shadow process eliminated.
Controls and validations must be reapplied. During the crisis some controls were bypassed because the team had no capacity to apply them. Others were relaxed deliberately to increase processing speed. As stabilisation progresses these controls must be restored sequentially, with monitoring to confirm that restoring them does not create new bottlenecks.
Teams must be aligned on consistent ways of working. The crisis period produced variation, different people handling the same scenario in different ways, because the documented process was not being followed and there was no time to enforce consistency. As stabilisation progresses that variation must be reduced, through process refreshes, team calibration and visible monitoring of process adherence.
Deviations must be monitored closely. Stabilisation is not achieved and then maintained automatically. The restored processes must be actively monitored for signs of regression of teams reverting to crisis-period habits, of new exceptions emerging at rates that suggest the process has not been fully restored. The monitoring must be more intensive during the stabilisation period than in steady state and must remain intensive until the data confirms that the process is stable.
Key Takeaway:
A process is stabilised when it produces consistent results under controlled conditions not when the crisis is declared over. Stabilisation requires active management, explicit reinstatement of standard flows and intensive monitoring until the data confirms stability.
"Stability is not the absence of problems—it is the control of them."
MarvinPro_|_March_2026
marvinpro.com
In the same organisation where the queue of thousands had accumulated, clearing the backlog was only part of the challenge. The harder problem was ensuring it did not return.
During the crisis period the team had operated reactively. Decisions were made case by case. Workarounds had been created to handle scenarios the standard process could not absorb at speed. Some of those workarounds had been in place long enough to feel like the process.
Recovery required two things simultaneously, continuing to reduce the remaining backlog while rebuilding the process that would prevent it from returning.
The first step was visibility. Every workaround was identified and assessed. Some were valid temporary adaptations that needed to be formalised. Others were shortcuts that had introduced inconsistency and needed to be removed. The distinction mattered, not all workarounds are wrong, but all workarounds need a decision.
The second step was prioritisation by cost of delay rather than urgency. Urgency is felt. Cost of delay is calculated. A case that feels urgent may have low actual impact. A case that feels routine may be generating duplicate contacts, customer escalations and downstream complexity every day it remains unresolved. Resolving by cost of delay meant the cases with the highest ongoing impact were addressed first regardless of how loudly they presented.
The third step was stabilisation of the intake process. Recovery fails when the inflow continues to exceed capacity. The same methodology used to clear the backlog, matching case type to agent capability, removing duplicates at intake, handling quick decisions immediately was embedded as the standard operating model rather than the emergency response.
Within weeks of the backlog clearing the queue remained stable. The recovery had not just resolved the crisis. It had redesigned the process that caused it.
"Recovery is not complete when the backlog is cleared. It is complete when the process that created it no longer exists."
MarvinPro_|_March_2026
marvinpro.com
Chapter Outcome:
Recovery restores control. Stabilisation restores consistency. Without both, operations continue but the process remains broken.
The shift from reaction to structure, the systematic resolution of the exception backlog, the reinstatement of controls and the intensive monitoring of the stabilisation period, these are not optional activities that follow a crisis. They are the crisis response. They are what separates the organisation that emerges from a crisis stronger than it entered from the organisation that emerges weaker.
Every crisis is an opportunity. Not in the motivational sense, in the operational sense. The crisis exposed weaknesses that normal conditions were hiding. The recovery and stabilisation process is the mechanism for addressing those weaknesses permanently rather than temporarily.
The organisation that recovers well does not just return to where it was. It advances to where it should have been.
"Recovery is not the return to what existed before. It is the first opportunity to build something better than what broke."
MarvinPro_|_March_2026
marvinpro.com