We Don't Burn Out Overnight: Why Capability Isn't the Same as Capacity
Why organisations need to stop mistaking capability for capacity
If you ask someone why they burned out, they'll often tell you about the final straw.
It was the restructuring.
The acquisition.
The impossible deadline.
The difficult manager.
The project that finally pushed them over the edge.
I don't think burnout works like that.
Looking back on my own experience, I can't point to a single moment where everything became too much. Instead, I see something far more subtle. Burnout wasn't an event; it was a pattern. It developed so gradually that I didn't notice it happening until I'd already been living with it for years.
That's one of the reasons I wanted to write this article.
When we talk about burnout, we often focus on resilience, wellbeing initiatives or encouraging people to speak up sooner. Those things matter, but I think they risk distracting us from a more uncomfortable question.
What if the way we identify high performers is part of the problem?

Image created using generative AI to illustrate the concepts discussed in this article.
For most of my career, I was the person who could be relied upon.
I worked in Human Resources, eventually leading the function for a growing organisation while also serving as President of an 82-unit co-op in Harlem. Both roles carried significant responsibility, and both involved helping people navigate uncertainty, conflict and change. I enjoyed solving problems. I liked bringing order to complexity. When something wasn't working, my instinct was to understand it, fix it and leave it better than I found it.
Those qualities served me well.
They also made me an obvious person to ask whenever something new came along.
The company I worked for was acquired. Then came another acquisition. We implemented Workday, which transformed the way the organisation managed its people processes. Alongside that were immigration cases, employee relations, operational challenges and all the day-to-day realities of leading an HR function. Outside work, COVID dramatically changed what it meant to lead a residential community. Residents were looking to the board for reassurance and practical leadership during one of the most uncertain periods most of us had ever experienced.
If you look at each responsibility individually, none of them seems unreasonable. In fact, every one of them had a perfectly sensible justification. The business needed support through change. The board needed stability. People needed someone to help them navigate uncertainty.
The problem wasn't any single responsibility.
The problem was that nothing ever came off my plate.

Image created using generative AI to illustrate the concepts discussed in this article.
Looking back now, I don't think I was being promoted because I had more capacity.
I was being given more because I had demonstrated capability.
Those two things are not the same.
Organisations are generally very good at recognising people who consistently deliver. They notice the people who remain calm during a crisis, who willingly take ownership and who quietly solve problems before they become visible to everyone else. Those people become trusted. They become dependable.
Eventually, they become indispensable.
We often celebrate that word as though it's the highest compliment an employee can receive.
I'm no longer convinced it is.
When an organisation says, "Only Lois knows how to do that," I think leaders should immediately ask themselves another question.
Why does only Lois know how to do that?
Sometimes the answer is expertise.
More often, it's organisational debt.
Knowledge hasn't been shared. Processes haven't been documented. Responsibilities haven't been distributed. One capable person has slowly become the place where every gap in the system eventually lands.
From the outside, that looks like exceptional performance.
From the inside, it feels very different.
For years, I thought my problem was that I had too much work.
The research has helped me understand that what I was experiencing was much more complicated than that.
Christopher Wickens' work on attention and mental workload argues that our cognitive resources are finite. Different tasks compete for different forms of attention, and eventually the brain reaches a point where it cannot continue processing everything simultaneously. At that stage, we don't simply "work harder." We begin switching between tasks, delaying them or unconsciously shedding them altogether. The issue isn't motivation. It's capacity.
Reading that research was one of those moments where something clicked into place.
I hadn't simply been doing more work than everyone else.
I had been moving between completely different kinds of work, each demanding a different part of my brain. One conversation might involve immigration legislation. The next involved organisational design. Then a sensitive employee issue. Then a technology implementation. Then governance. Then a resident emergency.
Each transition carried a cognitive cost.
None of that showed up on my calendar.
One of the biggest misconceptions about burnout is that it announces itself dramatically.
Mine didn't.
I didn't suddenly become unable to work. I didn't wake up one morning and realise I couldn't get out of bed. Instead, I experienced repeated cycles of burnout over several years. I'd hit a wall, recover just enough to function again and then return to exactly the same conditions that had created the problem in the first place.
Each recovery restored my ability to keep going.
It didn't remove the reasons I had stopped.
The moment that frightened me most wasn't actually the exhaustion.
It was the compassion fatigue.
Anyone who knows me knows that people have always been at the centre of how I see the world. Whether I was working in HR, leading a community or building Unlabelled & Limitless, my starting point has always been the same: how do we create environments where people can do their best work?
When I realised people had started to feel like one more problem that needed solving, I knew something fundamental had changed. I hadn't stopped caring. I simply had so little emotional capacity left that even empathy had become difficult to access.
That wasn't who I wanted to become.
The more research I read, the more I realised my experience wasn't unusual.

Image created using generative AI to illustrate the concepts discussed in this article.
The Neurodiversity in Business report produced with Birkbeck University argues that organisations still rely too heavily on individual coping rather than systemic inclusion.
That phrase has stayed with me ever since I first read it.
Individual coping.
How much of modern work depends on capable people quietly compensating for systems that don't work particularly well?
Remembering information because processes are inconsistent.
Filling communication gaps.
Managing relationships that should have been managed earlier.
Holding institutional knowledge inside one person's head because nobody has had time to document it.
From the organisation's perspective, everything appears to be working.
From the employee's perspective, an enormous amount of invisible effort is required just to keep ordinary work moving.
Eventually, that invisible effort becomes normal.
That's dangerous because organisations tend to reward the outcome, not recognise the cost.

Image created using generative AI to illustrate the concepts discussed in this article.
When we founded Unlabelled & Limitless, we weren't trying to build another consultancy.
We were trying to answer a question.
What would happen if we designed an organisation around what we've learned rather than around what we've inherited?
That's why we wrote an ethics handbook before we had a large team. It's why we talk openly about workload, psychological safety and capacity. It's why we've built mechanisms for stepping back rather than celebrating people who continually push through exhaustion. Most importantly, it's why we've challenged one of my own assumptions about leadership.
For years, I believed servant leadership meant removing barriers for everyone else.
I still believe leaders should remove barriers.
I no longer believe they should absorb them.
There's an important difference.
When a leader redesigns a process, redistributes work or removes unnecessary friction, they've strengthened the system.
When a leader quietly takes on more work themselves so everyone else can continue, they've strengthened nothing. They've simply become another single point of failure.
I know, because I spent years doing exactly that.
Burnout coaching didn't simply help me return to work.
It helped me return to my life.
Over time, work had quietly displaced almost everything else that mattered to me. Friends, family, hobbies and simple moments of joy had gradually disappeared beneath responsibility. I hadn't consciously chosen that trade-off. It had happened one reasonable decision at a time.
Recovery wasn't about becoming productive again.
It was about becoming myself again.
That experience fundamentally changed how I think about organisational success.
Yes, results matter.
Performance matters.
Financial sustainability matters.
But if the people producing those results no longer have enough of themselves left to enjoy the lives they're working so hard to support, I think we should question whether we've designed success properly in the first place.
Perhaps that's the lesson I hope organisations take away.
The people you describe as your highest performers may also be carrying the greatest amount of invisible organisational debt. They may be translating confusion into clarity, absorbing uncertainty, compensating for broken processes and protecting everyone else from friction you've never realised exists.
If that's true, the answer isn't to teach those people to become even more resilient.
The answer is to ask why your organisation needs extraordinary coping simply to achieve ordinary work.
Because capability isn't the same thing as capacity.
And the sooner we start designing organisations that recognise the difference, the less likely we are to lose the very people we've spent years relying on.

.png)



Comments