The Productivity Dip Nobody Talks About

Every operation has a period of reduced productivity. It happens every day, on every shift, in every industry. Yet most businesses continue to plan as though it doesn't exist.

I'm talking about the thirty minutes before a shift ends and the thirty minutes after a new shift begins.

For years we've measured uptime, efficiency, output, labour utilisation and production performance. We've invested heavily in technology, automation, reporting systems and now artificial intelligence, all in the pursuit of squeezing more productivity out of the working day. Yet one of the most predictable production realities continues to be largely ignored.

Productivity naturally tapers off around shift change. This isn't a criticism of workers, supervisors or management. It's simply an observation of human behaviour.

By the final thirty minutes of a shift, employees are operating at the point of greatest fatigue. They have spent hours solving problems, making decisions, responding to interruptions and maintaining concentration. Whether the shift is eight, ten or twelve hours long, physical and mental energy are lower than they were at the start of the day. At the same time, attention begins shifting toward what comes next. Workers are thinking about getting home, picking up children, preparing dinner, beating traffic or simply getting some rest.

The work is still being done. Machines are still running. Production hasn't stopped. But anyone who has worked on a production floor knows there is a difference between the first hour of a shift and the last.

On the other side of the shift change, the incoming crew faces a different challenge.

Although they arrive fresh, they are not immediately operating at full productivity. They are settling into the day. They may be grabbing a coffee, checking work orders, discussing overnight events, organising tools or speaking with outgoing personnel. More importantly, they are rebuilding situational awareness. They need to understand what happened before they arrived, what equipment is running, what problems exist and where attention is required.

This process takes time.

Most organisations refer to this period as a handover, but that description doesn't really capture what's happening. A handover implies that information is simply transferred from one person to another. In reality, workers are transitioning from one mental state to another. They are moving from being outside the operation to becoming fully engaged in it.

That transition has a productivity cost. The mistake many organisations make is treating this as a problem to be eliminated. Every few years a new technology arrives promising to solve communication issues, improve information flow or remove inefficiencies from the handover process. More recently, artificial intelligence has been presented as the next answer.

While these tools can certainly improve the quality of information available to workers, they don't remove the human condition.

The Last 30 Minutes: When Fatigue Starts to Take Over

People still need time to establish context when they arrive.

People still operate according to habits, routines and behaviours that have existed for as long as organised work itself. Technology can support these transitions, but it cannot eliminate them.

This is where many productivity discussions miss the mark. They assume that every reduction in output is evidence of a process failure. In reality, some reductions are simply a natural consequence of human beings operating within a production environment.

Understanding that distinction changes the conversation.

Instead of asking how to eliminate the shift change productivity dip, organisations should be asking how to design systems that acknowledge it. The goal is not to force workers to behave like machines. The goal is to create processes that work with human behaviour rather than against it.

This extends far beyond the traditional handover report. A written logbook, a verbal briefing or an email summary only addresses part of the challenge. Effective operational systems must support both the departure of experienced workers and the onboarding of incoming workers. They must fit naturally into existing work habits and provide information in a way that reduces friction, confusion and delay.

The organisations that achieve the highest levels of uptime are rarely the ones that ignore these realities. They are the ones that recognise predictable periods of reduced productivity and build their operating systems around them.

Perhaps the biggest opportunity lies in simply acknowledging that this one-hour window exists. Once organisations stop treating shift change as a perfectly productive period, they can begin measuring it differently, planning around it differently and supporting workers through it more effectively.

The thirty minutes before a shift and the thirty minutes after a shift are unlikely to ever become the most productive periods of the day. Nor should they.

They are a natural consequence of people handing over responsibility, knowledge and context to the next group of people responsible for keeping the operation running.

The sooner we stop pretending this productivity dip doesn't exist, the sooner we can start designing better systems around it.

How would you solve it?