Lessons from the Eye of a Hurricane

Great Things Rarely Begin in Perfect Conditions

Some of the most powerful forces in nature begin with something seemingly insignificant.

A hurricane doesn't announce its arrival as a massive, organized force capable of reshaping coastlines. It begins as a disturbance. A collection of atmospheric conditions that, individually, might not seem particularly remarkable.

Warm ocean water. Rising air. Moisture. A developing area of low pressure.

None of these things, by themselves, constitute a hurricane.

Yet under the right conditions, these individual elements begin interacting. Energy accumulates. Movement becomes organized. What once appeared to be an unremarkable collection of forces can eventually become one of the most powerful weather systems on Earth.

I've spent much of my career building, developing, and leading teams, and the more I think about this phenomenon, the more similarities I see between the formation of a hurricane and the development of a high-performing team.

In leadership, we frequently reference Bruce Tuckman's model of team development: Forming, Storming, Norming, and Performing.

It's a model that has existed since 1965, and for good reason. It provides a relatively simple way to understand the complicated dynamics of people learning to work together.

But I've always believed that understanding the stages of team development and understanding what's actually happening within those stages are two very different things.

We know teams form. We know they experience conflict. We know they eventually establish ways of working together. And, under the right circumstances, they begin performing at a level that exceeds what those individuals could accomplish independently.

But why?

What transforms a collection of talented individuals into something greater than the sum of its parts?

Perhaps the answer has less to do with the individuals themselves and more to do with the conditions that allow their collective energy to become organized.

Much like a hurricane.

1. Forming: The Tropical Disturbance

Every powerful system begins with potential, not certainty.

Hurricanes begin over warm tropical waters, where heat and moisture provide the energy needed to sustain developing thunderstorms.

As warm, moist air rises, pressure near the ocean's surface can begin to fall. Surrounding air moves inward, additional moisture rises, and the process can reinforce itself.

But there's an important distinction.

Not every tropical disturbance becomes a hurricane.

In fact, most don't.

The ingredients can be present without the conditions ever becoming favorable enough to produce an organized, sustained system.

I think about this whenever I see organizations bring together a group of incredibly talented people and expect high performance to emerge naturally.

We hire exceptional engineers, designers, analysts, product managers, and leaders. We put them on a team, give them a common objective, and assume their collective talent will produce extraordinary results.

Sometimes it does.

Often, it doesn't.

Because a collection of high-performing individuals is not necessarily a high-performing team.

During the forming stage, people are still trying to understand their environment.

Who can I trust?

What's expected of me?

Where do I fit?

Whose opinion carries weight?

What happens when I disagree?

These questions aren't necessarily spoken aloud, but they influence almost every interaction.

People bring their own experiences, assumptions, ambitions, insecurities, and ways of working. Each person enters the environment carrying energy that has been shaped by their previous experiences.

And just like the atmospheric conditions surrounding a developing storm, that energy can either contribute to the emerging system or work against it.

This is where leadership has its first significant responsibility.

Not to force the team into immediate performance, but to create the conditions in which performance can eventually emerge.

That means establishing a clear purpose, creating opportunities for relationships to develop, clarifying expectations, and making it safe for people to contribute before they've figured everything out.

You cannot command a tropical disturbance to become a hurricane.

And you cannot command a group of strangers to become a high-performing team.

You can, however, influence the conditions surrounding them.

2. Storming: When the Winds Begin to Intensify

What looks like chaos may actually be the beginning of organization.

As a tropical system develops, atmospheric pressure can continue to fall, circulation strengthens, and thunderstorms begin organizing around a developing center.

The system becomes more energetic.

Winds increase. Rain intensifies. Previously disconnected activity begins interacting in increasingly complex ways.

From the outside, the environment appears to be getting worse.

But something important may be happening beneath the turbulence.

The system is beginning to organize.

This is the stage of team development that I believe is most frequently misunderstood.

Storming.

It's the stage where the excitement of forming gives way to the realities of working with other human beings.

Differences become visible.

One engineer challenges another's technical approach.

A product owner pushes for speed while the development team raises concerns about quality.

A team member questions a decision that everyone else seemed comfortable accepting.

Someone becomes frustrated because they believe their contributions aren't being recognized.

