The overtime nobody sees: preventing burnout on a support team under pressure

To prevent burnout on a team doing overtime you have to do three things: make the effort visible and recognize it concretely (for example, letting people choose between future rest or pay), explain the plan to remove the cause to the team, and prioritize lifting the load instead of asking them to keep absorbing it. In this case, an automation removed the extra work and the team didn't carry the wear into the next quarter.

The problem: out-of-contract work, absorbed as if it were normal

In a banking operation I ran, a client-side headcount reduction left us over our capacity. Between 30 and 40% of incoming cases were user-configuration requests: initial onboarding, office changes, approval-level changes. That work wasn't even in the original contract scope.

Each request demanded close to half an FTE of manual work during the first five or six days. The team was working real overtime to keep up.

The risk of it becoming normal

Overtime rarely starts as a problem. It starts as a one-off push, a "let's just get this out". The risk is that, week after week, it becomes part of the landscape: invisible to those not doing it and exhausting for those who are. I didn't want that to happen to my team.

Pro Tip #1 — Make the extra effort visible before it normalizes. If nobody names the overtime, the team assumes it's expected, and burnout sets in without anyone deciding it.

Recognize, listen, and explain

I recognized the effort concretely: each person could choose between banking that time as future rest, once we stabilized the project or transferred the work to the client, or having it paid out directly if they preferred the income.

Pro Tip #2 — Let people choose how the effort is compensated: time or money. Not everyone needs the same thing at the same moment; the choice itself is a form of respect.

At the same time, I held periodic feedback sessions with the team. They served to hear how we could make diagnosis easier and reduce friction in the rest of the queue, but just as important: to make sure they knew what we were doing to resolve the root cause, and to open a space where they could tell me directly if they felt overloaded.

Pro Tip #3 — Tell the team the plan to get out, not just the plan to endure. Pressure is tolerated better when you know it has an exit date and who's working on it.

Lift the load, don't ask them to absorb it

In parallel, I prioritized building the automation that would remove the extra load, instead of asking the team to keep absorbing it longer. When that automation was ready, overtime dropped, and the team didn't carry that wear into the following quarter.

Pro Tip #4 — The best measure against burnout is removing the cause, not compensating for it forever. Recognizing the effort is necessary; eliminating the work that causes it is what resolves it.

What remains from this story

A team under pressure doesn't just need a technical solution: it needs someone to see the effort, recognize it concretely, and explain how they're going to get out of it. The automation solved the problem; what kept the team from burning out along the way was not letting the effort become invisible.

Frequently asked questions

How do you detect that overtime is becoming normalized? When it stops being mentioned as something exceptional and the team assumes it's expected. If nobody names it, it has already become part of the landscape.

Is it better to compensate overtime with time off or with pay? It depends on the person. Letting each one choose recognizes the effort and respects what each needs at that moment.

Does compensating overtime prevent burnout? Not on its own. Compensation recognizes the effort; what prevents burnout is eliminating the cause of the overload.