A New Supervisor's First Week on the Floor: A 5-Day Plan
A day-by-day plan for your first week as a new manufacturing supervisor, with one usable artifact per day so you're not winging it.
You got promoted off the line, or you got hired in from outside, and now you’re the supervisor. Monday morning a crew of people, some of whom did your job longer than you’ve been alive, are watching to see what kind of boss you’re going to be. Most of what gets written for this moment is leadership-poster nonsense. “Be authentic.” “Build trust.” Great. How? On Monday? At 6 a.m.?
Here’s a real plan. Five days, one concrete thing to do each day, and one artifact you can actually use so you’re not improvising in front of people. The whole point of week one is this: you are learning the operation and earning the right to change it later. You are not fixing it yet. Move slow on purpose.
Day 1: Meet the team without overpromising
The single biggest week-one mistake is walking in and announcing how things are going to be different. You don’t know enough yet, and the crew has heard the new-boss speech before. They’re not impressed by vision. They’re watching whether you keep your word about small things.
So keep Day 1 short and honest. Get everyone together for five minutes at shift start. Here’s a script you can run almost word for word:
“I’m [name], I’m the new supervisor here. I’m not going to come in and change a bunch of stuff this week, because I don’t know your jobs as well as you do yet. My plan for this week is to watch, ask a lot of questions, and figure out how things actually run. If something’s broken or making your job harder, I want to hear it, but I’m not going to promise to fix things I don’t understand yet. What I will do is tell you the truth and do what I say I’m going to do. That’s it. Let’s get to work.”
That’s the whole speech. It sets two standards that matter: you tell the truth, and you keep your word. You’ll be held to both, which is exactly what you want. Then spend the day learning names and where things are. Write the names down. Forgetting someone’s name on Day 2 undoes a lot of Day 1.
The artifact for today is that intro script. Adapt the words to sound like you, but keep the two promises and keep it short.
Day 2: Watch before you touch anything
Day 2 is for observation, and I mean structured observation, not wandering around looking busy. You’re going to see things that look wrong. Resist the urge to “fix” them on the spot. The thing that looks wrong is often the workaround that keeps the line running, and the new boss who rips it out on Day 2 becomes a cautionary tale by Day 4.
Carry an observation log. Three columns is enough:
- What I saw. Plain description. “Operators at station 3 walk to the tool crib twice an hour for the same bit.”
- Question to ask later. “Why isn’t that bit kept at the station?”
- Don’t act yet. A checkbox to remind yourself this is a note, not a to-do.
Walk the whole process start to finish. Watch a changeover if one happens. Stand where the work is and shut up. The log keeps you from either forgetting what you saw or jumping on it too early. By the end of the day you’ll have a page of real questions instead of a head full of vague impressions, and those questions are gold for the conversations coming up.
The artifact for today is that three-column observation log.
Day 3: First one-on-ones
Now you start the conversations. A short one-on-one with each crew member, ten to fifteen minutes, is the highest-value thing you do all week. You’re not evaluating them. You’re learning the operation through the people who run it, and you’re letting them size you up in a low-stakes setting.
Use a light template so every conversation covers the same ground and nobody feels singled out:
- “How long have you been doing this, and what do you run?”
- “What’s the part of your job that works well?”
- “What’s the thing that makes your job harder than it needs to be?”
- “If you were me, what’s the first thing you’d look at?”
- “Anything you want to ask me?”
Then the most important move: write down what they tell you, and if you commit to looking into something, actually look into it and circle back. The fastest way to lose a crew in week one is to ask “what would you fix?” and then do nothing with the answers. You don’t have to fix it. You have to follow up. “I asked maintenance about that bit, here’s what they said” buys you more credibility than any speech.
The artifact for today is that one-on-one template.
Day 4: Stand up a daily huddle
By Day 4 you know enough names and enough about the operation to start running a short daily huddle. This is the habit that makes you a supervisor instead of a firefighter. Five to ten minutes, same time, same spot, standing up so it stays short.
A simple agenda that works:
- Yesterday. What did we make, what got in the way? Keep it to the one or two things that mattered.
- Today. What’s the plan, what’s the priority, what’s different today (a rush order, someone out, a machine down)?
- Safety and quality. Any near-miss, any quality issue, anything to watch for.
- Help needed. Who’s blocked, who needs something from me or from another station?
Run it tight. The fastest way to kill a huddle is to let it turn into a twenty-minute gripe session, and the second fastest is to make it a status report you read at people. Ask, don’t lecture. End on the same beat every day so people can count on getting back to work. If you protect the ten minutes and you actually clear the “help needed” items, the huddle becomes the most useful part of everyone’s morning within a couple of weeks.
If your plant runs a board with Safety, Quality, Delivery, Inventory, and Productivity, the huddle is where you walk that board. Same idea, just with the numbers in front of you.
The artifact for today is that huddle agenda.
Day 5: Run a week-one retro on yourself
Friday, before you leave, spend twenty minutes reviewing your own first week. Not the crew’s. Yours. This is the habit that separates supervisors who get better from supervisors who just get older.
Four questions:
- What did I learn about how this operation actually runs?
- What did I say I’d do this week, and did I do it? (Go back to Day 1’s two promises and Day 3’s follow-ups. Be honest.)
- From my observation log, what are the two or three things actually worth changing, and which one do I tackle first next week?
- What did I do this week that landed badly, and what will I do differently?
Write it down. Keep it. In a month you’ll want to see how far the operation, and you, have come. This is also where week one connects to everything after: you’ve spent five days earning the right to make a change, and now you’ve got a short, evidence-backed list of what that change should be. You start week two with a plan instead of a panic.
The artifact for today is that week-one retro sheet.
The throughline
Five days, five artifacts: an intro script, an observation log, a one-on-one template, a huddle agenda, and a retro sheet. Notice what’s not on the list: a turnaround plan, a list of people to discipline, a big speech. Week one is for learning and for keeping small promises. The credibility you build doing that is what lets you actually change things in week three without the crew digging in against you.
I keep free versions of all five of these as fill-in templates, the script, the log, the one-on-one, the huddle agenda, and the retro, so you can walk in Monday with the paperwork already handled. You can grab them through the field notes list at the bottom of this page. If you want the deeper playbooks behind each one, including onboarding, running effective one-on-ones, the daily huddle, and the SQDIP board, those are covered across my manager’s titles on the books page.
Move slow this week. You’ll move faster for it later.
Liked this? Get the free SOP Writing Cheat Sheet.
The 6-step SOP format on one page. Free.