And suddenly, the environment that initially felt so promising begins to feel uncomfortable.

Many leaders interpret this discomfort as evidence that something is wrong.

They rush to resolve disagreements, suppress difficult conversations, introduce additional controls, or attempt to restore the harmony that existed when everyone was still getting acquainted.

But harmony and effectiveness are not the same thing.

Sometimes what appears to be harmony is nothing more than people avoiding the conversations that actually need to happen.

I've seen teams that rarely disagreed with one another, not because they were particularly aligned, but because people had learned that disagreement wasn't worth the consequences.

They looked peaceful.

They weren't necessarily healthy.

Conflict isn't automatically evidence of dysfunction. Sometimes it's evidence that people have finally become comfortable enough to reveal what they actually think.

That distinction matters.

A team challenging assumptions, questioning approaches, and debating competing ideas may be developing the trust needed to perform at a higher level.

However, this doesn't mean all conflict is productive.

A hurricane's turbulence can produce destruction, and interpersonal conflict can do the same.

Personal attacks, intimidation, exclusion, and disrespect don't make teams stronger. They destroy the trust required for collaboration.

The leader's responsibility isn't to encourage conflict for its own sake.

It's to help people distinguish between challenging an idea and attacking a person.

Between productive tension and unnecessary friction.

Between discomfort that leads to growth and behavior that undermines psychological safety.

And perhaps most importantly, between a disagreement that needs resolution and a difference in perspective that the team can learn to appreciate.

The objective isn't to eliminate the storm. It's to help the team develop the ability to move through it without losing one another.

3. Norming: Finding a Common Center

Organization emerges when individual forces begin working within a shared system.

As a hurricane develops, its circulation becomes increasingly organized around a central area of low pressure.

Bands of thunderstorms spiral around the system. Air moves inward near the surface, rises within intense thunderstorms, and flows outward at higher altitudes.

What once appeared disconnected begins participating in a larger pattern.

There is still tremendous movement, but that movement now has structure.

This is what makes the norming stage so fascinating to me.

Because a team doesn't suddenly become effective when everyone starts agreeing.

It becomes effective when people begin understanding how to work together, particularly when they don't agree.

Something changes.

Team members begin anticipating one another's needs.

They understand each other's strengths and limitations.

They know who to approach when a problem emerges.

They recognize when someone needs support and when someone needs space to solve a problem independently.

More importantly, they begin developing shared expectations about how work gets done.

Those expectations are often what we call team norms, but I've never particularly liked reducing them to a working agreement that gets written on a whiteboard and forgotten.

A team's real norms aren't necessarily what it says it values.

They're what its members consistently demonstrate through their behavior.

If a team says it values transparency but important decisions happen behind closed doors, secrecy is the actual norm.

If a team says it values collaboration but rewards only individual achievements, competition may become the actual norm.

If a team says it values continuous improvement but punishes mistakes, self-preservation eventually becomes the norm.

Culture is not what we declare.

Culture is what our systems repeatedly encourage, tolerate, and reinforce.

And that brings us back to the hurricane.

What gives the storm its recognizable structure isn't the elimination of movement. It's the organization of movement around a common center.

For a team, that center should be its shared purpose.

Not the manager.

Not the most senior engineer.

Not the loudest voice in the room.

The problem the team exists to solve.

When individuals understand that shared purpose, something extraordinary becomes possible.

People can disagree about the approach while remaining aligned on the outcome.

They can challenge decisions without challenging one another's value.

They can recognize that their individual contribution matters, but that its greatest value often comes from how it enables everyone else's contributions.

The team develops coherence.

And coherence is far more powerful than compliance.

4. Performing: The Eye of the Hurricane

The most remarkable part of a powerful hurricane may be the place where the winds become calm.

At the center of a mature, well-organized hurricane is the eye.

A region of relatively calm conditions surrounded by the eyewall, where some of the storm's most intense winds and rainfall occur.

It's a fascinating contrast.

Near the center of an extraordinarily powerful system, there can be a sense of stillness.

Yet just beyond that relative calm, tremendous energy is moving.

I've always thought this was a powerful way to understand high-performing teams.

Because high performance isn't the absence of pressure.

It isn't a team that never encounters setbacks, disagreements, uncertainty, or difficult decisions.

