Mental Health at Work: 4 management failures that turn overload into absence

Mental health at work is often treated like a side program, as if overload were a personal weakness instead of a decision problem. That is the wrong model, because the moment work keeps expanding faster than capacity, the operation starts borrowing from sleep, attention, and judgment, and the bill shows up later as absence, conflict, or quiet disengagement.

Across 25+ years in multinational EHS and more than 250 cultural transformation projects in 30+ countries, Andreza Araujo has seen the same pattern repeat. The organization usually waits until distress is visible, then asks people to be more resilient, although the real fix sits earlier, in workload design, priority setting, and the quality of the management decision. In A Ilusão da Conformidade ("The Illusion of Compliance"), she shows why a tidy process can still hide a fragile reality, and in Muito Além do Zero ("Far Beyond Zero"), she argues that good numbers do not prove the system is healthy.

This article is for line managers, HR partners, and site leaders who need a practical way to stop overload before it becomes absence. If you want the operational version of the problem, start with How to run a workload-risk review in 8 steps, because workload only changes when someone makes the pressure visible and names the owner.

Why does overload become a management problem before it becomes a health case?

Overload becomes a management problem when the work itself keeps asking for more time than the system gives back. That is not a therapy issue. It is a design issue, because people can absorb short pressure, but they cannot absorb a permanent mismatch between demand, capacity, and decision rights without paying for it somewhere else.

ISO 45003 exists for that exact reason. Psychosocial risk is part of occupational health, not an optional extra, and it belongs in the same conversation as workload, supervision, autonomy, conflict, and recovery time. If the team has no room to reset, the organization is no longer managing a healthy operating rhythm.

The real question is not whether people can cope for a week. The real question is whether the operating model keeps asking them to cope indefinitely. That is the difference between temporary pressure and a structural exposure that will surface later as absence, turnover, or error.

Failure 1: nobody owns the decision that created the overload

Many leaders talk about workload as if it arrived from nowhere, but overload usually has a name attached to it. It is a deadline that was accepted too early, a project scope that was expanded without a tradeoff, a staffing gap that was normalized, or a meeting culture that kept stealing recovery time from the same people every week.

When no one owns the decision, everyone owns the consequence, and that is where the damage starts. The team absorbs the pressure, the manager absorbs the frustration, and HR gets called only after the symptom has already hardened. A better response starts with decision rights, because someone has to say what moves, what stops, and what cannot be added without removing something else.

If you need the wider control logic, the article on How to build a safety decision trail in 30 days shows the same principle in another setting. The organization gets safer when decisions are visible, named, and reviewable, not when they are buried inside a calendar invite or a vague sense of urgency.

Failure 2: leaders wait for distress instead of reading the workload signals

By the time someone asks for help, the earliest signals have usually been present for weeks. The clues are practical and ordinary. Overtime keeps rising. Breaks become shorter. Task switching grows. People answer messages late at night because they feel they have no margin during the day. Rework increases. Small conflicts become sharper because nobody has enough mental room to absorb friction.

The manager who waits for an employee to break down has already missed the operational signal. A better manager watches the work pattern before the person turns it into a health case. That means asking where the pressure comes from, which tasks keep spilling past the shift, which priorities keep changing, and which meetings are taking more energy than they return.

The article on New Line Manager in 90 Days: What to Do Before Workload Breaks the Team is useful here because a new manager often sees the signal before the culture tells them how to ignore it. Early sight is a gift only when the manager acts on it.

Failure 3: wellness language replaces work redesign

Organizations often answer overload with good intentions and weak controls. They add a poster, a resilience session, a webinar, or an employee assistance message, then call the problem addressed. Those tools can help, but they do not change the source of the pressure, which means the underlying exposure stays in place while the language around it gets softer.

That is the trap Andreza Araujo describes in Muito Além do Zero ("Far Beyond Zero"). A nice number, a neat program, or a polished message can hide a condition that still needs intervention. Mental health support matters, but support is not a substitute for workload relief, clearer priorities, fewer conflicting demands, and a supervisor who knows what to stop.

