How to keep a turnaround from slipping back into crisis

Keep a turnaround from slipping back by turning the recovery’s useful decisions into ordinary operating routines. Define what teams review, which exceptions trigger action, and who owns the response. Retire temporary crisis practices when their conditions no longer apply, while preserving the information needed to detect recurring failures.

Organizational routines are recurring patterns of interdependent work through which an organization performs tasks. This working definition follows the discussion of task sequences and knowledge embedded in routines in Argote and Ingram’s 2000 framework. Here, a sustaining routine means a repeatable operating arrangement, not a guarantee against another crisis.

A routine differs from a recurring meeting. The meeting may be one part of the routine, but the routine also needs usable information, decision ownership, and follow-through. A calendar invitation alone does not establish that any operating problem will be addressed.

Identify what changed during recovery

Start with the failures the recovery was meant to resolve. Choose a concrete example of each relevant failure and identify the changed behavior or operating arrangement. Avoid treating improved results as a complete explanation of what produced them.

Ask which changes are still required for normal service. Which depend on personal intervention by the CEO? Which exist only because a small group keeps reminding everyone? Record those dependencies before the recovery team disperses.

The returning founder’s turnaround playbook supplies the wider recovery mandate. Use that mandate to identify the operating conditions worth preserving. Do not attempt to preserve every activity performed during the turnaround.

A temporary daily escalation call may have served an urgent need. The long-term requirement may be a reliable exception route, rather than that exact call at that exact frequency. Separate the function from the crisis-era form.

Distinguish a result from the routine supporting it

A favorable report tells you something about reported results. To understand the operating routine, examine the decisions and handoffs that produced the work. Check definitions and data sources before comparing periods.

For a delivery recovery, inspect whether promises are verified before they reach customers. For an approval bottleneck, inspect whether authorized owners make decisions within the agreed boundaries. Choose evidence tied to the original failure.

Do not assume the same threshold suits every function. Establish a review condition appropriate to the work and its consequences. An arbitrary standard borrowed from another company can create false reassurance or unnecessary escalation.

Ask what evidence would show the routine is breaking down before the later business result changes. Treat the answer as a hypothesis to inspect, rather than calling it a proven early-warning indicator.

Use the post-recovery routine review

The post-recovery routine review is a proposed advisory method. It is not a validated relapse-prevention intervention or a prediction that a company will avoid another crisis. Use it to make operating expectations reviewable.

1. Name the failure being prevented. Describe the specific work breakdown and its consequence. Keep the description separate from judgments about the people involved.
2. State the sustaining behavior. Identify the recurring decision, check, or handoff that addresses that failure. Assign an owner with appropriate authority.
3. Specify the evidence. Name the record that shows whether the behavior occurred. Identify who maintains it and how a disputed entry is corrected.
4. Define an exception trigger. State what requires attention outside the ordinary review. Include the response owner and the route if that person is unavailable.
5. Match review frequency to exposure. Choose a cadence based on the work’s dependencies and consequences. Record when the cadence will be reconsidered.
6. Remove duplicate crisis demands. Identify which emergency meetings and parallel reports can end. Preserve necessary obligations and assign the closure work.
7. Test and revise the routine. Walk through a plausible exception, inspect an actual operating cycle, and change what does not support a usable decision.

Keep the review record concise. Its purpose is to direct the next necessary action, not to create an additional reporting layer that competes with the work it monitors.

Put operating knowledge where the next team can use it

Argote and Ingram discuss knowledge embedded in people, tools, tasks, and their interactions. Their framework suggests looking beyond a procedure document when transferring recovery practices into ordinary work.

Ask the receiving team to perform the routine with the actual information available to them. Observe where they need interpretation from the recovery team. Determine whether the gap concerns missing context, an inaccessible record, or an unclear decision boundary.

If a procedure requires a personal message to the founder whenever an exception appears, the founder remains part of the operating design. Decide whether that involvement is justified. Do not label the process independent while leaving the dependency intact.

Train through relevant examples and preserve necessary context. Avoid collecting private stories about colleagues when work records will explain the decision. Involve appropriate counsel before changing monitoring practices or using operating data for employment decisions.

A composite scene: the crisis meeting never ends

Consider a hypothetical composite. The recovery report has improved, but you still cancel an evening at home for the daily crisis call. The call now repeats ordinary status updates. Employees maintain both the normal reporting system and a separate recovery spreadsheet because nobody has authority to retire either one.

When a real exception appears, it is discussed in both systems. Each meeting assumes the other has assigned the response. The company has preserved the burden of crisis mode without preserving a clear decision route.

