New Shift Supervisor in 60 Days: What to Do Before Routine Drift Sets In

A new shift supervisor does not inherit only a roster and a production target. The role inherits the handover quality, the tempo, the exceptions, and the small shortcuts that decide whether routine work stays controlled or quietly drifts into exposure.

The shift is often where risk changes shape. A crew starts a little tired, a task starts a little late, a temporary arrangement stays one more hour, and the whole site learns to call that normal. A supervisor who only watches output will miss the point, because the real job is to keep the work honest while the pressure rises.

Across more than 25 years in executive EHS and more than 250 cultural transformation projects, Andreza Araujo has seen that repeated decisions under pressure shape the real culture. In Safety Culture: From Theory to Practice, she argues that culture lives in what people repeat. In A Ilusao da Conformidade, she shows that neat paperwork can hide weak control. This article uses both ideas for one purpose, which is to help a new shift supervisor make the first 60 days count in the field, not only on the schedule.

The thesis is straightforward. A shift supervisor earns authority by making the right stop easier than the wrong shortcut, because routine drift usually starts when people believe the exception is temporary and harmless.

What the shift supervisor needs to understand before starting

A shift supervisor is a control role before it is a people role. The supervisor sees the moments where work changes hands, the order changes, and the crew starts to improvise. That is why ISO 45001:2018 matters here. It requires operational control, competence, and change management, which means the supervisor has to know where the controls live and when they stop being real.

James Reason is useful because the shift rarely fails in one dramatic step. It fails when a tired crew, a weak handover, an ignored exception, and a rushed release line up across the same few hours. Patrick Hudson is also useful, since maturity is visible in how the team handles uncertainty, not in how polished the meeting sounds.

The job is not to police every movement. The job is to make sure the crew can still answer a few hard questions before the shift gets busy. What changed since the last handover? Which controls are open? Who can stop the work now? If those answers stay vague, the supervisor has not yet taken control of the real risk.

If you want a practical companion to this first-pass view, the article on new maintenance supervisor in 60 days shows how the same logic works when routine work starts to slip. The article on how to run a post-observation debrief that changes the next shift is also useful because it shows how to close the loop before the next crew inherits the same issue.

First week: walk the changes that happen between shifts

The first week should be a field walk, not a desk review. Start with the areas where the work changes fastest. Find the start-of-shift meeting, the handover point, the night note, the temporary route, the maintenance window, the cleanup zone, the contractor arrival point, and the place where the crew usually says, "we just do it this way for now."

Write down what changed by hour, not only by day. A shift supervisor needs to know which tasks get rushed at the end of a shift, which tasks get paused and restarted, which exceptions always appear after lunch, and which barriers weaken when the same people are asked to cover more than one role. That is where routine drift starts.

Use a simple field test. Ask three people what they do when a condition changes. If you get three different answers, the site is not managing a rule. It is depending on memory. That is not a stable control system, because memory is the first thing that bends under time pressure.

The article on how to build a permit revalidation routine in 14 days helps here because a shift handover should do the same thing as a permit review, which is separate current reality from yesterday's assumption.

First 30 days: make handover a control conversation

Most handovers fail because they exchange tasks, not control information. A good handover says what happened, what changed, what remains open, and what condition would stop the next step. A weak handover says the crew is busy, the job is almost done, and somebody will look again later. Those are not the same thing.

During the first 30 days, the supervisor should require four items every time. What is still open, what changed since the last shift, what has to be verified before restart, and what gets escalated now if the field does not match the plan. If the crew cannot answer those four points in plain language, the handover is not ready.

That discipline also protects the supervisor from a common trap, which is trusting the written record more than the field. In A Ilusao da Conformidade, Andreza Araujo argues that compliance on paper can hide real weakness. A neat handover sheet that does not reflect the live situation only makes drift look organized.

If the crew needs a practical reset loop, the article on how to run a post-observation debrief that changes the next shift shows how to turn one shift's lesson into the next shift's control. That is the difference between a lesson learned and a lesson repeated.

Month 2 and month 3: manage exceptions before they become procedure

By month 2, the supervisor should be looking for the exceptions that are trying to become the default. A bypass that was supposed to last one hour, a temporary staffing gap that keeps returning, a spotter role that disappears under pressure, or a cleanup zone that keeps stealing attention are all signs that the shift has started to normalize drift.

The market often treats these things as small operational compromises. They are not small. They are the way a site teaches itself that the written control can be bent when the hour gets busy. A supervisor who accepts that pattern has already lost the first layer of control, because the next exception will arrive with less resistance.

