- The business in question
- Why the standard method does not start here
- The first move is building a case nobody asked for
- Where the evidence actually is
- The three gates you have to pass
- What to change first when nothing is broken
- The cost you should expect to pay
- What holds it in place afterward
- When not to do this
- Frequently asked questions
Zero. That is the number of people in the building who will thank you for starting this, and it is the single most important fact about turning around a business that is not failing. Every method in the turnaround literature assumes a burning platform, which is to say it assumes the hardest part of the job has already been done for you by circumstance.
It has not been. What follows is the version of the work that applies when the numbers are acceptable, nobody is alarmed, and you can see the decline coming anyway. It is a harder job than a crisis turnaround and considerably less well documented, which is odd, because far more businesses are in this state than in the other one.
The business in question
Hypothetical: the business described below is constructed to carry the argument. The figures are illustrative and are not drawn from any company.
What it looks like from outside
Revenue has been within a few points of flat for four years. Gross margin has drifted down about a point a year, which nobody has flagged because a point is inside the noise of any single quarter. Operating margin is positive. The bank is happy, the owners are happy, and the plant is busy every day of the week.
SKU count has grown every year. Nothing has been retired in a decade. The newest product anybody can name is six years old. Two of the top three customers have been reducing their share of wallet slowly, which never appeared as a lost order and therefore never triggered a review.
What that combination actually means
Read together rather than separately, those facts describe a business converting its accumulated position into current earnings. Every year it works harder to produce the same result, which is the operational definition of stagnation, and the reason nobody has noticed is that the P&L reports the result rather than the effort.
The thirteen behavioral signals that produce this condition are in the stagnation signals. This article is about what to do once you have counted them and concluded that you are right and nobody agrees.
The reason nobody has acted
Every individual fact in this business has a reasonable local explanation, and that is precisely what makes the condition durable. The margin point is mix. The SKU growth is customer responsiveness. The absent new product is a deliberate focus on the core. The customer softness is their inventory cycle. Each explanation is offered in good faith by somebody competent, and each one is defensible in isolation.
What nobody has done is put the four explanations side by side and ask whether a business can hold all of them simultaneously for four consecutive years and still be healthy. That question has no owner, because it does not belong to any function, and the absence of an owner is the mechanism rather than an accident of this particular company.
Why the standard method does not start here
The standard turnaround sequence starts with cash because cash buys calendar. In a business that is not failing you already have calendar, which removes the first stage entirely and, more importantly, removes the thing that made the rest of the sequence socially possible.
What the crisis was actually doing for you
A crisis performs three functions that nobody credits it with. It grants permission to act without a complete diagnosis. It suspends the normal objection that a proposed change might not work. And it aligns a leadership team around a single shared fact, which is that the current path ends badly on a specific date.
Remove all three and the same sequence stops working. You cannot act before diagnosis because nobody has agreed there is a problem. Every proposal is met with the entirely reasonable observation that things are currently fine. And your leadership team is aligned around a fact you disagree with.
What replaces it
Evidence replaces urgency, and the order of operations inverts. In a crisis you act, then measure, then explain. Here you measure, then explain, then act, and the explaining phase is longer than either of the others. That inversion is the single structural difference between the two jobs and almost everything else follows from it.
In a crisis you act, then measure, then explain. Without one you measure, then explain, then act, and the explaining phase is longer than either of the others.
Where the sequence still holds
Two things survive the inversion. The dependency order inside the operating work is unchanged: you still cannot recover margin from a line whose output you cannot measure, and you still cannot ask a management layer to execute while decisions take eleven days. And the twelve-month completion test is the same, because the mechanism you are installing is the same mechanism.
What changes is only the front end, and it changes completely. Treat the crisis playbook as correct from stage two onward and wrong at stage one, and you will save yourself the experience of proposing a well-designed intervention to a room that has not yet agreed there is anything to intervene in.
The first move is building a case nobody asked for
Your first sixty days are spent assembling an argument, not running a diagnostic, and the difference is in what you are optimizing for. A diagnostic is optimized to find the cause. A case is optimized to survive people who would prefer it were not true.
Direction, not level
Level is the enemy. Any statement about the current state invites the response that the current state is acceptable, and it is. Direction cannot be answered that way. Four years of gross margin by product family, four years of SKU count, four years of changeover hours as a share of constraint time, four years of customer concentration. Each of those is a slope, and a slope is an argument.
Take the longest history you can reconstruct rather than the cleanest. Six patchy years beats two immaculate ones, because the whole case rests on the shape of the line and two points do not have a shape.
Effort against result
The second half of the case is the one that lands. Show that the business is doing more work to produce the same output: more part numbers, more changeovers, more configurations, more quotes per win, more meetings per decision. Put it beside the flat revenue line.
That comparison converts an abstract worry into something an operator recognizes immediately, because the people in your building have been feeling exactly this for years without a number attached to it. Give them the number and a meaningful share of them become allies rather than obstacles.
Where the evidence actually is
Almost all of what you need already exists in systems nobody queries for this purpose, and none of it requires a project to obtain. The barrier is knowing what to ask for rather than whether it is available.
The four pulls
Revenue by product family by year, for as far back as the system goes. SKU or part number count by year, including the ones that are technically active with no volume. Changeover events on the constraint by year, which maintenance or scheduling usually has. And quote count against win count by year, which sales has and rarely looks at longitudinally.
Each of those is a single query. Together they produce four slopes, and four slopes pointing the same direction is a case that does not depend on anyone’s judgment, including yours.
What to skip
Skip the employee survey, skip the benchmarking exercise, and skip anything requiring an outside firm. All three are slow, all three produce findings that can be argued with, and commissioning one signals that you do not yet have a position of your own. In a business that is not failing, the perception that you are still looking is fatal to the argument.
The three gates you have to pass
Between having a case and being allowed to act there are three gates, and they have to be passed in order. Skipping one does not get you to the next faster, it gets you back to the first.
What each gate tests
The first gate is agreement that the slopes are real. Not agreement that they matter, just that the lines are what you say they are. This is a factual conversation and it is winnable if your four pulls are clean.
The second gate is agreement that the slopes continue. This is where the argument actually happens, because everyone in the room can construct a story in which the line flattens on its own. Your counter is mechanism: name the specific thing producing the slope and show that nobody is currently working on it.
The third gate is agreement about who pays. Every change you propose will cost some function something, and the gate does not open until that is explicit. An approval granted without this conversation is not an approval, it is a deferral of the argument to the first moment your change inconveniences somebody.
What to change first when nothing is broken
Choose the first change for what it demonstrates rather than for what it earns. In a crisis you pick the largest available number. Here you pick the thing that proves a mechanism exists, because the mechanism is what you are actually installing.
Retire something
The first change should be a retirement: one product, one report, one process, one recurring meeting. Retirements are the decisions a stagnating business structurally cannot make, because additions have champions and retirements have opponents and no champion. Making one, visibly, proves the capability exists.
Pick one that is genuinely defensible and genuinely inconvenient for somebody. A retirement that costs nobody anything demonstrates nothing, and the organization will read it accurately as theater.
Then the decision layer
Second change is thresholds and escalation timing, for the same reason it comes early in a crisis: everything downstream depends on it, and unlike most of what you will propose, it is almost impossible to argue against. Nobody in a healthy business wants to defend an eleven-day approval cycle out loud.
Additions have champions and retirements have opponents with no champion. Making one retirement, visibly, proves that the capability exists at all.
Then one visible number
The third change should be a number that goes up on a wall, updated by the people who produce it, chosen because it captures the effort-against-result comparison rather than the result alone. Changeover hours as a share of constraint time is usually the best candidate, because it is the number that makes the busy-and-flat condition legible to everyone who walks past it.
Do not add it to a dashboard. A dashboard is where numbers go to become somebody’s monthly obligation. One number, physically posted, in the area that moves it, is a different instrument entirely, and in a business with no crisis it does more argumentative work than any presentation you could give.
The cost you should expect to pay
This work has a price and it is paid in a currency that does not appear in any business case, which is your own standing. Knowing the size of the bill in advance is most of what determines whether you finish.
The first two quarters
You will be the person who arrived and decided things were wrong. That characterization is unfair, partly accurate, and completely unavoidable, and it will be applied by people who are neither hostile nor stupid. It fades when the first evidence lands and not before.
Expect at least one senior person to disagree publicly and one to disagree privately while agreeing publicly. The second is more of a problem than the first and it is worth identifying early.
What makes it survivable
Two things. Having your boss inside the case before you take it wider, which is worth more here than in any of the other situations because you are spending capital on a problem nobody asked you to solve. And a written, dated statement of what would change your assessment, which converts you from someone with a conviction into someone running a test.
Budget for the second bill as well, which arrives around month nine. By then the early evidence has landed, the argument is broadly won, and the work moves from proving to doing. That is the point at which people who accepted the diagnosis discover what accepting it costs their own function, and a portion of the goodwill you earned in month four gets spent again. Expect it, and do not read it as the case unravelling. It is the case being implemented.
What holds it in place afterward
The mechanism that keeps a non-failing business from re-stagnating is a standing retirement obligation, and it is the only piece of this that has to survive you.
The obligation
Every product portfolio review, every year, retires something. Not may retire, retires. The obligation is what makes the decision structurally possible, because it converts a retirement from an act somebody has to champion into a requirement somebody has to satisfy.
The same logic works on reports and recurring meetings. An annual obligation to remove one of each costs almost nothing and it prevents the specific accumulation that produced the condition in the first place.
The standing question
Add one question to the quarterly review permanently: are we doing more work to produce the same output than we were a year ago. Attach the four slopes. That question is the entire diagnosis in a form that runs without you, and it is the difference between fixing this once and fixing it once a decade.
The alternative that gets proposed instead
At some point in the second quarter somebody senior will propose a growth initiative as the answer, and it will be well argued. A new market, an adjacent product, an acquisition. The proposal is attractive because it promises to solve the flat revenue line without anyone having to accept that the operating model is the problem, and it is the single most likely way this work gets displaced.
The counter is not to oppose growth. It is to ask what the initiative will run on. A business that cannot retire a product, cannot get a decision back inside a week, and cannot tell you its margin by family will execute a growth initiative using exactly those capabilities, and the result will be a larger version of the same condition with more capital attached to it.
When not to do this
Three situations where the honest answer is to leave it alone, at least for now.
When you cannot get the data
If the four slopes cannot be reconstructed, you do not have a case, you have a conviction. Convictions lose gate one. Spend the time building the reporting that would let you make the argument next year rather than making it badly this year.
When the clock is elsewhere
If the business is genuinely facing something with a date attached, a customer transition, a facility move, a regulatory change, do that first. Running a no-crisis turnaround alongside a real deadline gives you two efforts at half strength, and the one with the date will win anyway.
Frequently asked questions
How long does this take compared with a crisis turnaround?
Longer at the front and about the same at the back. Budget sixty days for case building where a crisis would have given you the first move on day one, then expect the operating work itself to run on a similar twelve-month arc. The total is roughly a quarter longer.
Do you need the CEO or owner on side first?
Yes, and earlier than in any other situation. You are proposing to spend organizational goodwill on a problem nobody has asked about, and that is a decision the person above you has a legitimate claim to be part of rather than to learn about second hand.
What if the numbers turn on their own?
Then you were wrong, you say so in writing against the assessment you dated at the start, and you have lost very little. That is the entire reason for naming your disconfirming evidence in advance. A test you defined yourself and lost costs a fraction of a conviction you defended past its evidence.
Is this the same as a growth initiative?
No, and confusing the two is the most common failure here. A growth initiative sits on top of the existing operating model and inherits it. This work changes the model, which is why it comes first. Bolting expansion onto a business that cannot retire anything produces a larger version of the same problem.
Monday morning, pull revenue by product family for as many years as your system holds. That single query is the beginning of the case and it takes about twenty minutes.
About the Stagnation Assassin
Todd Hagopian is a Fortune 500 transformation executive who has generated $3B in shareholder value across Berkshire Hathaway, Illinois Tool Works, Whirlpool, and JBT Marel, where he serves as Global VP of Product Strategy and Marketing. Known as The Stagnation Assassin, he is the author of two published books: The Unfair Advantage: Weaponizing the Hypomanic Toolbox and Stagnation Assassin: The Anti-Consultant Manifesto. His blog is published in 15+ languages and read by operators worldwide. Bring him to your stage via his speaking page or connect with him on LinkedIn.
Most leadership teams will not accept this argument from an insider on the first pass. Hearing the four slopes laid out by somebody with no stake in your internal politics moves the room faster than another deck does. Bring it to your leadership offsite.
See also: The 4 Beliefs Your Industry Has Never Tested, When a Turnaround Works and When It Won’t