Point Lookout: a free weekly publication of Chaco Canyon Consulting
Volume 25, Issue 4;   January 22, 2025: Storming: Obstacle or Pathway?

Storming: Obstacle or Pathway?

by

The Storming stage of Tuckman's model of small group development is widely misunderstood. Fighting the storms, denying they exist, or bypassing them doesn't work. Letting them blow themselves out in a somewhat-controlled manner is the path to Norming and Performing.
A diagram of the cross section of a boat with a single water ballast tank at the bottom

A diagram of the cross section of a boat with a single water ballast tank at the bottom. In a heavy storm, taking on water for the ballast tank is necessary for achieving stability of the boat. It's an example of using an element that threatens your survival (water) to increase your chances of survival.

So it is with the Storming stage of development in small groups. Spending time examining your problems is a necessary first step to solving those problems. If you try to solve the problems before you agree on what the problems are, failure is likely.

Image by PanScient courtesy Wikimedia.

Dozens, maybe hundreds of white papers, workshops, and Web pages agree that the second stage of Tuckman's development sequence for small groups — the stage Tuckman called Storming — is painful. [Tuckman 1965] [Tuckman & Jensen 1977] Those resources assert that Storming stands in the way of the next two stages, Norming and Performing. They hold that with its focus on conflict, frustration, and disagreement, Storming prevents groups from getting work done. There are tips for getting through Storming, for leaving it behind as quickly as possible. For a brief review of Tuckman and Jensen's model, see "Tuckman's Model and Joint Leadership Teams," Point Lookout for January 18, 2023.

Examples of advice available:

  • Refocus on goals
  • Break goals into smaller achievable steps
  • Develop conflict management skills
  • Focus on collaborative process

The idea these advocates present seems to be that by getting the group to start Norming, we can end Storming and get on with the task. For them, Storming is a period of near-zero productive output that we must tolerate because, well, we must.

I see things differently. The Storming stage can be productive, but we must be careful about what we mean by productive. What Storming produces is a modified version of the group itself. This modified version of the group is one that can do what's needed in the Norming stage because the obstacles related to Storming have been cleared away.

The work Only by addressing the issues of
the Storming stage can the group
develop the foundation needed
for Norming and Performing
we do in the Storming stage is necessary and productive. Storming is the period when the group constructs the foundations necessary for producing the behavioral and professional norms and the group structure that it will need when it starts accomplishing its task first in the Norming stage and later in the Performing stage. Only by addressing the issues of the Storming stage can the group develop that foundation. Storming isn't an obstacle. Storming is the way forward.

An example of a tangle due to ineffective Storming

One tangle that ensnares some groups is trying to work towards a goal before the group agrees about what the goal is. In some cases, groups try to work towards a goal even before the group can agree about what the goal is.

Consider a project team that has intentionally abbreviated its time in the Storming stage. The sense among its leaders and managers had been something along the lines of, "Enough of this analysis-paralysis. We know what we need to know to make a start on our task. We can work out the final details along the way."

And that's how two subgroups — Subgroup A and Subgroup B — started building parts of what each subgroup surmised would be needed. But since Subgroup A's interpretation of the goal differed from Subgroup B's interpretation of the goal, their two efforts eventually reached a point of irreconcilable conflict. Partway through their work, the conflict between their two interpretations became clear. A debate erupted. They halted work until the larger group could decide — or until Management could decide — which of the two paths the group would follow. Since time is money, they made that critical decision under time pressure, and that caused them to overlook some important factors. More waste. More lost time.

The group could have avoided the waste and lost time if they had used the Storming stage to learn how to disagree constructively. The problem wasn't analysis-paralysis. It was instead an inability to conduct respectful debate — or even air differences — among people who hold contradictory opinions. This skill deficit prevented the group from exploring differences in enough detail to uncover ambiguities in descriptions of customer preferences.

The problem was that the group had tried to start working on task before they had properly exposed their differences in the Storming stage. And that prevented them from using the Norming stage to create a unified, cohesive approach to the task.

Statements of possible task goals

In the example above, the group could have made progress in goal clarification during the Storming stage. Setting specific goals is best left for the Norming stage, but the exercise of clearly stating differing views of possible goals is valuable for developing clarity during Storming. And that exercise is appropriate for Storming because it doesn't involve final priority decisions, which are better left for the Norming stage or later. More about this next time.

Last words

The Storming stage isn't a time for making decisions. It's a time for expressing doubts and frustrations and hearing others express theirs. It's a time for giving everyone permission to face squarely the problems that stand in the path to success. The group can do this by taking a problem inventory. Next time I'll provide the beginnings of a framework for taking that inventory.  A Framework for Safe Storming Next issue in this series  Go to top Top  Next issue: A Framework for Safe Storming  Next Issue

