Business Turnaround & Rebuilding | Repair the Operation Before Scaling

“The business needs a turnaround” describes concern. It does not yet identify something that a person can examine on Tuesday morning. An operation is more concrete: receive a request, prepare an agreed item, check it, and make it available to the intended recipient. Its boundaries let you ask where the promise stops matching the result.

Start with one sentence: “We help this recipient obtain this result under these conditions.” A community materials room might help activity organisers obtain the correct reusable supplies by an agreed collection time. A printing service might produce an approved version in an agreed quantity. A booking desk might give a visitor a confirmed place and clear arrival information. These are different operations, even when all three are described as customer service.

Keep the recipient visible. A neatly arranged store cupboard can support the materials room, but arrangement is not the final service. The organiser needs a usable pack. Equally, an attractive confirmation message is not enough if the booking has never entered the actual schedule. Useful internal work earns its place by contributing to the agreed result.

Name where your examination begins and ends. You might begin when a complete request is accepted and end when the checked pack is ready for collection. That excludes earlier enquiries and later transport. The exclusion is a boundary for this inquiry, not a claim that those activities do not matter. If complaints concern transport, you will need a different boundary.

State what would count as restoration. “More organised” is difficult to check. “The collection coordinator can locate the correct checked pack and its current status” gives a clearer test. Avoid making the target so narrow that it rewards an unusable result: ready must mean more than placed on a shelf.

Finally, distinguish restoration from redesign. If the same useful service has become unreliable, repair may be appropriate. If recipients now require something materially different, restoring the old arrangement may leave the central problem intact. You do not have to decide immediately. You need to make the uncertainty explicit before choosing a route.

Contents · Next chapter

A useful starting record contains the commitment, the observed result, the conditions and the unanswered question. It should be small enough to understand without a presentation. Begin with a few identifiable requests or pieces of work that can be followed through the operation. Totals are useful later; individual examples help establish what the totals mean.

For a delayed supply pack, the record might show that the complete request arrived on Monday, collection was agreed for Friday, the pack was assembled on Thursday, and the collection list still showed “in preparation” on Friday morning. “The packing team is too slow” would be an explanation. The timestamps alone do not establish it. They point towards a question about what happened after assembly.

Use ordinary evidence available within the work: the agreed request, the item produced, the status record, and an account from the people handling it. Where accounts conflict, preserve both until the discrepancy is understood. Replacing an uncertain account with the most confident speaker’s version makes the record tidier while making the decision weaker.

Do not turn a short observation into a permanent label. A queue seen after an equipment interruption may differ from the queue on an ordinary day. A surge of complex requests may make this week unlike last week. A missing entry may mean work was not done, or that the recording step failed. These possibilities require different follow-up questions.

NIST’s Baldrige guidance connects organisational performance with customer judgments, a whole-system perspective and decisions grounded in measured evidence. Read NIST’s core values and concepts.

For the practical exercise here, write an evidence sentence and an explanation sentence separately. “Two checked packs were absent from the collection list” is evidence if you inspected both the packs and the list. “The handoff rule was unclear” is a possible explanation until you examine the rule and ask how it was used.

Choose the next observation for its ability to separate explanations. Looking at another shelf may add little. Following one completed pack from its check to its collection entry may reveal the missing decision. The aim is not to gather everything; it is to obtain enough relevant evidence to choose responsibly.

Contents · Previous chapter · Next chapter

An operation in difficulty usually contains some work worth keeping. Correct requests may already be recorded. A checking practice may reliably catch mismatches. Someone may know how unusual orders should be handled. Protecting those strengths is part of recovery because an indiscriminate reset can remove the very capabilities needed for repair.

Make a short preservation note alongside the problem statement. Name the useful result and the condition that supports it. “Keep the independent quantity check because it catches missing items before collection” is more informative than “keep quality high.” The first statement identifies something that a proposed change could accidentally remove.

Separate the work already promised from the future method under discussion. A team may need to locate today’s missing pack while deciding how tomorrow’s status updates should work. Resolving the immediate request does not prove that the recurring problem has been fixed. Conversely, debating a better future process does not answer today’s recipient who needs an accurate update.

