Why some of the most important work in an organization never appears on a dashboard.
– Chris McLean
The system runs.
The org chart? It’s clear.
Meetings happen when they’re supposed to.
And yet, the real problems only surface inside conversations, after the meeting ends, or when the right person quietly steps in to keep everything from going sideways.
That’s usually a sign that the organization is running on invisible labour.
Some of the most important work in any organization is never formally assigned, tracked, or recognized. It happens in the gaps between roles, processes, and reporting lines. The longer it goes unnamed, the more essential it becomes.
What is unspoken work?
Unspoken work is the effort that keeps a team functioning, even though it does not appear in a project plan, KPI dashboard, or formal role description.
It often looks like:
Calming people down after a tense meeting
Translating between leaders, teams, or personalities
Smoothing over friction no one has addressed directly
Carrying context and institutional memory others rely on
Holding together trust, cohesion, and momentum when the structure itself is not doing that job
It is often the human duct tape holding a brittle system together. Because it is untracked, it tends to fall on the same people over and over again: the dependable one, the emotionally attuned one, the person who “just handles it,” the team member others instinctively turn to when things start to fray.
In many organizations, this burden falls disproportionately on women, junior staff, and people with strong relational intelligence.
They were never formally assigned this responsibility. The system simply kept handing it to them.
The pattern underneath the pattern
If you want to understand what is really holding an organization together, do not just examine the workflows. Look at who is absorbing the tension those workflows create.
Whenever an organization seems surprisingly functional despite broken structures, misalignment, or chronic friction, it’s worth asking:
Who is carrying the strain so the system does not have to confront it?
These are load-bearing people.
They are often:
Doing essential work invisibly
Holding cultural and relational continuity
Compensating for weak management, unclear roles, or poor structural design
Receiving little recognition for the weight they carry
And eventually, one of three things happens:
They burn out.
They disengage.
Or they leave.
When they do, leaders are often surprised by how much more disappeared than a job description could explain. That’s because the system was never as stable as it looked. Someone was absorbing the instability on its behalf.
A familiar organizational failure
Many leaders assume a functional-looking team must be supported by a healthy structure.
Not always.
Sometimes the structure is weak, but a few highly capable people are compensating for it so effectively that the weakness remains hidden. The organization mistakes personal buffering for systemic health.
That works right up until it does not.
When one of those people steps away, the loss is often described in vague language:
“Things just haven’t felt the same.”
“They were such a stabilizing presence.”
“We lost more than we realized.”
Those statements are usually true. They are also diagnostic.
They point to work the organization depended on but never named.
A simple audit
If you want to identify unspoken work inside your organization, start with a few direct questions:
Who do people go to when something feels off?
Who helps restore calm after difficult leadership conversations?
Who is informally translating, mediating, or reconnecting people?
Who is compensating for bad systems with emotional or relational labor?
What would quietly start breaking down if that person stopped doing the extra work?
You won’t be able to eliminate all of this labour. Some relational work is part of healthy organizations. But leaders should be very wary when essential organizational functioning depends on work that is invisible, unevenly distributed, and unsupported.
Signs you are seeing it
A few common indicators:
One person keeps stepping in “just to keep things moving”
The room relaxes when a certain person joins the call
Someone is described as “indispensable,” but no one can clearly explain why
A team loses cohesion after a departure in ways that exceed the official role
Conflict stays low, but only because someone is constantly absorbing it before it surfaces
These are not just personality dynamics. They are structural signals.
What leaders should do
1. Name it
If the work is real, it should be discussable. Bringing it into the open is the first step toward dealing with it responsibly.
2. Recognize it properly
Do not reduce essential relational labour to vague praise about being a “team player.” If someone is carrying meaningful organizational weight, that should be reflected in how their contribution is understood and valued.
3. Distribute it
Do not let invisible labour become the default tax paid by your most capable or emotionally intelligent people. Healthy organizations spread relational and cultural responsibility more deliberately.
4. Redesign around the need
The deeper question is not just who is carrying the load. It is why the load exists in the first place. What weak process, unclear decision pathway, leadership habit, or structural gap is creating this need for constant human buffering?
Do not just celebrate the load-bearing person. Fix the conditions that made them necessary.
Final thought
Some of the most important work in an organization does not show up in the metrics. It shows up in trust, cohesion, translation, timing, and the person everyone relies on when things start to fray.
If that person leaves and the whole atmosphere shifts, that’s not just a personnel issue.
It is a signal.
Your organization may not be over-reliant on a person.
It may be over-reliant on silence.