Great Teams WorkshopOccasionally we have the experience of belonging to a great team. Thrilling as it is, the experience is rare. In part, it's rare because we usually strive only for adequacy, not for greatness. We do this because we don't fully appreciate the returns on greatness. Not only does it feel good to be part of great team — it pays off. Check out my Great Teams Workshop to lead your team onto the path toward greatness. More info

More about Tuckman's sequence of small group development

Tuckman's stages of group developmentReaching Agreements in Technological Contexts  [December 7, 2022]
Reaching consensus in technological contexts presents special challenges. Problems can arise from interactions between the technological elements of the issue at hand, and the social dynamics of the group addressing that issue. Here are three examples.

Promotional photo of Boris Karloff from The Bride of Frankenstein as Frankenstein's monsterThe Politics of Forming Joint Leadership Teams  [January 4, 2023]
Some teams, business units, or enterprises are led not by individuals, but by joint leadership teams of two or more. They face special risks that arise from both the politics of the joint leadership team and the politics of the organization hosting it.

Tuckman's stages of group developmentTuckman's Model and Joint Leadership Teams  [January 18, 2023]
Tuckman's model of the stages of group development, applied to Joint Leadership Teams, reveals characteristics of these teams that signal performance levels less than we hope for. Knowing what to avoid when we designate these teams is therefore useful.

A white water rafting team completes its courseWhite Water Rafting as a Metaphor for Group Development  [December 4, 2024]
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies better to development of some groups than to others. We can use a metaphor to explore how the model applies to Storming in task-oriented work groups.

Tuckman's stages of group developmentSubgrouping and Conway's Law  [December 18, 2024]
When task-oriented work groups address complex tasks, they might form subgroups to address subtasks. The structure of the subgroups and the order in which they form depend on the structure of the group's task and the sequencing of the subtasks.

A monarch butterfly emerges from its chrysalisThe Storming Puzzle: I  [December 25, 2024]
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies to today's task-oriented work groups — if we adapt our understanding of it. If we don't adapt, the model appears to conflict with reality.

Image of Hurricane Isabel by Astronaut Ed Lu, taken from the International Space Station, September 15, 2003The Storming Puzzle: II  [January 1, 2025]
For some task-oriented work groups, Tuckman's model of small group development doesn't seem to fit. Storming seems to be absent, or Storming never ends. To learn how this illusion forms, look closely at Satir's Change Model and at what we call a task-oriented work group.

National Weather Service Director Jack Kelly presents civil engineer Herbert Saffir (on right) with a framed poster of Hurricane Andrew depicting the Saffir-Simpson scale for rating the strength of hurricanesThe Storming Puzzle: Six Principles  [January 8, 2025]
For some task-oriented work groups, Tuckman's model of small group development seems not to fit. Storming seems to be either absent or continuous. To learn how this illusion forms, look closely at the processes that can precipitate episodes of Storming in task-oriented work groups.

An informal meeting geometryThe Storming Puzzle: Patterns and Antipatterns  [January 15, 2025]
Tuckman's model of small group development, best known as "Forming-Storming-Norming-Performing," applies to today's task-oriented work groups, if we understand the six principles that govern transitions from one stage to another. Here are some examples.

The Eisenhower Matrix of Urgency by ImportanceA Framework for Safe Storming  [January 29, 2025]
The Storming stage of Tuckman's development sequence for small groups is when the group explores its frustrations and degrees of disagreement about both structure and task. Only by understanding these misalignments is reaching alignment possible. Here is a framework for this exploration.

People in a conference roomOn Shaking Things Up  [February 5, 2025]
Newcomers to work groups have three tasks: to meet and get to know incumbent group members; to gain their trust; and to learn about the group's task and how to contribute to accomplishing it. General skills are necessary, but specifics are most important.

An apple and an orange. The phrase "comparing apples and oranges" is idiomatic for "false equivalence fallacy"On Substituting for a Star  [February 12, 2025]
Newcomers to work groups have three tasks: to meet and get to know incumbent group members; to gain their trust; and to learn about the group's task and how to contribute to accomplishing it. All can be difficult; all are made even more difficult when the newcomer is substituting for a star.

Footnotes

Comprehensive list of all citations from all editions of Point Lookout
[Tuckman 1965]
Bruce W. Tuckman. "Developmental sequence in small groups," Psychological Bulletin 63:6 (1965), pp. 384-399. Available here. Retrieved 15 October 2024. Back
[Tuckman & Jensen 1977]
Bruce W. Tuckman and Mary Ann C. Jensen. "Stages of small-group development revisited," Group and organization studies 2:4 (1977), pp. 419-427. Available here. Retrieved 22 November 2022. Back