Temporary stabilisation should have a visible limit. For example, one agreed person might reconcile the current collection list with the completed packs for that afternoon. Record which requests were checked and when the arrangement ends. Otherwise a temporary rescue can quietly become a permanent dependence on one person’s memory and extra effort.

Do not promise a result that the current record cannot support. If an item has not been checked, say that its readiness is unconfirmed. If a request is missing a required detail, identify the detail and who can confirm it. Honest status information allows the next person to act; optimistic guesses send uncertainty further through the operation.

Protection also applies to the people doing useful work. Ask how the work currently succeeds before asking why it sometimes fails. An unofficial note may be compensating for a gap in the formal record. Removing the note without supplying the missing function would make the system appear simpler while making the work harder.

For the wider principle, use Defence: protect what still works. In an operational recovery decision, the practical question is specific: which useful capability must still be present after the proposed change, and how will you notice if it disappears?

Contents · Previous chapter · Next chapter

The same complaint can arise from different causes. “My order was late” may mean that preparation took too long, that a detail remained unresolved, or that completed work was never released. The complaint matters, but it does not choose the diagnosis. Use the five families below to organise the next question.

These are routes into an investigation, not mutually exclusive explanations of an entire organisation. A vague requirement can produce rework, which can lengthen queues, which can complicate a handoff. Follow one request carefully enough to identify the relationships. Calling every symptom a separate problem can lead to several competing fixes for one underlying difficulty.

Choose the first route by consequence, evidence and what it enables. A small ambiguity may block an otherwise complete request. A much larger pile may contain work that is deliberately waiting for next week’s collection. Counting visible items alone cannot decide priority. Nor should the loudest complaint automatically define the entire operation’s purpose.

A good first route has a manageable boundary and a meaningful decision at its end. “Understand why two checked packs were not released” can lead to a specific handoff repair. “Improve everything about communication” cannot tell you when the inquiry has produced enough understanding.

Sometimes the best first move is confirmation rather than change. If nobody can establish the agreed quantity, changing preparation speed is premature. Confirming the request creates a usable starting point for later diagnosis. The Strategy guide develops this distinction between investigating a difficulty and acting on an adequately supported explanation.

Contents · Previous chapter · Next chapter

Before asking whether an operation is efficient, establish what it is meant to deliver. A pack with the right number of items but the wrong item type is not an acceptable substitute unless that substitution has been agreed. A quick reply that leaves the recipient unable to proceed is not necessarily a completed service.

Write the acceptance condition in language a person can apply to actual work. For an activity pack, it might include the requested contents, quantity, identifying label and agreed readiness time. Keep necessary distinctions visible. “Ready for collection” and “collected by the recipient” describe different events; one should not be silently counted as the other.

Check the condition against an ordinary example and an awkward example. If a request specifies twelve blue folders, does a pack of twelve assorted folders pass? If a recipient agrees to accept assorted colours, where is that change recorded? The point is not to invent bureaucracy. It is to prevent two reasonable people from applying different versions of the promise.

Separate a missing requirement from a defect against a clear requirement. When colour was never agreed, you have an uncertainty to resolve. When blue was agreed and red was supplied, you have a mismatch to repair. Both can disappoint the recipient, but the improvement question differs. The first concerns how the request becomes complete; the second concerns how agreed information reaches production and checking.

Avoid expanding the requirement after seeing the result. A team should not declare a failed pack acceptable merely because the correct materials are inconvenient to obtain. Equally, a reviewer should not invent extra criteria that were never part of the task. Where the requirement genuinely changes, record the revised agreement and distinguish it from the original commitment.

Use complaints as starting evidence rather than complete specifications. “The pack was confusing” needs examination: was the label unclear, were the contents mixed, or were the instructions missing? A concrete example can turn the complaint into a repairable difference without dismissing the recipient’s experience.

A useful requirement enables the next person to make a decision. If the phrase “good quality” still requires an explanation every time, it has not finished its work. Show what an acceptable result looks like, name the important exceptions, and identify who can resolve an unanswered question before the work proceeds.

Contents · Previous chapter · Next chapter