Andreza Araujo's experience in more than 250 transformation projects points to the same lesson every time. The site improves faster when leaders make the field fact harder to ignore. During the PepsiCo South America period, where the accident ratio fell 50% in six months, the turning point was not magic. It was visibility, follow-through, and the habit of closing the gap between what the team said and what the field showed.

That is why the supervisor should own the list of live exceptions and review it at the same hour every day. If the list grows, the site is not being flexible. It is accumulating hidden risk. If the list shrinks, the shift is learning how to keep control without drama.

Month 4 onward: build a daily rhythm the crew can repeat

By month 4, the supervisor should be building a rhythm that the crew can repeat without improvising the process each day. The rhythm can be simple. Start of shift with current risks, mid-shift with exception review, end of shift with handover proof, and one stop condition that everyone can use when the field changes.

The purpose is not to add more ceremony. The purpose is to make the control loop visible enough that the crew can trust it. A shift that knows where the open risks sit will respond faster, because people do not have to decode the system every time the pressure rises.

This is also the point where the supervisor should ask what the team would say if the same issue appeared for the third time in a week. If the answer is still "we will see", the shift has not yet built a learning habit. If the answer is "we stop, verify, and escalate", the role is finally doing its job.

For leaders who want to deepen the same skill set, the article on new maintenance supervisor in 60 days is a strong companion, because maintenance and shift supervision fail in the same place, which is where pressure makes a shortcut look useful. The article on how to build a permit revalidation routine in 14 days adds the control logic, while the debrief article adds the habit of closing the loop.

Common mistakes

The first mistake is treating induction as competence. Training matters, but a person who attended a session can still miss the control when the line is crowded, the crew is short, or the pace changes in the middle of the shift.

The second mistake is letting EHS carry the shift. EHS can support the system, although the shift supervisor owns the live handover, the exceptions, and the field decision that stops work before the wrong move spreads.

The third mistake is confusing a clean log with control. A tidy note is not the same thing as a verified condition, and a verified condition is the only thing that protects people when the next hour starts to slip.

The fourth mistake is tolerating the same exception twice. The first time can be a gap. The second time is usually a signal that the gap has become part of the workflow. That is the moment to intervene.

The fifth mistake is waiting for a monthly review to solve a live field issue. A shift supervisor has to act at shift speed, because the hazard also moves at shift speed.

Resources to deepen

Make The Difference: Be a Leader in Health & Safety is the closest fit for this role because it speaks directly to frontline leadership and the pressure of daily decisions. Safety Culture: From Theory to Practice is the best book for understanding how repeated decisions become culture. A Ilusao da Conformidade is the strongest reminder that a neat system can still fail in the field.

Three articles are worth keeping open while the new supervisor is learning the role. New maintenance supervisor in 60 days shows how to manage drift in another high-pressure role. How to run a post-observation debrief that changes the next shift shows how to close the loop. How to build a permit revalidation routine in 14 days shows how to keep control current when the work changes.

If the shift needs a broader leadership lens, Andreza Araujo's own work is the right place to start, because the same pattern repeats across production, maintenance, logistics, and supervision. The question is not whether the site has a procedure. The question is whether the procedure still matches the work when the hour is tight.

A new shift supervisor earns trust when the crew can point to one exception that was closed, one handover that told the truth, and one stop condition that prevented the next mistake.

For a deeper practical path, start with the store at loja.andrezaaraujo.com and the article archive at Andreza Araujo, because the first 60 days of the role are easier when the supervisor has both the books and the field logic in view.

FAQ

What should a new shift supervisor do first?

Start by walking the places where the work changes between shifts, then write down the open risks, the temporary fixes, and the conditions that stop the job. That is more useful than spending the first week in the office.

Is a handover note enough?

No. A handover note is only a record unless it tells the next crew what changed, what is still open, and what proof is needed before the work continues. The field has to match the note.

How do I know an exception is becoming normal?

When the same exception shows up more than once and nobody can say when it ends, the exception is already moving toward normal status. That is the time to escalate, not to wait.

What should I do when the crew is under time pressure?

Keep the control questions short and direct. Ask what changed, what is open, who owns it, and what stops the work now. A short control conversation works better than a long speech under pressure.

Which Andreza Araujo book fits this role best?

Make The Difference: Be a Leader in Health & Safety fits best for daily supervision. Safety Culture: From Theory to Practice and A Ilusao da Conformidade are the two strongest companions for understanding culture and field drift.