Your comments are welcome

Would you like to see your comments posted here? Send me your comments by email, or by Web form.

About Point Lookout

This article in its entirety was written by a 
          human being. No machine intelligence was involved in any way.Thank you for reading this article. I hope you enjoyed it and found it useful, and that you'll consider recommending it to a friend.

This article in its entirety was written by a human being. No machine intelligence was involved in any way.

Point Lookout is a free weekly email newsletter. Browse the archive of past issues. Subscribe for free.

Support Point Lookout by joining the Friends of Point Lookout, as an individual or as an organization.

Do you face a complex interpersonal situation? Send it in, anonymously if you like, and I'll give you my two cents.

Related articles

More articles on Conflict Management:

A calm seaAn Emergency Toolkit
You've just had some bad news at work, and you're angry or really upset. Maybe you feel like the target of a vicious insult or the victim of a serious injustice. You have work to do, and you want to respond, but you must first regain your composure. What can you do to calm down and start feeling better?
A pariah dogPariah Professions: I
In some organizations entire professions are held in low regard. Their members become pariahs to some people in the rest of the organization. When these conditions prevail, organizational performance suffers.
"The Thinker," by Auguste RodinThey Just Don't Understand
When we cannot resolve an issue in open debate, we sometimes try to explain the obstinacy of others. The explanations we favor can tell us more about ourselves than they do about others.
A review meetingReframing Revision Resentment: II
When we're required to revise something previously produced — prose, designs, software, whatever, we sometimes experience frustration with those requiring the revisions. Here are some alternative perspectives that can be helpful.
"My Wife and My Mother-in-Law", a famous optical illusionResolving Ambiguity
Ambiguity is anathema to success in collaborations. It causes errors and rework, extending time-to-market. When we interpret information, we often choose the first interpretation we find, never recognizing that others are possible. That leads to failure.

See also Conflict Management for more related articles.

Forthcoming issues of Point Lookout

Aerial view of the Charley River at its confluence with the YukonComing June 18: Meandering Monologues in Meetings: Time
In a meeting, a meandering monologue has taken over when someone speaks at length with no sign of coming to a clear point, with no clear direction, and with little evidence of relevance to the topic at hand. This behavior wastes time, reduces engagement, and delays decisions. Available here and by RSS on June 18.
Braided streams in Grewingk Glacier RiverAnd on June 25: Meandering Monologues in Meetings: Engagement
In a meeting, a meandering monologue has taken over when someone speaks at length with no sign of coming to a clear point, and little of evident value. This behavior reduces engagement on the part of other attendees, thereby limiting the meeting's value to the organization. Available here and by RSS on June 25.

Coaching services

I offer email and telephone coaching at both corporate and individual rates. Contact Rick for details at rbrenner@ChacoCanyon.com or (650) 787-6475, or toll-free in the continental US at (866) 378-5470.

Get the ebook!

Past issues of Point Lookout are available in six ebooks:

Reprinting this article

Are you a writer, editor or publisher on deadline? Are you looking for an article that will get people talking and get compliments flying your way? You can have 500-1000 words in your inbox in one hour. License any article from this Web site. More info

Follow Rick

Send email or subscribe to one of my newsletters Follow me at LinkedIn Follow me at Bluesky, or share a post Subscribe to RSS feeds Subscribe to RSS feeds
The message of Point Lookout is unique. Help get the message out. Please donate to help keep Point Lookout available for free to everyone.
Technical Debt for Policymakers BlogMy blog, Technical Debt for Policymakers, offers resources, insights, and conversations of interest to policymakers who are concerned with managing technical debt within their organizations. Get the millstone of technical debt off the neck of your organization!
Go For It: Sometimes It's Easier If You RunBad boss, long commute, troubling ethical questions, hateful colleague? Learn what we can do when we love the work but not the job.
303 Tips for Virtual and Global TeamsLearn how to make your virtual global team sing.
101 Tips for Managing ChangeAre you managing a change effort that faces rampant cynicism, passive non-cooperation, or maybe even outright revolt?
101 Tips for Effective MeetingsLearn how to make meetings more productive — and more rare.
Exchange your "personal trade secrets" — the tips, tricks and techniques that make you an ace — with other aces, anonymously. Visit the Library of Personal Trade Secrets.
If your teams don't yet consistently achieve state-of-the-art teamwork, check out this catalog. Help is just a few clicks/taps away!
Ebooks, booklets and tip books on project management, conflict, writing email, effective meetings and more.