Work can appear delayed even when the physical task has finished. An assembled pack may be waiting for its check. A checked pack may be waiting for a label. A correctly labelled pack may be absent from the collection list. These states have different owners and different next actions, so “not ready” is often too broad for diagnosis.

Trace a single request through the boundary you defined. At each point, ask what exists, what remains to be done, and what the next person needs. A handoff may transfer an object, information, permission to proceed, or confirmation that a condition has been met. Putting an object in the next room may transfer the object while failing to transfer its status.

For example, a preparer says, “I left it on the finished shelf.” The coordinator says, “I was waiting for the checked label.” Neither account proves carelessness. The problem may be that finished meant assembled to one person and checked to the other. The missing distinction should be examined before a new reminder is added.

If unfinished work genuinely accumulates, define the observation period and the unit of work before comparing stages. Ten small packs and ten complex custom packs are not automatically comparable workloads. Nor does the largest queue, seen once, establish which step limits the operation. Requests may arrive in batches or wait deliberately for a scheduled action.

Use How to Diagnose a Process Bottleneck when the main uncertainty concerns arrivals, work time, waiting, available resources and acceptable completions. That guide develops the numerical investigation. Here, the routing decision is whether you need that investigation at all, or whether the available evidence points first to a missing requirement or handoff.

Be careful when proposing more speed. A faster preparation stage can send more unchecked work towards a checking stage that is already behind. An extra reminder can generate more messages without clarifying the current status. Before acting, describe how the proposed move would help the recipient obtain an acceptable result across the whole boundary.

A useful handoff makes three things legible: what is being passed, what condition it is in, and what the recipient of the handoff should do next. Start with the smallest arrangement that supplies those facts in the actual work, rather than assuming a new tool is required.

Contents · Previous chapter · Next chapter

An operation can faithfully produce something that fewer people now need. It can also receive new requests that the old method handles poorly. These are different from a temporary delay in otherwise suitable work. Rebuilding the previous arrangement without examining current requirements may restore reliability around the wrong result.

Look for a specific change in the requests, not a vague feeling that the environment is different. A resource room once supplied identical packs for whole-group activities. Recent organisers may instead request smaller mixed packs for drop-in sessions. The relevant difference concerns quantities, combinations and collection arrangements. It does not mean that the room’s knowledge of materials has become worthless.

Distinguish enquiry, accepted request, completed work and recipient feedback. Several enquiries about a new format do not prove that the format will become regular demand. A quiet week does not prove that an existing service is no longer useful. Record which event you observed and what further evidence would clarify the pattern.

Ask what can be preserved. The reliable checking practice, clear item descriptions and knowledge of reusable supplies may remain valuable even if the pack format changes. Adaptation can retain those functions while changing how the work is grouped. The preservation question prevents “new demand” from becoming an excuse to discard useful capability.

Keep the first exploration within an agreed, ordinary task. You might compare an existing pack description with a confirmed new request and identify the mismatch. That comparison can establish what must change before you decide how to change it. It does not require a prediction about an entire market or a claim about commercial success.

The Metamorphose guide explains how to examine a changed demand while retaining useful strengths. Its examples concern learning; the question travels here with a different object: what does this operation now need to accomplish that its previous method did not provide?

If the current offer still meets the agreed requirement and the problem is unreliable execution, return to the other routes. Adaptation is a response to a demonstrated mismatch. It should not be used to avoid investigating an ordinary error in a process that remains fundamentally suitable.

Contents · Previous chapter · Next chapter

The fictional Kestrel Materials Room lends reusable activity supplies to community organisers. Maya coordinates requests and Leo prepares packs. Their ordinary arrangement allows them to inspect current requests, correct their own records and discuss collection details with the organisers. This example concerns those routine activities only.

Twelve accepted requests, K01 to K12, are due to be ready by Friday at 3 p.m. Each request is for one pack. The acceptance condition is the agreed contents and quantity, the correct request label, a completed contents check, and an entry on the collection list. Readiness does not mean that the organiser has already collected the pack.

At Friday noon, a casual count describes seven packs as “prepared.” Maya and Leo inspect the twelve request records together. They classify each request once, by its current main unresolved state. Other background difficulties may exist, but no request is counted twice in this snapshot.

