Why HR burnout is a design problem – not resilience
HR burnout is usually talked about as a capacity issue.
Too much work.
Too many demands.
Too little recovery.
And I understand why that framing exists. It comes from concern. From wanting to help. From recognising that HR carries a lot.
But in my experience, and particularly when I was leading HR, burnout didn’t feel like a personal capacity problem at all. It felt like carrying something that didn’t belong to me, but also couldn’t be put down.
Seen this way, burnout isn’t a weakness.
It’s a signal from the system.
HR sits in a difficult place. Between leadership intent and lived reality. Between what is meant to happen and what actually lands with people. When decisions hesitate or authority thins, that tension doesn’t disappear, it moves. And very often, it moves to HR.
Not because HR wants it.
But because HR can hold it.
This doesn’t happen dramatically.
HR absorbs.
HR steadies.
HR translates.
Conversations are picked up. Consequences are managed. People stay engaged. Work keeps moving. From the outside, it looks like competence. From the inside, it can feel like constantly adjusting your grip on something heavy, without ever quite being able to put it down.
At first, this can feel purposeful.
There were moments when I consciously chose to absorb shock. Not to protect poor leadership, but to prevent fracture. To create enough stability to understand what the system was no longer able to hold. In those moments, absorbing pressure felt like leadership.
But what starts as a deliberate choice can quietly become a permanent expectation.
Over time, this way of working becomes normal. HR isn’t just supporting the system – it’s compensating for it. And because things continue to function, the deeper design problem stays largely unexamined.
This is where burnout really begins.
Not because HR lacks resilience or commitment, but because it is carrying ongoing pressure without the authority to resolve its source. Decisions still happen, but ownership is blurred. Tension is managed carefully rather than addressed directly.
And because HR is good at this, because it cares, notices, and adjusts, the organisation adapts around it.
Issues get routed to HR rather than owned where they originate. Difficult conversations are softened. Decisions arrive already filtered. What looks like responsiveness is often the system quietly learning that it doesn’t need to change.
Burnout doesn’t arrive suddenly.
First, something else shifts.
Clarity fades a little. Meetings end without real resolution. Energy drains in small, hard-to-name ways. HR tends to notice this early, in tone, in behaviour, in the quiet recalibrations people make just to keep things moving.
By the time exhaustion becomes visible, the system has often been relying on HR to compensate for some time.
This is why resilience narratives can feel both well-meaning and unsatisfying.
They place the focus on coping rather than conditions. They suggest the answer is more support for HR, rather than asking why HR has been carrying so much in the first place.
Burnout, seen this way, isn’t a call for HR to toughen up or step back.
It’s a signal that HR has been doing a great deal, often quietly, often skilfully, for longer than the system should reasonably expect.
This isn’t about blame.
Leaders are often well-intentioned. HR is often deeply capable. The issue isn’t effort – it’s design.
When pressure has nowhere appropriate to go, it settles where it can be held safely. HR becomes the shock absorber. And absorbing shock can be leadership – ethical, intentional, and necessary in moments of distortion.
But when that becomes permanent, it extracts a cost.
Burnout is that cost.
Not because HR lacks strength, but because no system can offload pressure indefinitely without redesign. Eventually, something has to give.
Burnout isn’t asking HR to be more resilient.
It’s the organisation quietly revealing that the way pressure is being held is no longer sustainable.
And that’s a signal worth listening to – not with urgency or judgement, but with honesty about what the system itself is asking for next.
