Feel the Burnout

Eleven Practical Ways for DevOps Engineers to Better Manage Their Work Environment

At OnPage, we know the importance of DevOps burnout and have explored the topic in different formats such as our eBook and video. The importance of the issue is highlighted by the following components:

• Decreased employee happiness: Employees become less satisfied and content with their work.
• Decreased productivity: Because employees are fatigued, they are less productive.
• Frequent job shifts: Throughout the industry, it has become standard for engineers to switch jobs every two- to-three years in hopes of finding employment that won’t burn them out.

How to Recognize DevOps Burnout

How do you realize that you are suffering from burnout? It’s like the famous description of a frog in boiling water. The frog only knows it’s going to die when it’s too late. Similarly, the engineer only knows they are suffering burnout when they have either burnt bridges or broken friendships or flamed out. In fact the culture change from adopting DevOps can lead to burnout in and of itself as engineers try to incorporate the lessons and teachings of DevOps. While the workplace itself might have adopted this new culture, the employees are not quite there yet.

Is It Me or Is It You?

Burnout is a symptom of the institution as much as it is of the engineer’s ego trying to take too much on. Engineers are famous for their fear of the “Impostor Syndrome” where they fear they are the least intelligent person on the team and they are just one step away from exposing themselves.

In an article from Business Insider, “Impostor Syndrome” was described as being like the boogie man: “Open the closet, turn on the lights, look around, and you see that nothing is there. But it never goes away entirely. It’s just temporarily gone, and you’ll have to expose it again.” And even though the boogie man is shown not to exist, the Impostor Syndrome feeling continues.

As a coping mechanism, engineers spend a significant amount of time compensating rather than reaching out for help. Engineers seem to delude themselves into thinking that the long hours are only a problem with their company. But really the problem extends to all companies.

Expect the Unexpected With Less Stress

Using OnPage, management can better address the arrival of high-priority alerts. High-priority alerts can be sent directly to the on-call engineer’s OnPage app on their smartphone. All critical notifications bypass the silent switch on mobile. No more hoping that the engineer reads the email or hears the arrival of a text message or a phone call.

For overnight on-call shifts, the engineer can be assured that they will be woken up by the prominent OnPage alert which continues for eight hours until the message is read. Low-priority alerts can be directed to the engineer’s OnPage account via a low-priority alert or email. By not having to constantly check email or SMS for critical alert messages, the engineer can alleviate significant amount of stress. The engineer knows they will receive the critical message.

Better Management of Work Environments

What responsibility does management hold in mitigating burnout? The following are actionable points management can incorporate and help DevOps engineers incorporate as well:

1. Employees should set boundaries for themselves: By practicing better pacing, employees know when to say “no” to new work.
2. Fibonacci storytelling: Points are assigned to a task based on the amount of time the whole team thinks the task will take based on the team’s velocity. When the team has taken on projects whose total point value equals the team’s maximum velocity, they stop taking on more items.
3. Mentoring: Make it easier for engineers to ask questions and have an adequate support structure. This type of program will help mitigate the feeling of “Impostor Syndrome.”
4. Pairing: Work in teams on challenging projects so engineers don’t feel the weight of an entire challenge on their shoulders alone.
5. Make the unplanned predictable: Use OnPage fail-safe scheduling to create a predictable on-call plan. Engineer(s) know they will immediately be apprised when a high-priority event has occurred.
6. Brain dumping: At the end of the day, write tasks that remain to be done. Productivity is truly aided by coming to work with a fresh brain.
7. Make management responsive: Managers need to show they are listening and responsive to engineer issues. Managers need to show they are willing to be accountable and when engineers say they cannot handle more work, managers should listen.
8. 9-5 needs to be flexible: Teams need flexibility to change their mode of working. If an engineer has worked for 12-13 hours to get a project done, he or she should be able to take the following day more leisurely or off entirely.
9. Hire more: Teams need visibility into the work pipeline so they can see how much work is awaiting them. If work is continually added after a board has been agreed to, then management needs to consider hiring more people.
10. Avoid email: Additional work should not come through email. Keep work structured and on tickets.
11. Be disciplined about time: Use the last hour of the day for personal development or small projects. Rather than finding yourself at 5 p.m. in the middle of fixing a bug or a project, start winding down at 4 p.m. so that when 5 or 5:30 p.m. comes around, you are ready to leave.

Conclusion

Discussing these 11 points would be the basis for a great, brown bag lunch between management and employees. The discussion would allow DevOps engineers to work with their managers so that each party could have a better understanding of the requirements for their team to be successful. Perhaps the team needs a better alerting technology along with a better way to prioritize alerts. A brown bag lunch would be a great place to start.

Let OnPage show you how our cloud-based, critical alerting platform can be an important tool in managing and controlling engineer burnout. Schedule a demonstration today!

Updated: Feb. 8th, 2022