If you were recently put in charge of people and every meeting now feels like a step backward from the work you were promoted for doing well, this piece is for you. What you are feeling is not a management failure. It is a physics problem. And the mountain explains it exactly.
There is a specific kind of freedom that only exists when you are moving alone on a mountain.
No partner to wait for. No anchor to build while someone else catches their breath. No negotiation about pace, no compromise on line, no one else’s fear bleeding into your decisions. You read the terrain, you move, you commit. The feedback loop between observation and action collapses to almost nothing. At full speed on good snow, it feels less like climbing and more like thinking with your body, fluid, immediate, intoxicating.
Every high-performing individual contributor knows this feeling, even if they have never touched a crampon. It is the state of deep autonomous execution. The codebase you own completely, the client relationship only you can navigate, the creative process that produces its best work precisely because no one else is in the room. You know what needs to happen. You can see it. And you can move toward it at a speed that feels, from the inside, like flying.
Then they put you in charge of people.
And everything stops.
Suddenly there are meetings where the answer was obvious twenty minutes ago. Decisions that should take an hour take a week because three people need to align. A teammate who is technically capable but moves at half your speed. The creeping, maddening sensation that you are being held back by the very team you were promoted to lead.
This is not a management problem. It is a physics problem. And the mountain explains it exactly.
The tax
Solo alpinism is fast because it is fragile. The soloist carries no redundancy. A single crampon failure, a single misjudged snow bridge, a single moment of hypoxic confusion with no one there to catch it, and there is no recovery. The speed is real. The cost of that speed, denominated in risk, is also real. Soloists accept the trade because they are betting entirely on their own excellence, and because the load they can carry alone is light.
The moment the mission requires a heavy load, serious technical gear, expedition-weight supplies, the infrastructure required to go higher or farther than any single person can sustain, you rope up. Not because roping up is philosophically preferable. Because it is the only mechanism that makes the objective achievable.
Roping up always makes you slower. This is not a bug in the system. It is the cost of scale, paid in advance, in the only currency that matters on a mountain: time and speed.
The founder who transitions from solo execution to leading a team is not being asked to become less capable. They are being asked to pay this tax. The promoted IC who spends their first six months as a manager furious at how slowly things move is not wrong about the slowness. They are wrong about what the slowness means. It doesn’t mean the team is broken. It means the mission got heavier.
Alignment is a lie
Corporate culture has a word it loves for this moment: alignment.
We need to get aligned. We need to make sure everyone is aligned. Let’s schedule an alignment session.
Alignment is a lie, or at least a profound understatement, because it describes a cognitive state (people agreeing on a direction) while completely obscuring the structural reality that makes teams function under pressure.
On a rope team, you are not aligned with your partner. You are tied to them.
The distinction is not semantic. When you tie in on a glacier, you are physically attaching your life to another person’s competence. If they step into a hidden crevasse and fall, the rope goes taut and they take you with them, unless you arrest the fall in the fraction of a second before the force becomes unrecoverable. Their mistake is your emergency. Their momentum is your problem. There is no version of events in which they fall and you continue climbing.
This is what shared fate actually means. Not shared goals. Not shared values. Not a shared Slack channel. Structural consequences that travel across the rope whether you want them to or not.
Look at your organization honestly against this standard. If Marketing hits their number and collects their bonus while Sales misses and the company suffers, you don’t have a team. You have soloists climbing on the same mountain. They may be polite to each other at base camp. They may attend the same all-hands. But when someone falls, there is no tug. There is no arrest. There is just one person’s outcome separating cleanly from another’s, which means the rope was never actually tied.
The test is simple and brutal. When someone on your team fails, does the rest of the team feel it? Not emotionally, not empathetically. Structurally. Does it land on them with physical force? If the answer is no, you have alignment. You do not have a rope team.
“Alignment is a lie. On a rope team, you are not aligned with your partner. You are tied to them.”
The art of the slack
Tying in is the beginning of the work, not the end of it. Once you are roped together, a new skill dominates everything: managing the rope between you.
A climbing rope is not a static connection. It is a live system that requires constant, situational adjustment based on terrain, pace, risk, and the specific capabilities of the person on the other end. Get it wrong in either direction and the consequences are severe.
Too tight, and the leader’s movement constantly destabilizes the follower. Every step forward generates a pull that throws them off balance before they have completed their own movement. This is micromanagement rendered in physics. Not malicious, usually well-intentioned, and completely destructive to the follower’s ability to develop their own footing. A climber who is perpetually pulled forward by a tight rope never learns to read terrain. They learn to react to the rope.
Too much slack, and you have created a different catastrophe. When a fall happens, and on a long route a fall will happen, the slack converts directly into velocity. The falling climber accelerates for every foot of rope they have before it comes taut, and when it does, the shock load transmitted to the anchor can be enough to rip the protection clean out of the wall. What would have been a manageable fall with proper rope discipline becomes a system failure. This is absentee management. The leader has given the team room to move, but the room has become so large that when something goes wrong, the force arrives all at once and destroys everything before anyone can respond.
The leader’s job, on the mountain and in the organization, is the continuous, active, imperfect calibration of the slack between these two failures. Not once, not in an annual review, not in a quarterly check-in. Continuously. Because the terrain changes, the pace changes, the competence of the person behind you changes as they grow, and what was the right amount of rope last month may be too tight or too loose today.
The question leaders rarely ask explicitly but should ask constantly: am I pulling them off balance by hovering, or am I leaving so much slack that a mistake will become a crisis before I see it?
There is no formula for the answer. There is only the discipline of asking.
THE TEAM TEST
Look at the people you call your team.
Are you actually tied together, with consequences that travel across the connection whether anyone wants them to or not? Or are you a group of high-performing soloists who share a budget, a reporting structure, and a Monday standup, but who ultimately move alone, succeed alone, and fail alone?
If someone on your team stepped into a crevasse today, would you feel the rope go taut?
Or would you find out in the next sprint review?