In many cases, the teams delivering the greatest value are operating in environments filled with those very things.

Deadlines shift.

Priorities compete.

Technologies evolve.

Customers change their minds.

Unexpected problems emerge.

The world surrounding the team rarely becomes less complicated simply because the team has learned how to perform.

But something within the team changes.

People become less reactive.

They make decisions with greater confidence.

They communicate without needing every interaction to be orchestrated by a manager.

They understand how to recover when something goes wrong.

They can move quickly without abandoning the relationships and practices that allow them to sustain that movement.

There is a relative calm at the center of their work.

Not because the challenges have disappeared, but because the team has developed a shared understanding of how to navigate them.

And this is where I believe leadership becomes especially interesting.

The goal of a leader shouldn't be to become the eye of the storm. It should be to help the team establish a center that exists independently of the leader.

Think about that for a moment.

If a team requires its manager to settle every disagreement, make every difficult decision, resolve every dependency, and constantly remind people why their work matters, how high-performing is it really?

What happens when that manager takes a vacation?

What happens when they're promoted?

What happens when the organization restructures?

If the system falls apart in their absence, the team may have become dependent on effective management rather than developing true collective capability.

I would argue that one of the greatest measures of leadership is not how well a team performs when its leader is present.

It's how well the team continues performing when that leader isn't.

This doesn't make leadership irrelevant.

Quite the opposite.

It means the leader has successfully invested in the relationships, clarity, trust, accountability, and decision-making capabilities that allow people to operate with increasing autonomy.

The leader is no longer required to generate every movement.

The team has developed the capacity to move together.

5. The Eyewall: Where Capability Meets Pressure

There's another part of a hurricane that makes this metaphor particularly compelling.

The eyewall.

Surrounding the relatively calm eye, the eyewall contains some of the hurricane's most intense weather.

This is where tremendous energy is concentrated.

For high-performing teams, I see the eyewall as the difficult work that surrounds their shared purpose.

The uncomfortable decisions.

The trade-offs.

The moments when doing the right thing requires more courage than doing the convenient thing.

It's the engineer raising a concern about a release that everyone wants to ship.

It's the team member admitting they made a mistake before anyone else discovers it.

It's the leader saying, "I don't know," rather than pretending to have an answer.

It's the team choosing to address a recurring problem instead of finding another temporary workaround.

These are the moments that reveal whether trust and alignment are genuine.

Anyone can talk about accountability when everything is going well.

Anyone can champion transparency when the information is favorable.

Anyone can promote psychological safety when no one has anything particularly uncomfortable to say.

The real test comes when those values are inconvenient.

A strong team doesn't avoid those moments.

It develops the capability to handle them without allowing the pressure to compromise its integrity.

And there's an important distinction here: Resilience should not be confused with an expectation of endless endurance.

High performance isn't about sustaining maximum intensity indefinitely.

People need recovery. They need boundaries. They need environments where the cost of delivering value doesn't continuously exceed the value being created.

A hurricane's intensity depends on the energy available to it and the conditions surrounding it.

Teams are no different in one important respect: their capacity is influenced by their environment.

Even talented, committed people cannot sustain exceptional performance when leadership continually removes the conditions that make it possible.

6. Wind Shear: The Forces That Can Tear a Team Apart

Not every developing storm becomes stronger.

One of the atmospheric conditions that can disrupt the organization of a tropical cyclone is vertical wind shear: changes in wind speed or direction with height.

Strong wind shear can displace thunderstorms away from a storm's center and interfere with the vertical organization needed for intensification.

The energy may still exist.

The moisture may still exist.

The potential may still exist.

But the system struggles to remain organized.

Organizations create their own versions of wind shear.

Competing priorities.

Constant restructuring.

Contradictory expectations.

Micromanagement.

Misaligned incentives.

Leaders who demand collaboration while evaluating people exclusively on individual output.

Teams that are expected to deliver long-term strategic outcomes while being interrupted continuously by short-term emergencies.

These forces pull people in different directions.

And what fascinates me is how frequently organizations respond to the resulting performance problems by focusing on the individuals.

We ask why people aren't more motivated.

Why the team isn't collaborating.

Why productivity has declined.

Why the culture seems to be deteriorating.