If you want the version of this problem focused on support delay, see Mental Health at Work: 5 Failures That Turn Support Into Delay. The point is simple. Support helps people recover. Work redesign prevents the injury from growing in the first place.

Failure 4: the dashboard measures absence after the damage

Absence is a lagging signal. So are resignations, medical referrals, and formal complaints. They matter, but they arrive after the operating pattern has already gone wrong. A dashboard that only reports those outcomes is reading the rearview mirror and calling it prevention.

A better dashboard watches the live controls that shape mental load. Overtime is one. Break loss is another. Task churn matters, because a person who is forced to restart work ten times a day burns energy faster than someone who can finish a sequence. Span of control matters too, because a supervisor with too many direct reports will default to reaction instead of coaching.

During the PepsiCo South America period, where the accident ratio fell 50% in six months, the lesson was that results changed when leaders changed the operating rhythm. The same logic applies here. If the rhythm keeps draining the same people, the absence number will move later, not sooner.

The article on Safety Dashboards: 5 Failures That Hide Critical Risk explains why the wrong metric creates false comfort, and Safety Indicators Explained: 4 Types Leaders Should Not Mix helps separate what is live from what is only historical.

What should a line manager change in the next 7 days?

The first move is to make the load explicit. A line manager should write down the top priorities for the week, the tasks that can slip, and the tasks that cannot continue to expand without a tradeoff. That is not bureaucracy. It is how the manager protects the team from hidden overload.

The second move is to stop pretending that every request has equal weight. If everything is urgent, nothing is prioritized, and the team will finish the week exhausted while still carrying unfinished work. The manager should decide which meetings can be dropped, which messages can wait, and which deadlines need a fresh conversation with the person who created them.

The third move is to look at recovery, not just output. If the same people are repeatedly staying late, skipping breaks, or carrying unfinished tasks home mentally, the work is already exceeding capacity. The manager does not need a speech. The manager needs a correction to the load.

The fourth move is to ask for the signal that people do not volunteer first. Ask which task is stealing sleep, which recurring interruption is creating the most frustration, and which routine makes the shift feel longer than it should. The answers are often specific, and that specificity is what turns concern into action.

What should HR own and what should it refuse to own?

HR should own the process that keeps the issue visible. That includes intake, triage, confidentiality, manager coaching, accommodation pathways, and pattern review. HR should also keep the language clean, because mental health work gets distorted quickly when the organization starts mixing clinical care, performance management, and workload control as if they were the same thing.

HR should refuse to own the work allocation itself. It should not be the person who decides which deadline moves, which project pauses, or which team absorbs the extra task. Those decisions belong to line leadership, because only the line manager can rebalance the actual work and the actual schedule.

That boundary matters because culture is built in repeated decisions. In Safety Culture: From Theory to Practice, Andreza Araujo shows that leadership is visible in the routine, not the slogan. When HR owns the process and line leaders own the load, the system can still fail, but it fails visibly, which gives the organization a chance to fix it before the damage spreads.

When does overload become a business risk?

Overload becomes a business risk when it starts to reshape the quality of decisions. People miss steps. Handover quality drops. Conflicts take longer to settle. Supervisors become reactive. The organization then pays twice, first in performance loss and later in the cost of replacing people, fixing errors, or restoring trust.

This is why mental health at work should not be treated as a soft topic. It affects continuity, attention, retention, supervision, and error recovery. A leader who ignores that link usually ends up managing the cost later, only without the people who were carrying the work when the pressure was still invisible.

If the operation wants a practical starting point, the best next move is to run the workload review, name the owner of the overloaded process, and reset the weekly decision trail. That sequence will not solve every problem, but it will show whether the team has a real control system or only a sympathy circuit.

Conclusion

Mental health at work improves when leaders change the work, not when they merely ask people to endure more. The four failures that matter most are simple to name: nobody owns the overload, leaders wait too long to read the signals, wellness language replaces redesign, and the dashboard measures absence after the damage.

If you want the practical version of that fix, start with How to run a workload-risk review in 8 steps and then bring the issue into the line manager rhythm. If the team still needs a broader view of leadership and culture, Andreza Araujo's books and advisory work at andrezaaraujo.com give the next layer of control.