The standard advice for a new plant manager is a 30-60-90 day plan. Learn in the first thirty, plan in the next thirty, act in the final thirty. It appears in every leadership book, it is taught in every transition program, and it is written for a general manager joining a stable business in an office.
It fails in a plant for one specific reason. It assumes the situation you walked into is uniform and that the only variable is you. It is not. There are four distinct situations a new plant manager can inherit, they demand different first weeks, and applying the learn-plan-act template to three of the four will cost you the quarter. In one of them it will cost you considerably more than that.
Short answer: Establish which of four situations you are in during week one, then run the ninety days that situation requires. A crisis plant needs you acting in week one. A drifting plant needs you counting for two weeks and then acting hard. A stalled plant needs you building a case nobody has asked for. A healthy succession needs you doing almost nothing visible for a month. Getting this wrong is the most common first-quarter error in the job.
Why is the standard 30-60-90 template wrong here?
Because it treats time as the organizing variable when the organizing variable is the state of the business you inherited. Thirty days of learning is correct in one of the four situations, disastrous in another, and roughly twice as long as necessary in a third.
Consider what the template asks you to do in a plant that is three weeks from a cash event. Learn for thirty days. By day thirty the decisions that were available to you on day one are gone, taken by circumstance rather than by you, and your plan is now a description of a narrower set of options. Nobody in the organization will say this out loud. They will simply stop bringing you things.
Consider it in the opposite case, a plant that is performing adequately under a respected predecessor. Here the template’s action phase at day sixty is actively harmful, because you will act on a ninety-day understanding of a business that has been running well for a decade, and the organization will read your first change as a judgment on people who were doing fine.
The template is not wrong because it is generic. It is wrong because it is confident about sequencing in a job where the correct sequence is determined by conditions the template never asks about.
There is a second cost to the template that nobody warns you about, which is what it does to the people watching. A plant reads a new manager’s first three weeks as a statement of intent, and the statement it reads from a formal learning phase is that the important decisions will be made elsewhere and later. In a drifting operation that reading is close enough to what the previous two years felt like that the organization simply carries on drifting, now with a note in its calendar about your day-sixty plan.
Which of the four situations did you walk into?
Two questions settle it, and you can answer both inside five days. Is the business under an active clock, meaning a cash, customer, or regulatory event with a date attached? And was your predecessor removed, or did they move on?
The clock question is a fact and you get it from the CFO in an hour. The predecessor question is not always answerable directly, but the plant knows, and the way people talk about the previous manager in your first week will tell you more accurately than the org announcement did.
Where the answers give you a clock, you are in a crisis and the predecessor question stops mattering. Where there is no clock and the predecessor was removed, you are in a drift. Where there is no clock and they moved on, you are in either a stall or a succession, and the tiebreaker is whether performance is flat or genuinely healthy.
What do the first 90 days look like in a crisis plant?
You act in week one, because there is no learning phase available and pretending otherwise is a decision to let the clock take your options. This is the situation the standard template damages most.
Week one is cash. Get cash on hand and weekly burn on day one, then work through the five places it hides: inventory sized against an old reliability assumption, receivables past terms, premium freight, capital in flight against dead assumptions, payables terms nobody renegotiated. None of that removes capability, which is what makes it available to you before you understand the plant.
Weeks two and three are measurement, compressed. You do not get the two-week diagnostic in this situation. You get three days of it: count the constraint yourself twice, compare against the reported number, and establish the four numbers. Everything else waits.
Weeks four through twelve are the fastest margin levers and nothing else. Discount drift, expedites, scrap on the two worst part numbers, unscheduled overtime. Resist every structural idea that arrives during this period, and there will be several, because structural work consumes the calendar you are trying to buy.
The thing that will be hardest is that you will be visibly acting on incomplete information, and some of your decisions will be wrong. That is the cost of the situation, not a failure of your process. An executive who insists on certainty in a crisis plant is choosing to be right at a date when it no longer matters.
One more thing about crisis plants, and it is the part most first-time managers are least prepared for. You will be handed at least one proposal in the first fortnight that solves a real problem, has a solid business case, and takes nine months. Turning it down is correct and it will feel like negligence, because the person bringing it has been trying to get it approved for two years and is entirely right about the underlying issue. Say yes to the diagnosis, no to the timing, and put a date on when you will revisit it. The distinction between rejecting an idea and deferring it is worth stating out loud, because the organization will not infer it.
What do they look like in a drifting plant?
A drifting plant is one where performance has slid for long enough that your predecessor was removed, and it is the situation where the full two-week diagnostic pays best. You have time, the organization expects change, and both of those are assets that expire.
Weeks one and two are the diagnostic in full, exactly as written: walk the floor alone, count the constraint twice, read the gap, establish the four numbers, log decisions for a week, sort downtime by asset, look at margin by family, have the commercial conversation, write the one page. The full procedure is in the two-week plant diagnostic.
Week three is where drift situations are won or lost. Publish the one page and make three visible decisions in the same week. Not a strategy. Three specific things, with names and dates attached. The organization has been waiting to find out whether the new manager decides, and it is running that test whether you know it or not.
Weeks four through twelve, you fix the decision layer first and the margin levers second. Raise thresholds, put a 24-hour clock on escalation, start the daily standing meeting. That work is unglamorous and it is what makes everything you do in month four onward stick.
The organization has been waiting to find out whether the new manager decides. It is running that test in week three whether you know it or not, and silence is an answer.
Two cautions specific to drift. The first is that you will inherit a set of explanations for the decline, delivered confidently and consistently by people who have had two years to rehearse them, and they will centre on labor, equipment, or demand. Those are the three causes that look like the problem and usually are not. Take them seriously, test them against your own count, and expect at least two of the three to dissolve.
The second is that the goodwill you have in a drift situation is finite and front-loaded. The organization wants change in month one, tolerates it in month two, and begins to resist by month four as the specifics start landing on individuals. Front-load the structural decisions accordingly. Managers who use months one and two to build consensus arrive at the hard calls precisely when the appetite for them has gone.
What do they look like in a plant that is fine but stalled?
A stalled plant is the hardest of the four, because nothing is wrong and therefore nothing gives you permission. Performance is flat, the numbers are acceptable, your predecessor left on good terms, and every change you propose will be measured against a baseline that nobody in the building considers a problem.
Your first month is not a diagnostic, it is case building. You run the same counting, but the output is different: you are assembling evidence that a comfortable business is losing ground, and the evidence has to be strong enough to survive people who like the current state. Direction of travel is your best material. Eight quarters of gross margin by product family, eight quarters of SKU count, eight quarters of decision return times if you can reconstruct them.
Month two is where you make it uncomfortable, and you do it with numbers rather than with rhetoric. The reading method for that is in how to read an underperforming P&L, and the behavioral version is in the stagnation signals. Both work better as a presented finding than as an opinion.
Month three is one deliberate, visible change that costs somebody something. Retire a product, close a report, reassign a role. The specific change matters less than the demonstration that retirement is now a thing this plant does, because the defining feature of a stalled operation is that it only ever adds.
Expect this to be lonely for a quarter. In the other three situations the plant either wants you to act or is willing to let you, and in a stall you are proposing to disrupt an arrangement that a lot of people are comfortable inside. You will be told, sincerely and repeatedly, that the numbers are fine. They are. That is the whole problem, and it is why the evidence has to be about direction rather than about level.
One tactical note. Bring your boss in early in a stall, earlier than you would in any other situation, because you are going to spend political capital on a problem nobody has asked you to solve. A boss who has seen the eight-quarter direction data in month one will back the month-three change. A boss who first hears about it when someone complains will not.
What do they look like in a healthy succession?
A healthy succession is the one situation where the standard template is roughly right, and where doing almost nothing visible for a month is the correct strategy rather than a failure of nerve. The plant works. Your predecessor built something. Your job in month one is to understand why it works before you touch any of it.
The trap here is the pressure you will feel to demonstrate value. New managers in healthy plants change things to prove they are managing, and the change lands on an organization that had no problem, which teaches everyone that your arrival was a cost. That impression takes a year to reverse.
Spend month one learning the mechanism rather than the results. Which specific practices produce the performance, who maintains them, and which of them depend on a single person who is now three years closer to retiring than they were when the system was built. That last question is usually the most valuable thing you will find, and it is invisible from the outside.
Month two and three, pick the one thing the plant is quietly bad at. Every high-performing operation has one, it is usually a thing that was never a problem because a strong predecessor compensated for it personally, and fixing it is both genuinely useful and politically safe because you are not undoing anyone’s work.
There is one exception to the do-nothing month, and it is worth watching for. If your predecessor was well regarded and left recently, there is often a decision they deliberately deferred until after the handover, and somebody in the leadership team knows exactly what it is. Ask directly in your first week: what did they leave for me. The answer is frequently the single most useful piece of information available in a healthy succession, and it is never in the handover document.
What is true in all four?
Four things hold regardless of situation, and they are the parts of the job you should treat as non-negotiable.
Count something yourself in week one. Every situation, no exceptions. The specific number matters less than the fact that you have one reading of the business that came from you and not from the reporting, because that reading is the only baseline nobody can revise later.
Say what you are doing and when people will next hear from you. Ambiguity in week one gets filled with the worst available rumor, and month two is a bad time to be undoing it.
Write a dated one-page position before day ninety. In a crisis that page is written on day fifteen. In a succession it is written on day seventy-five. It exists in all four cases and it goes to your boss.
And decide, deliberately, how much of your predecessor’s work you are going to keep. The Harvard Business Review argument on how to turn around nearly anything holds that the diagnosis phase should run longer than most operators allow, and I think that is right in three of these four situations and dangerously wrong in the fourth. Know which one you are in before you decide how much time to take.
Two more things that hold across all four. Meet the people who produce your numbers in the first fortnight, whichever situation you are in, because the production of a number and the number itself are different objects and only one of them appears in the report. And find out, early, what your predecessor was measured on. Plants optimize toward whatever the previous manager was rewarded for, and the residue of that optimization is still running long after the person has gone.
What should you have written down by day 90?
One page, in all four situations, containing four things: which situation you determined you were in and the evidence for it, what you found, what you changed, and what you will change next with dates attached.
The reason it is one page is that a situation you cannot state in a paragraph is a situation you have not isolated. The reason it is dated is that six months from now your reading of week one will be disputed by people with an interest in a different account, and a contemporaneous document is the only version that holds up.
Include what you got wrong. Every ninety days contains at least one call that did not survive contact, and naming it yourself, in writing, before anyone else does, is worth more to your standing than the two calls that worked.
Keep the page to one side of one sheet even when the quarter was eventful. The discipline is the point: an account that needs three pages is an account you have not yet reduced to a position, and a boss reading three pages will take away whichever paragraph happened to catch them rather than the judgment you actually formed. If the material genuinely will not compress, attach the detail behind the page and leave the page alone.
What if you are wrong about which situation you are in?
You will be, occasionally, and the recovery cost depends entirely on which direction you were wrong in. Treating a drift as a crisis costs you some credibility and some goodwill. Treating a crisis as a drift costs you the plant.
So the asymmetry tells you how to hedge. When the situation is ambiguous between crisis and drift, act as though it is a crisis for the first two weeks, because the crisis response consists almost entirely of releasing trapped cash and counting things, neither of which damages a plant that turned out to be merely drifting.
Between stall and succession the asymmetry runs the other way, and the hedge is to wait. Treating a healthy plant as a stalled one and forcing an unnecessary change is the more expensive error, and both situations give you the time to be sure.
Recheck at day thirty regardless. New information arrives constantly in a first quarter, and a situation call made on day five with the wrong predecessor story or an incomplete cash picture is worth revisiting once, in writing, before it hardens into the frame you use for everything else.
So the question was what to do in your first 90 days as a new plant manager, and the answer is that there is no single answer, only four of them. Spend week one finding out which one you are living in, and the rest of the quarter becomes considerably simpler.
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.
Moving operating leaders into new plants this year? The four-situation call is the one thing they will get wrong, and it is teachable in a session rather than learned across three assignments. Bring it to your operations leadership before their next placement.
See also: Should I Fix It, Sell It, or Shut It Down?, What It Costs to Fix a Business That Works