May 22nd, 2014 at 2:30 pm    
Employees and management see shift schedules from entirely different perspectives. When employees discuss their ideal shift schedule, they talk about things like shift length, work patterns, and shift start/end times. That's because these features are related to their primary concern: time off.
- Shift length affects the number of scheduled days off and percentage of weekends off.
- Work patterns influence the length and frequency of the breaks.
- Shift start/end times determine when they get to go home.
When managers of shiftwork operations discuss the organization's shift schedule, they are primarily concerned about the coverage requirements, staffing levels, absence rates, and overtime. That's because these features affect their main concern: the organization's resources.
- Coverage requirements define the amount of resources needed (total work hours per week).
- Staffing is the primary resource available to the organization.
- Absence rates determine the staff's availability and the amount of overtime needed.
- Overtime is seen by some as an unnecessary cost and by others as a strategic tool to boost the weekly work hours and/or cover absences.
Employees rarely consider the impact of their preferences on the organization's resources. Go to any employee forum and read the posts related to work schedules. You'll read about a group that adopted 10-hour shifts and how all the employees love them. Or how another group thinks a 6-on-3-off pattern would be better than the 5-on-2-off pattern they work now - because of the 3 consecutive days off. You also might find requests for a copy of someone else's schedule. No one ever mentions coverage requirements, the impact on absence coverage, or how many employees these choices would require. It's all about days off, weekends off, or not having to work too many days in a row.
So how can managers accommodate both the needs of the organization and the preferences of the employees? The only way to satisfy both sides is to start with what's feasible for the organization, and then seek out options that will satisfy employees. If you start with what employees want, you might get inconsistent or insufficient coverage, coverage that's not matched with the workload or staff size, or schedules that consume more resources than available.
Notice that I'm only indicating where to begin the search for a new schedule. Starting with what is feasible may narrow the scheduling possibilities or preclude certain approaches, but it doesn't mean the employees will have terrible schedules. And it doesn't mean they won't have any choices. What it does is join the management team with the workers in finding a solution that is best for both the organization and the employees.
|
May 16th, 2014 at 10:24 am    
I had a call from a California company earlier this week that was operating on a 24/5 basis. They expected to go to 24/7 in the next year or two and wanted to take steps now to prepare for the eventual change to a continuous operation. Their current schedule used three 8-hour shifts that rotated every 6 weeks. The shifts started at 5:00 a.m., 1:00 p.m., and 9:00 p.m. They were paying shift differentials for the 2nd and 3rd shifts. They were not represented by a union.
Here is what I recommended:
- Shift length. Most companies that change to 24/7 end up adopting 12-hour shifts. Not all, but a substantial majority. However, since this company was located in California and not represented by a union, it would have to pay overtime after 8 hours a day. This would make 12-hour shifts too expensive, leaving them with no choice other than 8-hour shifts.
- Schedule format. In general, employees prefer fixed shifts while management prefers rotating shifts. Since this company would be using 8-hour shifts, the choice was obvious. 8-hour fixed shifts often require a few more employees than rotating 8-hour shifts, making them a much more expensive choice. Because of this, I recommended that they stay with the rotating shifts. I also warned them that with 24/7 schedules, the employees would change shifts every week rather than every 6 weeks like the are doing now.
- Shift differentials. The purpose of the shift differential is to attract employees to the less desirable shifts. Since the company was using rotating shifts, everyone was working those shifts. There was no need for an incentive. Shift differentials are only appropriate for fixed shifts. With rotating shifts, they are nothing more than a wage increase. To keep the employees' pay the same, the company should replace the differential with an across-the-board pay increase.
- Shift start times. Early start times for the day shift will result in fewer hours of sleep. When you combine this with the rotating shifts, it's a double whammy. I recommended changing the day shift to start no earlier than 6 a.m.
I've run into other companies preparing for continuous operations that were considering transitional changes that would have made the final step to 24/7 much more difficult or that would have locked them into a more costly position. That's why it's important to visualize the key features of the 24/7 schedule in advance, so that the preparatory steps are in alignment.
|
April 24th, 2014 at 1:22 pm    
When organizations expand from working 5 days a week to 7 days a week, there will always be someone who suggests hiring a weekend crew. The current employees don't want to work weekends, so why not bring in someone else to do it? That would make the existing workforce happy. Besides, there are plenty of people who would do anything to get a job, even if it means working every weekend. It's a way to get their foot in the door. So everyone wins, right?
Unfortunately, no! There is a big loser, and it's the organization itself. Here are the things we typically hear about weekend crews that have been in place for a year or more:
- The weekend crew has a high turnover since the employees are continuously leaving for jobs with better hours (especially on the night shift).
- The weekend crew has high absenteeism. The weekend job is typically their second job. When they go on vacation from their "main" job, they simply call in sick for their weekend job.
- The weekend crew is out of touch with the rest of the plant.
- The weekend crew personnel move to the weekday crews as soon as there is an opening, which keeps the weekend crew staffed with the newest and least-skilled employees.
- The weekend crew typically performs at about 60% of the rate expected of weekday employees.
- If the weekend crew is also given weekday shifts (to bring them closer to 40 hours/week), the plant becomes overstaffed on the extra days they are scheduled to work.
- The weekend crew often gets a full benefits package. This means a 50% burden rate on the weekday employees equates to a 60-85% burden rate on the weekend crew's hours.
But it gets worse. The weekend crew will continue to under-perform unless the company over-pays. Some companies, in an attempt to improve retention and performance of the weekend crews, may pay 40 hours for 24 hours of work. This can raise the hourly cost of the weekend work to as much as double that of a weekday crew when the cost of benefits is factored in.
Once this becomes apparent (usually within the first 18 months) it's too late. Changing to a true 24/7 schedule will seem like a take-away and the workforce will fight it - tooth and nail. So before you jump at this tempting solution, please read this post one more time.
|
April 14th, 2014 at 4:19 pm    
This is the 7th an final post in a series on Fatigue in the Workplace. Previous posts on this topic have covered the impact of: (1) education, (2) start times, (3) shift length, (4 consecutive days of work, (5) rotating shifts, and (6) employee preferences. Today's post will address the role of overtime in employee alertness and fatigue.
Let's face it, overtime disrupts people's lives. They have plans that get changed at the last minute. They are forced to work when they had other plans. How do they respond? Forfeiting sleep is one of the most common ways employees try to recover time off lost to overtime.
How much overtime is too much is a difficult question to answer. Most companies feel that an annual average of between 5% and 15% is about right. However, there are a lot of considerations other than alertness that go into finding the perfect amount for any operation. You may wish to read a more complete article on the impact of high overtime (http://www.shift-schedule-design.com/preview/uploaded/files/Overtime%).
Here is a quick summary from the above referenced article. "Our surveys of shiftworkers show that, on average, they get 21% less sleep time on the days they work than the days they are off. When employees work lots of overtime, they don't get time off to recover or catch up on their sleep. This, in turn, can lead to fatigue and reduced alertness. Managers simply cannot ignore the possibility of increased safety and quality incidents under these conditions."
|
April 1st, 2014 at 5:57 pm    
This is the 6th in a series of posts regarding employee alertness or fatigue in the workplace. This post will focus on employee preferences regarding their shift schedules.
People judge their work schedule, not by when they have to come to work, but by when they can stay home. In short, they focus on their time-off.
What people really want is a schedule that minimizes the conflicts between when they want to be off work and when they can be off work. There is rarely a perfect fit and you will never find a workforce where 100% of the people want the same thing. However, minimzing a majority of the schedule conflicts should be your goal.
Why? When there is a conflict, people will find a way to do what they want to do, often at the expense of sleep. Less conflict equals better sleep patterns, which results in higher alertness and better performance.
There is no pattern that is "best" fo every employee demographic. If you want to know what your workforce wants - ask them.
|
March 28th, 2014 at 2:30 pm    
This is the 5th in a series of posts regarding scheduling considerations that affect employee alertness and fatigue.
In this post, we're going to take a brief look at the impact of the schedule format, i.e. fixed vs. rotating shifts. This is an important scheduling decision all organizations must make. Should the employees only work a single shift or should they periodically rotate through all the shifts?
You can read the pros and cons from the employee and management perspectives elsewhere on my website (http://www.shift-schedule-design.com/Fixed_Shifts). As you can see, this is a pretty complex decision. For the single issue of alertness, however, the answer is simple: Fixed shifts are the best, period. There is substantial research showing that rotating shifts have higher health risks and lower overall alertness than fixed shifts.
I would never base the decision on fixed vs. rotating shifts (what I commonly call the schedule format) on alertness alone. But since this series of blog posts is focused on fatigue in the workplace, skipping this scheduling variable would be inexcusable.
|
March 24th, 2014 at 10:53 am    
This is the 4th post on the subject of "fatigue in the work place."
People get less sleep on the days they work than the days they are off. With each consecutive day of work, they fall farther and farther behind in their sleep, or what is commonly referred to as sleep debt. Sleep debt accumulates and is very subtle. People don't realize they are losing a small bit of cognitive ability every day their sleep debt builds up. With each passing night, they come to work less safe and less productive.
Reducing the number of consecutive days of work, gives employees time off to catch up on their sleep and pay off some of the sleep debt. While the number of days needed to fully recover is uncertain, most researchers believe that at least 2 days off in a row are needed to have a recuperative impact.
The problem with reducing the number of consecutive days of work, of course, is that the number of weekends off can drop dramatically, especially with 8-hour shifts. There is no easy solution to this. The schedules we design never exceed 7 consecutive 8-hour shifts or 4 consecutive 12-hour shifts. Only in special circumstances do we feel that these limits can be exceeded safely.
|
March 6th, 2014 at 3:05 pm    
This is the third in a series of posts regarding fatigue in the workplace. The first post addressed educating employees about the need for 8-hours sleep and the impact of sleep deprivation. The second post addressed early day shift start times and how they reduce the amount of sleep people get. This post will address the impact of shift length on sleep and fatigue.
Intuitively, you would think that the longer the work day, the less sleep you would get. To a certain extent, this is right. We have found that people working a 12-hour shift get about 10 minutes less sleep per night than people working an 8-hour shift. But that's not a complete picture since it is only looking at the days of work.
People on longer shifts get more days off. Workers on 12-hour shifts will get 87 more days off each year than those on 8-hour shifts. Since people sleep more on their days off than they do on the days of work, the people on 12s actually will average more sleep than those on the 8-hour work days. Here's a link to a table showing the details: http://www.shift-schedule-design.com/12-Hour_Shifts. You may have to scroll down a couple of times to find the table.
What do think? Counter-intuitive isn't it?
|
March 3rd, 2014 at 11:11 am    
This is the second post in a series on the subject of fatigue. In each post, I will focus on steps that management can take to address fatigue.
In the first post, I noted that employees don't think they need more than 7 hours sleep. Managers may want to post articles explaining the impact of sleep debt and the need for more than 7 hours of sleep a day. Just run a Google search for "sleep debt" and copy of few of the articles. If you can find anything by William Dement, he is the subject matter expert. I doubt that doing this will change employee behavior, but it may help to justify any actions management undertakes to address fatigue.
This post draws from a previous post in which I showed how early shift start times reduce the average hours of sleep for day shift workers (http://www.shift-schedule-design.com/Blog?m8:post=problems-with-early-morning-start-times). To summarize, people who start work at 7 a.m. sleep about 20 minutes more per night than those who start a 6 a.m.
Changing shift start times is difficult because people build their lives outside of work around the shift start and end times. When I review employee surveys, they often list the pros and cons of early start times. They say that the best thing about their current schedule is that they get off early, giving them time to do all sorts of things. Then they turn around and say that the worst thing about their schedule is having to get up so early and always feeling tired. How do you resolve this dilemma? It's both the best and worst features of your schedule - at the same time.
The other consideration with shift start times is traffic congestion. Later shift start times may require employees to spend extra time commuting. This takes time away from other activities. For those "other" activities to continue to take place, sleep is often the first thing sacrificed. Although many companies flex their hours to allow commuters to minimize time spent in traffic, this can be challenging for those with shiftwork operations.
Early start times affect more than just shift workers. I've seen articles about the impact of early school start times on student performance. Teenagers have an internal clock that makes it difficult for them to be alert early in the morning, suggesting that learning would improve if schools started at 9 a.m. instead of 8 a.m.
|
February 24th, 2014 at 1:54 pm    
The American workforce is at war with a subtle enemy. That enemy is so subtle that many deny it even exists. The name of the enemy is fatigue and the cause is sleep deprivation.
Employee surveys show that most people think they only need 7 hours of sleep per night, yet they are actually getting much less than that. People readily exchange sleep for other activities, thinking there is little harm.
The fact is they need 8 hours. The result is a continual build-up of sleep debt as they get less sleep than they need night after night. After two weeks of mild sleep deprivation, cognitive abilities approach those of someone who is legally drunk.
Convincing employees that getting less than 8 hours of sleep is unsafe and unhealthy is not an easy task. Even if they believe that to be true, they still feel the sacrifice is worth the extra time spent with family, friends, hobbies, or simply watching TV.
I'm going to post a few more blogs on some of tactics managers can use to address fatigue in the workplace. If you have any horror stories you'd like to share, please feel free to post a comment.
|