The routine review identifies the original requirement: an exception must reach an authorized owner with enough information to act. The team places that requirement in the ordinary operating process and closes the duplicate spreadsheet after verifying the transfer.

The daily call ends under an explicit decision. A defined exception can still trigger a temporary additional review. Someone owns that decision and the condition for ending the extra review.

This constructed example does not establish that daily calls are inherently unhelpful. It shows why a crisis practice needs a current purpose and an exit condition, even when it once helped the recovery.

Review what receives leadership attention

A post-recovery agenda can continue rewarding crisis intervention after the underlying conditions have changed. Use Ocasio’s 1997 attention-based view to inspect which issues its rules and review arrangements keep bringing to leaders. This is an application of a theory about organizational attention. Ask what the agenda now excludes before deciding which emergency meetings to retain and which routine owners should receive their responsibilities.

Which operating exceptions have a defined place? Which improvements receive recognition? Which unresolved questions disappear because the meeting moves on? Check actual agendas and decisions before deciding the pattern.

A leader’s informal requests belong in this review. If the CEO repeatedly reopens a settled decision through private messages, the formal routine may no longer describe how the company operates. Record the exception and decide whether the routine or the behavior needs to change.

The culture behavior-reinforcement guide addresses how leadership choices communicate expectations. Here, inspect a narrower issue: whether ordinary management attention supports the behavior the recovery needs to preserve.

Make a recurrence useful information

A repeated failure deserves examination, but its recurrence does not establish one cause. The routine may have been poorly designed, the context may have changed, or a clear obligation may not have been met. Trace the work before choosing the explanation.

Ask which assumption the exception challenges. If the data source was unavailable, repair the information route. If the approved owner lacked authority, resolve the boundary. If someone made a contrary choice within a clear arrangement, address that behavior through the appropriate process.

Avoid restoring every crisis practice after one exception. Decide which temporary response is proportionate to the issue. State the condition for returning to the ordinary routine when you authorize the response.

Use the first-ninety-days review as a model for explicit checkpoints, while adapting the sequence to the company’s post-recovery mandate. A new phase should not be governed indefinitely by the calendar of the old one.

Check willingness and capability separately

Weiner’s 2009 theory of organizational readiness distinguishes shared commitment to a change from shared confidence in implementing it. It also explains why the proposed change matters when discussing readiness. General enthusiasm about recovery does not answer a question about a particular routine.

Ask the receiving team whether the routine serves a useful operating purpose and whether they can perform it with the available support. Compare those answers with observed work. Do not use a short discussion as a diagnostic scale.

The paper develops organizational-change theory using healthcare settings. Its concepts can structure an inquiry here, but they do not validate the specific sustaining routine you choose.

If employees understand the purpose but cannot maintain the records without duplicate entry, inspect the design. Calling for stronger commitment leaves the operating constraint unresolved.

Record who may change a review condition and how that change becomes visible to the people doing the work. Otherwise, an informal exception can become a new operating expectation without anyone reviewing its burden or consequences.

Define what outside support now contributes

An outside adviser may help inspect the transition into ordinary routines. Specify the question and the evidence the adviser should examine. Avoid retaining a permanent crisis role because nobody has reviewed what the role now does.

Use the outside-adviser selection guide to clarify that assignment. Keep decision authority with the appropriate company owners. Advice should help make the operating system usable, rather than become another hidden dependency.

Before closing the recovery phase, ask an owner who did not design the routine to explain the next exception route. Resolve any difference between the written process and the process they would use.

Set the next review against the ordinary mandate. Preserve the reason for each continuing routine and remove work that no longer serves it. A sustained recovery needs current operating discipline, with a way to detect and address failure without keeping the company permanently organized around emergency.

Test a sustaining routine with an exception that the crisis team once handled personally. Ask the ordinary owner to locate the information, make the permitted decision, and escalate the unresolved part. If the old crisis leader still has to intervene, identify the missing transfer. Keep that repair separate from a decision to retain every emergency meeting, because the unresolved dependency may need a narrower change to the operating arrangement.

Sources

• Argote and Ingram (2000): Knowledge transfer: A basis for competitive advantage in firms. Grounds the account of operating knowledge embedded in recurring work.

• Ocasio (1997): Towards an attention-based view of the firm. Frames the post-recovery agenda and its exception reviews.

• Weiner (2009): A theory of organizational readiness for change. Supplies a readiness lens for transferring crisis work into ordinary operations.