The five actual status categories contain 6 + 1 + 2 + 2 + 1 = 12 requests. Six meet the readiness condition, so the noon snapshot is 6 out of 12, or 50%. The seven “prepared” packs were the six ready packs plus K06. That informal total included a pack which could not yet satisfy its request.

The snapshot does not measure the room’s weekly capacity. It says nothing about requests due next week, the time required by each pack, or whether noon is normally a quiet or busy point. It also does not establish the eventual Friday result. It answers a narrower question: what is known about these twelve commitments now?

Maya initially suggests asking Leo to prepare everything faster. The record shows why that response is incomplete. Some work lacks an agreed requirement, some lacks a usable handoff, and one request lacks the agreed material. More assembly effort alone cannot supply those missing conditions.

Contents · Previous chapter · Next chapter

Maya and Leo first protect the six conforming packs. They keep those packs identifiable and preserve their checked records. K06 remains clearly separate from ready work while the folder-size mismatch is corrected. They seek confirmation for K05 and K11 and establish the actual options for K09 with its organiser. These are actions on existing commitments, not evidence that a new system works.

For the first recurring process question, they choose the K03 and K08 handoffs. The choice is not based on those requests being the largest category. It is based on an observable gap they can examine within their ordinary work: physical packs exist, but their completion information is missing from the collection record.

They follow both packs. The contents and quantity had been checked against the agreed requests. Leo placed the completed check slips inside the packs, expecting Maya to find them during collection preparation. Maya expected the slips beside the collection list. Both packs waited while each person believed the other still had an action to perform.

This finding supports a specific explanation for these two requests: the place used to pass checking information did not match the coordinator’s expectation. It does not establish that every delay has the same cause. It also does not excuse the separate requirement, material and folder-size difficulties. Those remain visible in the request record.

After inspecting the slips, reconfirming their match to the packs and completing the missing collection entries, Maya can classify K03 and K08 as ready. If nothing else changes in the illustration, the readiness count becomes 8 out of 12. Four requests remain unresolved: K05, K06, K09 and K11. The team has released two particular requests; it has not demonstrated a lasting improvement rate.

For future comparable packs, Maya and Leo now have a precise question: can an agreed visible location for the checked status make the handoff usable without weakening the contents check? That is narrower than “improve communication.” It preserves the function that caught K06 and addresses the information gap observed in K03 and K08.

They can take that question to How to Test a Small Operational Change Before Scaling It. The companion guide develops the trial, measures and interpretation. The achievement here is choosing a warranted next question from an untidy situation, while keeping the other unresolved commitments honest.

Contents · Previous chapter · Next chapter

A rescue depends on someone noticing the problem and making an extra effort. A rebuilt arrangement makes the necessary decision available during ordinary work. In the materials room, the useful decision is whether a specific pack has met the readiness condition and can be placed on the collection list. That decision needs information, an agreed place and a recognisable next action.

Describe the arrangement from the next person’s perspective. When Maya begins collection preparation, what can she see? Can she connect the status to the correct request? Does “checked” still mean that the agreed contents and quantity were inspected? What should she do if the signal is absent or inconsistent? A label has value only if the people using it share these meanings.

Keep exceptions usable. An ordinary pack may move through a simple sequence, while a pack awaiting an organiser’s confirmation needs a different state. If the record offers only “done” and “not done,” people may squeeze uncertainty into whichever category seems least inconvenient. A small, meaningful distinction can prevent the wrong next action.

The arrangement also needs a restart point after interruption. Suppose preparation stops before the quantity check. The next person should be able to identify the remaining action without treating a half-completed note as confirmation. This is a design question about the work record, not a demand that people remember more carefully.

Avoid adding a second record without deciding which record governs the current state. Two lists can begin consistently and then diverge. If both are necessary for different purposes, specify how the shared information is maintained. If one serves no separate decision, its upkeep may be an avoidable burden. Simplicity should be judged by usable work, not by the apparent neatness of a diagram.

The Rebuild guide explores how a chosen improvement becomes workable across ordinary interruptions and changing weeks. For this operational application, write the smallest complete arrangement: the starting signal, the action, the evidence of completion, the next handoff and the response to a missing condition.

