If your team feels aligned but has never fought over anything real, this piece is for you. What you have is not culture. It is a rope that has never been weighted. And the moment it finally is, you will find out whether the anchor holds.
There is a moment on every rappel that no amount of instruction fully prepares you for.
You have built the anchor. You have threaded the rope. Your partner has checked your device, checked your harness, checked the system twice. Everything is correct. Now you have to do the thing that every nerve in your body is screaming at you not to do. You have to lean backward off the edge, transfer your full body weight onto the rope, and trust.
Not believe. Not hope. Trust, which is a physical act, not a cognitive one.
“An unweighted rope is just an idea of safety.”
Until that moment, the anchor is a theory. The rope is a promise. You can inspect every component, verify every connection, and still not know whether the system will hold. The only way to find out is to weight it. To deliberately stress it with everything you have and let it prove itself under load.
This is what Storming actually is. And almost every corporate leader is doing it wrong.
The comfortable lie of basecamp
Bruce Tuckman mapped the lifecycle of teams in 1965: Forming, Storming, Norming, Performing. The model is everywhere. What almost nobody teaches is how it actually feels, and how dangerously easy it is to mistake the first stage for the last.
Forming is basecamp. The team has assembled. Everyone is capable and credentialed. The conversation is energized and collegiate. People are generous with each other’s ideas, careful with each other’s egos. There is genuine excitement about what the group might accomplish together.
It feels like cohesion. It is not cohesion. It is an unweighted rope.
The rope looks right. The anchor looks solid. But no one has gone over the edge yet. No resource has been fought over. No priority has been forced. No one has had to tell a peer their flagship idea is the wrong call with the CEO in the room. The system has never been loaded.
I watch this in every New Product Development cohort I run, and in the executive teams I advise. The Forming phase is so pleasant, so productive-feeling, that leaders unconsciously work to preserve it. They run more alignment sessions. They build more shared frameworks. They invest in team culture before the team has any culture to invest in.
What they are actually doing is spending more time at basecamp to avoid having to weight the rope.
The rescue that breaks the team
Then Storming arrives. It always does.
Resources get constrained and two equally valid priorities collide. A deadline forces a decision that one team member thinks is catastrophically wrong and says so, loudly. An ego surfaces. A hierarchy that was implicit and polite becomes suddenly, uncomfortably explicit. The rope goes taut.
The well-meaning leader’s instinct is immediate. Intervene, de-escalate, restore the collaborative atmosphere that made Forming feel so promising. Enforce civility. Redirect the tension into a structured process. Make it stop.
This is the most dangerous thing they can do.
When you rescue a team from Storming, you don’t resolve the conflict. You drive it underground. The operational hierarchy (who defers to whom under pressure, whose judgment the team trusts when it costs something to trust it, who can deliver hard news and still be heard) never gets established. It exists as assumption and inference, untested and therefore unreliable.
More critically, the team never learns how to disagree safely with each other. They never develop the live protocols for escalating a risk when the stakes are real and the relationship is on the line. They never find out, under controlled pressure, whether their anchor holds.
What you have instead is a group of talented people who have learned one durable lesson. Conflict in this system gets suppressed. So the next time someone sees something wrong, they run a quick calculation. The cost of raising it versus the cost of staying quiet. They stay quiet. The early warning system shuts down. The storm goes underground.
Underground storms don’t dissipate. They build pressure. They wait for the worst possible moment, the product launch, the board meeting, the acquisition close, the moment when the team is already at altitude and the weather is already turning. Then they surface all at once. Except now there is no controlled environment to work through them. Now it is a crisis.
You didn’t save the team. You just ensured they would shatter later, under real load, in conditions where recovery is no longer possible.
“The team that never Stormed doesn’t have a culture. It has a ceasefire.”
What the rope teaches
The job of the leader during Storming is not to stop the conflict. It is to create the conditions in which the conflict can do its work.
On a technical climb, this means building an anchor that is genuinely bomber. Not so the rope never gets tested, but so that when it does, the system holds and the climber learns something true about their gear and themselves. You build the anchor well precisely because you intend to weight it hard. The goal was never to avoid the load. The goal was to be ready for it.
In a team, it means staying present in the friction without rescuing anyone from it. It means letting the hierarchy surface naturally under load rather than imposing it artificially before it has been earned. It means treating the first significant conflict not as a failure of team culture but as the team culture finally becoming real.
Once you see it that way, most “team-building” spend starts looking like the money you paid to avoid finding out whether the anchor was ever any good.
THE TEAM TEST
When your team first shows signs of Storming (the friction, the clashing priorities, the first moment someone says something that lands badly) what do you actually do? Do you move immediately to restore the peace? Or do you recognize that the rope is finally being weighted, stay close, and let the anchor prove itself?
If you have never let your team Storm, truly Storm, with the conflict on the table and the hierarchy at stake, then you don’t have a high-performance team. You have a group of people who have agreed, implicitly, to keep the rope unweighted.
You won’t know that until the moment it matters most. Which is exactly when you will need it to hold.
