The Informal Load-Bearers
Who They Are, What They Carry, What Leaves When They Do.
There is a category of organizational work that never appears in a job description.
It is not informal in the sense of being casual or unimportant. It is informal in the sense that it exists outside the official architecture of roles, accountabilities, and deliverables. It is the work of holding the connective tissue together. Knowing who to call when the process breaks down. Absorbing the anxiety of a team in the middle of a transition so that it does not spill into the meeting. Translating what leadership actually meant when what leadership said landed badly. Bridging two departments that do not naturally communicate and making that bridge feel effortless to everyone who crosses it.
The people who do this work are rarely described as doing it. They are often described as being great to work with, or having good instincts, or being someone people go to. These are ways of pointing at the work without naming it. The work does not have an official name because the organization has never needed to name it. It has just always been done.
Until it is not.
Who they are
The informal load-bearers in an organization are not always the same person. The work distributes itself differently depending on team structure, tenure, personality, and the particular demands of a given moment. But there are patterns.
They tend to have institutional memory that spans more than their own role. They know why certain decisions were made three years ago, and they know why those decisions were made in that way rather than some other way, and they know who was in the room when it happened. That context does not live anywhere official. It lives in them.
They tend to be the people other people go to when something is not working through the normal channels. Not because they have authority over those channels, but because they know how to navigate around them, or know who to call to get something unstuck, or know when to escalate and when to wait. This knowledge was acquired through years of paying attention and is not transferable through documentation.
They tend to absorb emotional weight on behalf of the team. When a manager is unavailable, or when the official response to a difficult situation is inadequate, the informal load-bearer is the person who sits with colleagues who are struggling. They do not have a formal role in that conversation. They are just there, and they are steady, and that steadiness costs them something.
They are disproportionately represented among the people described as cultural carriers. They know the unspoken norms. They model the behaviors that are valued without making a show of it. They integrate new people not through a formal buddy program but through proximity and generosity of time.
What they carry
The load is not evenly distributed, and the people carrying the most of it are often the last to say so.
Part of what makes informal load-bearing invisible is that the people who do it tend to be good at making it look effortless. The bridge they built between two teams looks like those two teams simply get along. The translation they provided between a difficult announcement and a demoralized workforce looks like that workforce simply handled it well. The institutional knowledge they hold looks like, from the outside, just knowing things.
What is actually happening is labor. Cognitive labor: tracking the social dynamics of the organization, anticipating where friction will emerge, staying current on the unofficial version of events alongside the official one. Emotional labor: holding other people's distress without passing it on, staying regulated when the people around them are not, being available in a sustained way for conversations that are genuinely hard. Relational labor: maintaining trust relationships across the organization that took years to build and require ongoing investment to keep.
None of this is measured. None of it is formally recognized. In most performance review systems, it is not even visible as a category of contribution. It shows up, sometimes, in the soft language of peer feedback — great to work with, always available, keeps the team grounded — in ways that read as complimentary but do not translate into compensation, advancement, or formal acknowledgment.
This is the architecture of how organizations use people without knowing they are using them.
What leaves when they do
When an informal load-bearer leaves an organization, the immediate visible gap is almost always smaller than the actual gap.
What is visible is a role. A set of responsibilities. A position on an org chart that will need to be backfilled. The organization responds to what is visible: it posts the job, writes a transition plan, schedules knowledge transfer sessions. This is appropriate. It is also insufficient.
What is not visible, and what the organization will discover gradually and often painfully, is everything that was held informally. The person who knew that the two teams needed a go-between does not document that they were the go-between. The person who absorbed the team's anxiety during the last restructuring does not write up the methodology they used. The person who held the institutional memory of why a particular process works the way it does may not know that they are the only one who holds it, because no one ever told them they were.
The loss reveals itself in accumulation. The process that used to run smoothly starts producing friction. The two teams that seemed to collaborate well start missing things. The new hire who should have been integrated by now still seems to not quite understand how things work. The meeting that used to end with a clear outcome keeps ending inconclusively. None of these are dramatic failures. They are quiet degradations, each one explicable on its own terms, hard to trace back to a common source.
The common source is that the person who was making them not happen is no longer there.
What to do about it
The standard response to this problem, when organizations recognize it at all, is to try to make the informal formal. Document the knowledge. Build the processes. Create the roles. Some of this is useful. But it misses something.
Informal load-bearing is not just a set of tasks that can be reassigned. It is a set of relationships, accumulated over time, that allow the work to happen. The knowledge is relational as much as it is informational. The reason the informal load-bearer could call someone and get something unstuck is not that they knew the right process. It is that they had a relationship with a person who trusted them enough to move quickly. That does not transfer through documentation.
What organizations can do is name the work before it leaves. Not just as an exercise in retention, though retention matters. As an exercise in organizational honesty about what is actually holding things together. If the answer to "who would we miss most if they left tomorrow" is a person whose job description does not begin to capture why, that is information worth acting on.
It means asking: what is this person actually doing that is keeping things functional? Who would they take with them, relationally, if they left? What institutional knowledge do they hold that exists nowhere else? What social labor are they performing that would otherwise fall to no one?
The people who carry the most informal load are often the people who would be least likely to announce that they are considering leaving before they have already decided. The warning signs are quiet. The departure, when it comes, is often described as a surprise.
It should not be.
The work that is never formally valued
There is something uncomfortable in the observation that organizations systematically rely on informal load-bearing without compensating for it, without acknowledging it, and often without even recognizing it is happening. The discomfort is appropriate.
The people most likely to do this work are not randomly distributed. They tend to be people who have been socialized to make themselves useful, to absorb friction rather than generate it, to invest in relationships and environments even when that investment is not formally rewarded. That is a pattern worth looking at honestly.
Organizations that want to do better by these people have to start by seeing them clearly. Not as people who are great to work with, but as people who are doing essential work that the organization has decided not to formally account for. Naming that honestly is where it starts.
The quiet architects of your organization are holding more than you know. The question is whether you will figure that out before or after they are gone.
