A New Supervisor's 30-60-90 Day Plan for the Manufacturing Floor
A 30-60-90 day plan built for a real manufacturing floor, not a corporate template: earn trust, fix one broken thing, then own the metrics.
Search for a 30-60-90 day plan and you get the same corporate template every time. Days 1 to 30: “learn the company culture and meet stakeholders.” Days 31 to 60: “identify quick wins and align with leadership goals.” Days 61 to 90: “drive strategic initiatives.” That language is written for a knowledge worker who got hired into an office, and it falls apart the second you take it onto a production floor.
Here is why it fails you specifically. On a floor, nobody cares about your plan. They care about whether the line runs and whether you are someone worth following. The crew has seen new supervisors come in with a binder full of “strategic initiatives” and leave eighteen months later having changed nothing that mattered. Your 30-60-90 is not a document you present to your boss. It is a roadmap for earning the right to lead people who can already do the work without you.
So here is the version that fits the floor. The throughline is simple: on a production floor, authority is earned by competence and follow-through, not handed to you with the title. Each phase has one job, and you do not move to the next one until the last one is real.
Days 1 to 30: Earn trust and learn the real process
The mistake almost every new supervisor makes is treating month one as the month to prove they belong by changing things. Wrong instinct. Month one is for being visible, learning names, and finding out how the operation actually runs versus how the work instructions say it runs. You change almost nothing on purpose.
If you have not read the first-week plan, that is days one through five of this phase. The rest of the month is the same discipline stretched out:
- Be on the floor, not in the office. The new supervisor who hides at a desk answering email is invisible, and invisible reads as either lazy or scared. Be where the work is. People decide whether they trust you by watching you, not by reading your plan.
- Learn names and learn jobs. Every operator, every shift, what they run, how long they have run it. Get this wrong and you signal that the people do not matter to you. Get it right and you are already ahead of the last three supervisors.
- Find the real bottleneck. Not the one on the slide deck. Walk the process start to finish and find the station where the work actually piles up, where the overtime gets burned, where the expedites come from. The crew already knows where it is. Your job in month one is to learn what they know.
- Change almost nothing. When you see something that looks broken, write it down and leave it alone. Half the time the thing that looks wrong is the workaround keeping the line running, and the supervisor who rips it out in week two becomes the cautionary tale by week three.
The signal that month one worked: people start telling you things without being asked. When an operator flags a problem to you unprompted, you have crossed the first threshold. That is the crew deciding you are worth talking to.
Days 31 to 60: Fix one visible thing the crew already knows is broken
Now you spend the trust you built. Month two is about a single quick win, and it has to be the right kind of win. Not a metric you improved on a spreadsheet. A visible, physical thing the crew has been complaining about for months that nobody bothered to fix.
This matters more than it looks. Back in month one you asked people what makes their job harder than it needs to be. You have a list, and somewhere on it is something small, fixable, and annoying that the crew has stopped expecting anyone to handle. The tool that is never at the station. The light over the inspection bench that has been out for a year. The form everyone fills out that goes nowhere. Fix that.
You are not fixing it because it is the biggest problem. You are fixing it because it proves you listen and you follow through. The message lands without you saying a word: I asked what was broken, you told me, and I did something about it. That beats any speech about your management philosophy.
A few rules for picking the win:
- It has to be visible. Something people see or touch every shift. A backend process nobody notices does not build credibility even if it saves more money.
- It has to be the crew’s complaint, not yours. If you fix something you think is broken but they do not, you taught them you do not listen.
- It has to actually get done. A quick win you announce and then let stall is worse than doing nothing. Half-finishing it teaches the crew that you are like every supervisor before you.
- Credit goes to whoever flagged it. “Maria pointed this out, so we fixed it.” Now everyone knows that telling you about a problem leads somewhere.
The signal that month two worked: the next time you ask the crew what is broken, you get a longer list and more honest answers. You proved that flagging a problem to you is worth their time, so they bring you more.
Days 61 to 90: Own the metrics and start a routine
By month three you have credibility, you know the operation, and you have proven you follow through. Now you start acting like the person responsible for the numbers, because you are.
Two things happen in this phase. First, you take ownership of your metrics. Whatever your plant tracks (safety, quality, output, scrap, on-time delivery), you stop treating those numbers as something that happens to you and start treating them as yours. You know the real bottleneck from month one, so you know which number to move, and you point your attention there instead of spreading it thin across all of them.
Second, you stand up a routine that outlasts your attention, and the core of that routine is a short daily huddle. If you have not started one yet, this is the month to make it a habit the crew can count on. I wrote a full agenda for it in the daily huddle post, but the short version is five to ten minutes, same time, same spot, standing up, walking yesterday’s results and today’s plan. The huddle is what turns you from a firefighter into a supervisor, because it forces the operation to surface its problems to you every morning instead of at the end of a bad week.
Then pick one improvement and run it through to done. One. Not a transformation plan. You spent two months learning where the real bottleneck is, so attack that, with the crew’s help, and finish it. Owning the metrics plus one finished improvement plus a routine that holds: that is what month three is for.
The signal that month three worked: the huddle runs whether or not you are perfectly on your game that day, and the crew is bringing improvement ideas to it. The routine has started to carry itself.
The 30-60-90 plan on one page
Here is the whole thing in a form you can actually use. Notice that each phase has one goal and one signal that tells you it worked, so you are not guessing whether you are ready to move on.
| Phase | Goal | Do this | Signal it worked |
|---|---|---|---|
| Days 1 to 30 | Earn trust, learn the real process | Be visible, learn names and jobs, find the real bottleneck, change almost nothing | People tell you about problems without being asked |
| Days 31 to 60 | Prove you listen | Fix one visible thing the crew already knows is broken, credit whoever flagged it | The crew brings you a longer, more honest list of problems |
| Days 61 to 90 | Own the metrics, start a routine | Take ownership of your numbers, run a daily huddle, finish one improvement | The huddle runs itself and the crew brings ideas to it |
The reason this works and the corporate template does not is the throughline running down that signal column. Every phase is built around the crew’s response, not your activity. You can check every box on a generic 30-60-90 plan and still be a supervisor nobody respects, because the boxes measure what you did, not whether anyone followed. The signals measure what actually matters on a floor: whether the people are deciding you are worth following.
What to skip
The pressure to do the opposite is strong. Plenty of new supervisors feel they have to make a splash early to justify the promotion, so they reorganize a line in week two, call out a long-tenured operator in front of the crew, or roll out three initiatives at once. It almost always backfires. You burn the trust you have not earned yet, and the crew quietly waits you out.
Skip the big speech. Skip the reorg you do not understand yet. Skip the discipline campaign. Skip trying to fix the metrics before you know which one actually matters. Move slow in month one so you can move fast and have it stick in month three. Authority you grab does not hold. Authority you earn does.
Bringing it together
Ninety days, three jobs: earn trust by learning the floor, prove you listen by fixing one real thing, then own the numbers and build a routine. The order is not optional. You cannot own the metrics in month one because nobody is following you yet, and you cannot fix the right thing in month one because you do not yet know what the right thing is.
I keep a free fill-in version of that one-page 30-60-90 table, with space to write your bottleneck, your month-two quick win, and your month-three improvement, so you can map your own ninety days instead of carrying it in your head. You can grab it through the field notes list at the bottom of this page. The deeper playbooks behind each phase are spread across my manager’s titles on the books page.
Ninety days is enough time to become the supervisor the crew trusts. It is not enough time to fake it. Spend the first thirty earning the right to lead, and the next sixty will go a lot easier.
Related notes
Liked this? Get the free SOP Writing Cheat Sheet.
The 6-step SOP format on one page. Free.