The Work That Doesn't Have a Name
The Invisible Load
Every organisation runs on two kinds of work. The first kind is visible: the deliverables, the projects, the outputs that have names and owners and success metrics. The second kind is harder to see: the work of maintaining the conditions in which the visible work is possible. The conversations that prevent conflicts from becoming crises. The context that gets handed to new people without being formally written anywhere. The relationships that hold difficult collaborations together. The attention that catches problems before they become visible enough to require management.
This second kind of work is often the most load-bearing and the least recognised. It does not appear in project tracking systems. It is not captured in performance reviews. It generates no direct outputs that can be pointed to and celebrated. And yet, in its absence, the visible work degrades — relationships break down, context is lost, conflicts escalate, new people fail to integrate, and the organisation pays costs that no one can trace to their actual source.
Who Carries the Invisible Load
Invisible work is not distributed randomly across an organisation. It tends to concentrate in specific people — people who are temperamentally oriented toward the relational and contextual dimensions of work, who are trusted by many different people and therefore positioned to hold information and relationships across silos, who notice what is happening in the organisation at a level that precedes formal reporting. These people are often not the most senior, not the most visible, and not the most formally powerful. But they are often among the most operationally essential.
When these people leave, organisations often discover their importance through the gap they leave. The informal coordination that used to happen stops. The context that used to be held disperses. The early warning signals that used to surface through their attention now arrive as visible crises instead. The exit interview might say something generic about career development. The actual cost of the departure is rarely quantified — because the work that was lost was never quantified.
The Measurement Problem
Invisible work resists measurement by design. The nature of much of it is preventive — it stops things from going wrong. And the absence of things going wrong is not a measurable output. It is an absence. Organisations that measure only outputs cannot see it. They can see the outputs that exist. They cannot see the problems that do not exist because someone's invisible work prevented them. This measurement gap means that invisible work is systematically undervalued in performance assessments, compensation decisions, and development conversations.
The people who carry this load often know they are carrying it. What they often do not know is whether the organisation values it. And when the signals they receive suggest it does not — when their visible outputs are thin relative to peers who are generating outputs but not maintaining the conditions for output — the invisible work becomes harder to sustain. Not because they stop caring. Because sustained investment in unacknowledged work, over time, is simply not viable.
Making the Invisible Visible
The first step in valuing invisible work is naming it. This is not as simple as it sounds, because the work does not have established vocabulary. But it begins with the practice of asking different questions in performance conversations: not only "what did you deliver" but "what did you prevent, coordinate, or enable for others?" Not only "what were your outputs" but "what were the conditions for others' outputs that you helped create?"
These questions invite people to name the work they have been doing without a name for it. And the act of naming often produces recognition — both for the person describing it and for the person receiving the description — that something genuinely important was happening, something worth valuing, something that deserves to be in the conversation about contribution and reward.
The Operational Truth
Every organisation that has tried to reduce headcount in areas where invisible work was being done has encountered the same discovery: the work was not as invisible as it appeared. Its absence created costs that were immediately and sometimes dramatically visible. The lesson from those experiences, when organisations are willing to learn it, is that the work that has no name is often the work that most deserves one.
Request Access at planets9.com