Playbook
Turning a Business Round
Diagnosis before initiatives. Find out whether each sale makes money, where the losses build up and what is throttling output, then point the whole organisation at the few fixes that matter. A week of honest arithmetic saves a year of energetic guesswork.
I have sat in the meetings where a struggling business tries to fix everything at once, and I have chaired a few of them, which is worse. When the numbers go wrong, the temptation is to launch ten initiatives and hope one of them is the right one. That is how tired people turn a bad year into a bad two years. A turnaround needs the opposite discipline: find out precisely where the money leaks, then concentrate everything on the few places that matter. This sequence works from the inside out. Unit economics tells you whether the business loses money every time it sells something, a question surprisingly few troubled businesses can answer. Pareto analysis then shows where the losses build up, because they are never spread evenly. Theory of Constraints finds the single point that is throttling the whole system's output. Hoshin Kanri turns what you have learned into three or four breakthrough objectives the entire organisation actually pursues, instead of a recovery plan that lives in a drawer. Diagnosis first, then focus, then deployment. In my experience the diagnosis is the part people rush, because it delays the comforting feeling of doing something. Resist that. A week of honest arithmetic saves a year of energetic guesswork.
Finance
Unit Economics
For checking whether each sale and each customer actually makes money, before you scale and multiply the loss. Leave it alone when you have too little history to know how long customers stay; three months of data is a guess with a decimal point. Instead Break-even Analysis and Cash Flow Forecasting until you have a year of customers; lifetime value needs a lifetime.
Start with the arithmetic nobody wants to do. Trace one sale, one customer, all the way through: what it earns, what it truly costs, what it contributes. If the unit loses money, everything downstream is decoration, because scale will only multiply the loss. I have seen businesses celebrate top-line growth while every order quietly took cash out of the till. Contribution per unit, cost to acquire a customer, value a customer returns. Three numbers, honestly calculated, and the shape of the turnaround starts to appear.
Watch forDistrust blended averages; a healthy overall ratio can hide one channel or one product doing all the damage.
Operations & process
Pareto Analysis
For finding the few causes behind most of the trouble, by ranking the losses and seeing where the weight sits. Leave it alone when the causes are all about the same size; forcing a vital few onto a flat spread invents a priority. Instead A Fishbone Diagram; when the causes are all the same size, look at how they connect rather than which is biggest.
Once you know the business bleeds, find out where it bleeds most. Losses, defects, complaints, unprofitable customers: they concentrate, usually far more than anyone expects. Rank the causes by cost, cumulate the percentages, and look at the curve. A steep curve is good news in disguise, because it means a handful of causes carry most of the pain, and a stretched team can concentrate on those few. In a turnaround, focus is the scarcest resource you have.
Watch forCheck whether you have ranked by count or by cost, because the thing that happens most often is frequently a minor line in the losses.
Operations & process
Theory of Constraints
For finding the one bottleneck that sets how much the whole system can do, and pointing everything at it. Leave it alone when there is no stable bottleneck, because demand is low everywhere or the constraint moves week to week. Instead Value Stream Mapping, to level the flow when there is no stable bottleneck to elevate.
Now find the bottleneck. Every system has one point that sets its total output, and in a struggling business it is usually announcing itself: work piling up in front of one stage while other stages sit idle. An hour recovered at the constraint lifts the whole business. An hour saved anywhere else is, as Goldratt put it, a mirage. This matters here because your improvement budget is tiny and your time is short, so every pound and every hour must go where the whole system feels it.
Watch forBeware managers defending local efficiency; a well-run constrained system deliberately leaves some resources idle, and that will feel wrong to people trained to keep everyone busy.
Org, people & execution
Hoshin Kanri
For turning a few breakthrough objectives into aligned targets at every level, negotiated up and down rather than handed down. Leave it alone when the direction is undecided; this deploys a strategy, it does not produce one. Instead Playing to Win, to decide the direction; hoshin only deploys one you already have.
Diagnosis without deployment is a report. By this point you know what each unit earns, where the losses concentrate and what constrains throughput. Hoshin Kanri turns that into three to five breakthrough objectives with named owners at every level, negotiated downwards through catchball so the people delivering the numbers have actually agreed they are possible. The saying no matters more than the choosing. A turnaround dies of too many priorities faster than it dies of any single problem.
Watch forIf no target moved during catchball, nobody negotiated; you have compliance, and compliance quietly delivers nothing.
In the end
You should finish with a per-unit picture of where money is made and lost, a ranked view of where the pain concentrates, a named constraint with a plan built round it, and a deployment system that keeps the whole organisation pointed at the few things that matter. The caveat is blunt. Frameworks cannot rescue a business whose leaders will not face the numbers, and if the unit economics say the model is broken, no amount of focus fixes the wrong model. Do the arithmetic first, and believe what it tells you.