But what if the individuals aren't the primary problem?

What if the system surrounding them is making the desired behaviors increasingly difficult?

I've long believed that one of the most valuable things a leader can do is understand the difference between a people problem and a systems problem.

That doesn't mean people are never accountable for their choices.

It means accountability without an examination of the surrounding conditions often leads us to treat symptoms while preserving the causes.

Sometimes the most meaningful leadership intervention isn't another motivational speech, team-building exercise, or performance improvement plan.

Sometimes it's simply removing the forces that keep pulling people away from what matters.

7. The Storm Is Never Finished

There's one final aspect of this metaphor worth exploring.

Hurricanes are not permanent structures.

Their organization and intensity change as they interact with their environments.

They can strengthen, weaken, reorganize, and eventually dissipate.

Teams evolve too.

And this is where I think the traditional interpretation of Forming, Storming, Norming, and Performing can become misleading.

We often describe the model as if teams move neatly through four sequential stages, eventually arriving at performing as though it's a permanent destination.

But anyone who has spent enough time leading teams knows that isn't how reality works.

A new person joins.

A respected teammate leaves.

A product changes direction.

A new leader arrives.

A major organizational decision changes the nature of the work.

Suddenly, a team that was operating exceptionally well begins experiencing uncertainty again.

People question decisions.

Roles become less clear.

Relationships have to adjust.

The team may find itself storming again.

And that isn't necessarily regression.

It's adaptation.

Tuckman's stages are useful for understanding group development, but they aren't a rigid sequence every team follows in exactly the same way.

Healthy teams revisit their agreements.

They renegotiate expectations.

They examine whether the approaches that worked yesterday are still appropriate today.

They recognize that growth can create new tensions that require new ways of working.

High performance isn't a permanent state. It's a capability that must continually be renewed.

The objective isn't to construct a team so perfectly that it never experiences turbulence again.

It's to develop a team capable of navigating turbulence without losing its purpose, relationships, or capacity to learn.

What Hurricanes Can Teach Us About Leadership

Obviously, there's an important limitation to this analogy.

Hurricanes are destructive forces of nature. High-performing teams should be forces for positive, meaningful outcomes.

And unlike atmospheric systems, people possess agency, emotion, judgment, and the ability to intentionally change how they interact with one another.

But that difference actually makes the metaphor more interesting to me.

A hurricane doesn't choose how its energy is organized.

A team can.

People can decide how they respond to disagreement.

They can choose whether to protect their own interests or support a shared outcome.

They can create conditions in which others feel comfortable contributing their ideas, admitting their mistakes, and challenging assumptions.

And leaders can choose whether to manipulate every movement or cultivate an environment in which people are capable of moving together.

When I reflect on the strongest teams I've had the privilege of building and serving, I don't remember them being free of conflict.

I remember the difficult conversations.

The problems we didn't immediately know how to solve.

The moments when someone challenged an idea that the rest of us had already accepted.

The occasions when the team came together to support someone who was struggling.

And perhaps most importantly, the moments when I realized they no longer needed me to provide the answer.

They had developed something far more valuable.

Trust in one another.

Confidence in their collective judgment.

A shared understanding of why their work mattered.

They had found their center.

That brings me back to the image of a hurricane.

A massive system composed of countless individual movements, each participating in something far greater than itself.

The power doesn't come from any single gust of wind.

It emerges from the interaction and organization of the entire system.

And perhaps that's the most important lesson of all.

A high-performing team isn't powerful because it contains extraordinary individuals. It's powerful because it creates the conditions in which ordinary and extraordinary individuals alike can accomplish something they couldn't accomplish alone.

Leadership isn't about preventing every storm.

It's about helping people build the trust, clarity, and shared purpose necessary to navigate the storms they'll inevitably encounter.

Because the true measure of a high-performing team isn't how well it performs when the conditions are perfect.

It's how effectively its members can move together when they aren't.

And the most meaningful legacy a leader can leave isn't a team that depends on their presence to succeed.

It's a team that has learned how to find its own center.

The storm may be inevitable. The way we move through it is not.

The next time your team encounters friction, before asking how to make the storm disappear, consider asking a different question:

Are we experiencing the turbulence of people pulling apart, or the growing pains of people learning how to move together?