If your organization has a person or a function whose value only becomes visible when they leave, this piece is for you. What you have is not a compensation problem or a recognition problem. It is the specific structural condition of enabling work, and the fix requires you to make visible what the system is designed to hide.
When a climber summits a significant peak, there is almost always a photograph.
The climber at the top, arms raised or not, the view behind them, the moment of achievement documented. This photograph exists in every summit archive, every expedition report. It is the visual record of what happened.
The belayer is not in the photograph.
The belayer, the person managing the rope below, maintaining the anchor, holding the system that made the ascent possible, was not on the summit. They were at the belay station, doing the unglamorous, technically demanding, continuously attentive work that the climb required. Their competence was load-bearing. Their attention kept the lead climber safe. Their specific technical skill was the difference between a successful ascent and a fatal fall.
And they are not in the photograph.
This is not an oversight. It is the structural condition of the belayer role. The work is invisible when it is done correctly, and becomes visible only when it fails. The anchor that held is not remarkable. The anchor that failed is catastrophic and memorable. The belayer who managed the rope flawlessly for six hours has done nothing noteworthy by the standards of the record. The belayer who made one error at the critical moment has done something that will be discussed for years.
The organizational equivalent of the belayer is everywhere. And the systematic undervaluation of the belayer function is one of the most expensive and least examined failures in team design.
What the belayer actually does
The belayer’s function is not supplementary to the lead climber’s. It is the system within which the lead climber’s work is possible at all.
The lead climber takes the visible risks, makes the visible decisions, receives the visible recognition. The belayer manages the invisible infrastructure. The rope tension that gives the lead climber the confidence to commit to a difficult move, the anchor system that makes the entire structure sound, the communication protocol that ensures the lead climber knows exactly what the system below them can and cannot support.
Remove the belayer and the lead climber cannot climb. This is not metaphor. It is the literal mechanics of the rope system. The summit is not the lead climber’s achievement alone. It is the joint product of the lead climber’s visible performance and the belayer’s invisible competence.
Most summit photographs tell half the story.
“The summit is not the lead climber’s achievement alone. It is the joint product of the lead climber’s visible performance and the belayer’s invisible competence.”
The organizational belayer
In organizations, the belayer function appears wherever there is visible high-performance work that depends on invisible supporting infrastructure. It is the function that does not appear in the outcome metrics but without which the outcome metrics would not be achievable.
The engineering manager who absorbs organizational complexity so that the engineers can write code without interruption. The executive assistant who manages the relationships and logistics that make the executive’s accessibility possible. The data analyst whose work enables the product manager’s strategic recommendations to be credible. The HR professional whose culture-building work creates the psychological safety that allows the team to perform.
None of these appear in the summit photograph. All of them are load-bearing.
The specific damage that organizations do to the belayer function is threefold. First: they underpay it, because the belayer function is invisible when it works correctly and compensation systems reward visible output. Second: they under-recognize it, because recognition systems are calibrated to celebrate visible achievement. Third: they discover its value only in its absence.
The belayer’s function becomes visible at the moment it fails or is removed. The executive whose assistant leaves and suddenly cannot manage their own schedule. The engineering team whose manager is promoted and suddenly cannot ship without organizational interference. The product organization whose data analyst departs and suddenly cannot make credible strategic recommendations. The value that was invisible when present becomes devastatingly visible when absent.
This is the most expensive form of undervaluation. Not knowing what you have until it is gone.
What the lead climber owes the belayer
The experienced lead climber knows something that the summit photograph obscures. The summit is a joint achievement, and the relationship between lead climber and belayer is not hierarchical in the direction that the photograph implies.
The belayer holds the lead climber’s life. This is a role of profound responsibility that requires specific technical competence, sustained attention, and the willingness to perform excellently in conditions of zero recognition.
The experienced lead climber names this explicitly. They credit the belay in the expedition report. They build the relationship over time rather than treating the belayer as interchangeable infrastructure. They understand that their own performance is conditional on the quality of the system that holds them.
In organizations: explicitly naming the enabling work in public recognition. Building the compensation system to reflect the value of the output enabled rather than the visibility of the function. Treating the departure of a key belayer as a significant organizational risk rather than a backfill problem. And asking, before the belayer leaves, “what do you know that we are not tracking?” Because the answer is almost always more valuable than the organization has been treating it.
The summit is the halfway point. The belayer is the reason you got there and the reason you got back.the reason you got there and the reason you got back.
THE TEAM TEST
Name the belayer in your organization. The person or function whose work is load-bearing for outcomes that get attributed to someone else.
Now ask three questions honestly.
Are they compensated at the level of the value they enable, not the visibility of their function, but the value of the output their function makes possible?
When did you last name their contribution publicly, not in a general “team effort” acknowledgment, but specifically, precisely, in a way that made the invisible work visible to the people who benefit from it?
And the hardest question: if they left tomorrow, how long would it take for the lead climber to realize they were no longer on belay?
The answer to the third question is the measure of how well the organization understands what it actually depends on.