You will still need to observe how it behaves. A clear description is a proposed arrangement. Repeated use under relevant conditions provides the evidence for deciding whether it deserves to become the ordinary way of working.

Contents · Previous chapter · Next chapter

An improvement at one step can move difficulty elsewhere. Suppose the materials room reduces the time spent writing item descriptions by using shorter labels. The preparation record may become quicker to complete, while the coordinator spends longer asking what the abbreviations mean. The local saving would not establish a better operation.

Follow the change through to the recipient’s result. What becomes easier? What becomes harder? What information is lost, delayed or duplicated? A change that makes a status visible may help collection while adding a recording task to preparation. That extra task might be worthwhile, but it should be acknowledged rather than hidden behind a pleasing headline.

Do not treat a faster total as a complete definition of success. A smaller completion time paired with more wrong packs may fail the purpose. A higher number of ready packs paired with unclear collection information may shift the problem to the organiser. Choose measures that preserve the agreed meaning of an acceptable result.

Keep conditions with the observation. If a later session has fewer requests, simpler packs or an additional helper, its result cannot be casually compared with an earlier difficult session. Those differences may be relevant explanations. They do not make the later result worthless; they limit what it establishes about the change.

EPA’s kaizen guide starts with a defined process, studies present conditions, tests ideas and follows up using measures. Read EPA’s guide to kaizen.

Here, use a short consequence question before adopting an attractive idea: “If this step becomes easier, what must remain true for the next person and the recipient?” For the materials room, checked must still mean checked, the request reference must remain correct, and a pack must still be locatable. Those conditions give the team something concrete to protect while learning from a proposed change.

This is also where the boundary of operational education matters. Even a well-observed improvement in pack readiness does not establish profitability, financial stability or a complete organisational turnaround. Report the operational result at the level the evidence supports. Wider questions require their own evidence and decisions.

Contents · Previous chapter · Next chapter

A useful decision note should let another person understand the present choice without reconstructing a long discussion. It is not a catalogue of every possible improvement. It records the operation, the specific difficulty, the evidence, what must be preserved and the question being taken forward.

For the materials room, the note could read: “We are examining the handoff between completed pack checks and the collection record for ordinary reusable-supply requests. K03 and K08 had matching check slips inside their packs, while the coordinator expected those slips beside the list. We will preserve the contents check and examine a visible, agreed handoff location.”

Add what the note does not settle. The two requests awaiting item confirmation and the request missing material require separate follow-up. Keeping those unresolved states visible prevents a handoff repair from becoming an explanation for everything. It also helps the next reader avoid reopening a settled question while overlooking a live one.

Name the person or role able to take the next ordinary action, but do not assign responsibilities that have not been agreed. “The coordinator will confirm the collection record with the preparer” is useful only if those roles have that arrangement. A plan written outside someone’s authority should be brought to the relevant discussion before it is treated as an instruction.

Record the next decision rather than an indefinite aspiration. You might need to decide whether the handoff idea is ready for a small trial, whether more observation is needed, or whether the problem belongs to another route. “Continue improving communication” leaves the work open forever. “Check whether the proposed status location supplies the missing information” gives the inquiry an end point.

Finally, specify what would make you revise the explanation. If further packs carry clear status information yet still wait, the location of the slip may not explain those delays. If the supposed requirement was never agreed, the inquiry needs to move earlier. A good note allows correction because it separates the current interpretation from the evidence beneath it.

The result should be brief enough to use at the work itself. Longer analysis can support the decision, but the person handling the next request needs a clear action, a relevant condition and somewhere to take an unresolved question.

Contents · Previous chapter · Next chapter

Try a different situation before reading the answer. The fictional Alder Exhibition Desk prepares information cards for a neighbourhood display. Each accepted request concerns one card. The desk’s agreed result is a card with the approved wording and language, the correct display location, and a matching entry on the placement list by the agreed time.

Nine accepted cards, A1 to A9, are due at noon on Saturday. The following snapshot is taken at 10 a.m. Each card appears in exactly one row. These facts are supplied for the exercise; they are not a real service record.

The desk’s earlier display used English-only cards. The current request form includes a language field, and both A5 and A6 correctly show the bilingual requirement. The preparation sheet copied from the earlier display contains the wording and size but omits the language field. The final check compares the print with that preparation sheet.

