A model for team development

A model for team development

Assembling a high performing team that delivers quality outcomes within tight timeframes requires some thought. Fortunately, there is a model for team development that will help you and your team tackle problems, develop healthy conflict, find better solutions, and, ultimately, grow together.?

The model is called?forming-storming-norming-performing-adjourning,?developed by Bruce Tuckman in 1965?and then later extended in?collaboration with Mary Ann Jensen in 1977. As a model it has stood the test of time. It remains one of the best frameworks and strategies for thinking about group dynamics and development, helping many teams come together and achieve quality results.

No alt text provided for this image

Each of these stages is expanded upon below.

Stage 1: Forming

In the Forming stage, the team is brought together and considers the work ahead of them. They learn about the challenges and opportunities of the work, agree on goals, and assign tasks.?

Emotions

Emotions of team members are usually along the lines of excitement or anxiousness. Excitement about the goals they’re setting out to achieve, but anxiousness about how they will fit in or whether the team will perform.

Behaviours

As the team familiarises themselves with the work and each other, they are likely to use a considered and polite approach in their interactions. Team members may also act hesitantly—this is due to uncertainty in their role, their position (whether formal or not), and the interpersonal dynamics with others.

Tasks

The key tasks for team development in this stage are:

  1. Create and share structure, goals and roles.
  2. Share mission, context, and expectations.
  3. Establish processes and ways of working.?

Stage 2: Storming

In the Storming stage, the team has been working together and is starting to sort itself out. Members will voice their opinions, question decisions, and make assessments of each other. People may feel that the team can’t reach its goals, or perhaps won’t work or perform in the way they expected.?

This stage will likely come with some conflict, thus the name ‘Storming’. In Tuckman’s paper, 50% of the team’s studied had intragroup conflict. However, some teams also completely skip this stage.

If there is conflict, it shouldn’t be overly concerning. Sometimes conflict is necessary in order to work through differences and to develop communication skills and channels. Interventions can sometimes, counter-intuitively, be counter productive. Any disagreements must be resolved before the team can progress out of this stage.?

Emotions

If this stage takes place, then emotions are usually along the lines of frustration or anger with the team’s performance, the leader, individual team members, ways of working, or the work itself.?

Behaviours

Team members may argue or express frustration during this stage. Some may not participate to the extent that they are capable. In extreme cases, there may also be behaviours that undermine the team or actively work against it.

Tasks

The key tasks for team development in this stage are:

  1. Refocusing on goals, perhaps breaking the goals down into smaller steps.?
  2. Re-evaluating ways of working.
  3. Redefining plans based on insights gained by the team.

Stage 3: Norming

In the Norming stage, with conflicts and disagreements now resolved, the team will find a spirit of cooperation. Working towards a common goal, all team members will be taking responsibility for their work, and be more tolerant of others in an effort to work together. There’s a danger in this stage that avoiding conflict will make people reluctant to share ideas.

Emotions

Through this stage, team members will feel energised and in harmony. A greater feeling of acceptance and belief in a common goal will give team members energy to work,?as well as a deeper connection to their team members.?

Behaviours

Team members will start to ambitiously work together to achieve the team’s goals. Roles and relationships will be more established, and big decisions can be made and implemented.

Tasks

The key tasks for team development in this stage are:

  1. Working together to achieve team goals.
  2. Optimising ways of working.
  3. Communication, collaboration, and harmony.

Stage 4: Performing

In the Performing stage, the team can start to reach an unexpectedly high level of success. Team members are both motivated and knowledgeable—their ability to autonomously work and handle big decisions keeps the team delivering quality outcomes.?

Team supervisors are almost always participating in this stage. Changes to personnel or circumstances may cause a team to revert to an earlier stage.

Emotions

In this stage, team members feel confident and driven. By this point they feel competent doing their work, are driven to continue to make a valuable contribution to the outcomes of the team.

Behaviour

Team members will feel confident enough to express their opinions, leading to greater collaboration and investment in the team. Conflict will (and should) come up in this stage, but it will need to be in a form that the team finds acceptable. That might be a rigorous debate as long as there’s no yelling, or short, sharp feedback sessions that still acknowledge good intentions and good work.?

Tasks

The key tasks for team development in this stage are:

  1. Continuing to achieve team goals and deliver strong outcomes.
  2. Having confidence in the efficacy of ways of working.
  3. Free expression of ideas.

Stage 5: Adjourning

As mentioned, the fifth stage of Adjourning was added by Tuckman and Mary Ann Jensen in 1977. This stage involves breaking up the team after the work is completed.

Emotions

In this stage, team members will feel closure and loss. If a team has successfully gone through the other stages of development, disbanding may create a sense of loss. People will often reflect on the value of their contribution to the team as a whole in this stage.

Behaviour

Team members move into different places or initiatives, and must remember their learnings from the completed project. Carrying these forward into new opportunities within a business will create a collective cultural memory, which will influence any newcomers into the organisation.?

Tasks

The key tasks for team development in this stage are:?

  1. Disbanding the team in a way that still retains knowledge—particularly of successful ways of working.
  2. Concluding the work in a way that brings closure.
  3. Maintaining relationships from the project.

Some considerations

A few thoughts to consider with the model:

  1. A team member joining or a change in leadership can send the team back to forming or storming.?
  2. In software development, high performing teams will swarm as they come together. Swarming?

Leadership Considerations by Stage

Below are some examples of leadership strategies to facilitate team development.?

No alt text provided for this image

**

This post originally appeared on Terem.Tech.

要查看或添加评论,请登录

Scott Middleton的更多文章

  • AI for Boards of Non-Tech Companies

    AI for Boards of Non-Tech Companies

    I’m asked regularly to share my thoughts on AI for a Board so I’ve developed a presentation that I use. Rather than…

    2 条评论
  • Returns from Product Development: A Case Study

    Returns from Product Development: A Case Study

    The way a business undertakes product development is driven by the types of returns it and its shareholders are looking…

    8 条评论
  • Returns from Product Development

    Returns from Product Development

    A business needs to see that the investments it makes are driving a financial return. This sounds simple but “desirable…

  • REST API File Upload Best Practice

    REST API File Upload Best Practice

    Uploading files to an API might seem like a solved problem, and mostly it is, but the trick is selecting the best…

  • API Design Guidelines: Essential Elements

    API Design Guidelines: Essential Elements

    The best API builders globally have API Design Guidelines to help them guide the development and design of their APIs…

  • Architecture Patterns for App Modernisation

    Architecture Patterns for App Modernisation

    When you are modernising a software application the architecture patterns you will use to evolve from where you are to…

    1 条评论
  • App Modernisation: An Overview

    App Modernisation: An Overview

    App Modernisation is a popular topic, particularly in older organisations although it is also used with increasing…

  • Tech Spinout Equity Guide (Part 4): Spinout Cap Tables

    Tech Spinout Equity Guide (Part 4): Spinout Cap Tables

    Spinout cap tables have some unique aspects to them. Spinout cap tables are a little different to venture-style startup…

  • Tech Spinout Equity Guide (Part 3): Private Equity Review

    Tech Spinout Equity Guide (Part 3): Private Equity Review

    When structuring equity in a tech spinout there are lessons that can be learned from private equity’s approach to cap…

  • Tech Spinout Equity Guide (Part 2): Startup Cap Table Review

    Tech Spinout Equity Guide (Part 2): Startup Cap Table Review

    The structure of a typical venture-style startup is essential to keep in mind when structuring the equity and cap table…

    1 条评论

社区洞察

其他会员也浏览了