One colleague proposes a faster printer. Another proposes more reminders to check the cards. A third says that the whole display concept should be replaced because demand has changed. You can inspect the records, discuss the ordinary preparation process and propose a small change through the desk’s agreed arrangements. No equipment purchase or wider redesign decision is part of the task.

Write a short answer to five questions. How many cards currently meet the full acceptance condition? What useful work should be protected? Which route deserves the first recurring-process inquiry? What evidence makes that route more suitable than the competing explanations? What remains unresolved after choosing it?

Then add one sentence describing a proposed next question, without claiming that the eventual improvement has already been demonstrated. You are choosing a justified direction from the record. You are not being asked to design the complete trial or calculate a capacity limit.

Contents · Previous chapter · Next chapter

Four cards currently meet the full acceptance condition: A1, A2, A3 and A4. The remaining groups contain 2 + 1 + 1 + 1 = 5 cards, so all nine are accounted for. A7 is physically correct but fails the placement-list condition. A5 and A6 fail the agreed language requirement. Printed therefore cannot be treated as a synonym for ready.

Protect the four conforming cards and their matching placement records. Also preserve the accurate request form: it successfully captured the bilingual requirement for A5 and A6. The final check has a useful intended function, but its reference document is incomplete. Preserving the function does not require preserving the defective preparation sheet exactly as it stands.

The first recurring-process inquiry should follow the requirement from the accepted request into preparation and checking. The source requests contain the necessary language information. The preparation sheet omits it. The final check uses that sheet, so following the checking instruction carefully can still miss the agreed requirement. That is a more specific explanation than “people need to check harder.”

A faster printer does not supply the missing language field. More reminders to use the same incomplete checking reference do not repair its content. Changed demand is part of the context because the old display was English-only, but the immediate mismatch is already identifiable: the current request is bilingual and the preparation information does not carry that requirement forward.

A suitable next question is: “Would carrying the agreed language requirement into the preparation and checking information allow the desk to verify the requested card without losing the correct wording, size and location?” That question is ready to be developed into a bounded trial through the small operational change guide. It is not a claim that adding a field has already solved the problem.

Several commitments remain unresolved. A5 and A6 still need correction. A7 needs its placement information reconciled. A8 needs confirmed wording. A9 needs a truthful discussion of the unavailable material and any agreed alternative. Choosing one recurring inquiry does not erase these practical responsibilities or convert their uncertain status into completion.

An alternative answer can be reasonable if it explicitly separates urgent action from recurring diagnosis. You might reconcile A7 immediately because its physical result is already correct. That would help a particular commitment. The supplied record nevertheless gives the strongest explanation for the repeated A5 and A6 mismatch at the requirement-transfer step, rather than at printing speed or the entire display concept.

Contents · Previous chapter · Next chapter

Operational recovery becomes manageable when the next question has an object: a request, a waiting pack, a missing field, a check or a handoff. You can inspect that object, compare it with the agreed result and decide what evidence would justify a change. The larger ambition matters, but useful rebuilding depends on those smaller decisions remaining connected to the recipient’s purpose.

If the requirement is unclear, confirm it before optimising the process around it. If the requirement is clear but work accumulates, use How to Diagnose a Process Bottleneck to examine the flow and its limits. If you have an adequately supported explanation and a reversible idea, use How to Test a Small Operational Change Before Scaling It to plan what you will observe and how you will decide what follows.

When the old method no longer fits a demonstrated new requirement, return to the adaptation question. When a useful change has been examined and needs to survive ordinary interruptions, return to rebuilding. These moves can occur in different orders. There is no benefit in forcing every situation through seven compulsory stages when its evidence points to a more direct next action.

Keep a record of the useful value being protected, the current uncertainty and the decision actually made. Update the record when the facts change. A request resolved today may reveal a recurring question for tomorrow; a promising idea may need revision after it reaches another part of the operation.

For the broader framework, return to Recovery and Transformation. The immediate task is now concrete: choose one ordinary operation, describe its agreed result, inspect a small set of real work, and take the next question to the route that can answer it.

Contents · Previous chapter · Return to recovery and transformation