On this website we use cookies that are strictly necessary to make our website function correctly, as well as optional – analytics, performance and/or marketing - cookies which help us improve our website by collecting and reporting information on how the website is used, as well as help us to reach out to you with information about our organization or offer. If you do not wish to accept optional cookies when visiting our website, you may change the settings in the Cookie Settings. For more information go to Cookie Settings.

Skip to content

The evolution of a team - part 3

Dec 17, 2015 - 5 minutes read

Objectivity Blog 416 306
Paweł Słowikowski
Scrum Master by trade, Trainer by choice, Human Being from birth. Interested in agile methodologies and leaning towards Lean. More than 8 years of experience in a multi-cultural IT projects, including 5 years as a Scrum Master and 1 year as an Agile Coach. Over 300 hours as trainer of Agile methodologies and soft-skills. Currently supporting front-line agile projects in Objectivity.
See all Paweł's posts
Data Driven Organisation Blog Ebook 416X300


Sturm und Drang


“Share our similarities, celebrate our differences.” – M. Scott Peck

“Hey, I have an issue with my new team. Last week they were all exchanging stories about their previous projects, smiling and walking to lunch together and now they are all speaking ill of each other, shouting and now two guys have even stopped talking to each other. What the %$#@ is going on?”

Relax, you are now in a very special place called ‘Storming’.

After the initial phase of getting to know each other, some interesting things will happen. First of all, group members will start to work on their tasks and inevitably they will notice some interdependencies. This will lead to the realization that there are different ideas on how to solve some problems or complete tasks. Second of all, people in the group will test the boundaries around them more and more. They will expose more of their ‘true self’ to the rest of the group and eventually touch sensitive subjects (related to personal values, identity, mission statements, etc.). And lastly, different roles will start to emerge – leaders, supporters, rebels and others. This will lead to a phase where conflicts will spring to life. It will be a difficult time for both the leader and the team. It is, however, essential not to try to quench it before it fully runs its course. This is the cleansing fire that the team needs to go through in order to reach high efficiency.

This phase of group development is called Storming, Conflict, Fighting and Interdependency. Most of the researches of the linear model agree that at some point in the evolution of the team, conflicts, different points of view and individualism will start to play a significant role. Many argue that this phase cannot be avoided – that a group of people will eventually go through this conflict phase, given enough time. In my experience, this phase is the most critical one on the journey to high performance.

During this period of time, the team members learn that they are different. Obviously, adult people already know that, but it is one thing to know that people are generally different and another to face those differences in daily work AND accept them. To build an effective team working for a common goal, people must rely on each other’s strengths, weaknesses and understand AND appreciate their differences – especially in the areas such as values, skills, identity, life mission and even spirituality. Also, by disclosing more and more personal information, sharing personal dreams, goals and values builds up TRUST – an essential ingredient needed to move forward in team evolution.

Let’s go back to the team that I have mentioned in the previous chapter. The one consisting of new people with little or no experience. It was an amazing experience for me to witness such diversity of characters gathered in one place. After some time I spent getting to know them it was clear to me that those different characters and their values will eventually clash. One person was a ‘delivery and speed’ type of person, the other was more of a ‘hold on, don’t forget the quality’ personality. Those two different approaches led to many quarrels (sometimes fierce ones) and the rest of the team started to polarize and took a stand by the first or the second leader. What I did was a series of workshops/discussions and individual feedback sessions to help the team members aware that their strength as a team comes from BOTH approaches and that we should take care about both quality and delivery. This was an easy-to-solve conflict in comparison to the second example below.

With the same team I went through what turned out to be THE most intense conflict that I have experienced (so far) in my professional career. It circulated around… places to sit! What at first amused me (what? Can’t you just switch places?) quickly escalated into a fierce war that spread out across the whole team. After a day of quarrels, I took the whole team to a separate room and told them that we won’t come out unless the situation is resolved because it was killing us. And after an hour of really intense discussions (things almost got physical…) and my mediation/moderation (and at that point I doubted that we will ever end up with a solution), one of the team members came up with a solution that was a win-win for everyone. And that was the beginning of the Norming phase (more about it in the next part).

What I have learned from this experience is that you will never know what kind of individual values the team members will protect and to what extent that they will fight with the world for them. It might be something important from your perspective (quality of code) or trivial (places to sit), but it will sure be important to them. You need to observe the situation and react accordingly. Listen, try to understand and help the team to get through this.

How to recognize this phase?

  • Internal conflicts – people are defending their ego, individualism, point of view and values. Emotions run high. It is a time of struggle between the need for being a part of the group and to keep the individual position
  • Leaders emerge and clash – team members take sides, assume other roles and sometimes ‘overthrow’ their leaders. I recommend reading “Trening Interpersonalny” by K. Jedliński (for group roles) and M. Belbin’s work for team roles (along with a questionnaire to check the role you assume).
  • Informal rules, processes and practices emerge and are challenged – along with the initially set boundaries and frameworks
  • Conflict with the external leader/manager – be careful here. It is easy to conflict yourself with the emerging team in this phase. Support them, coach them, but also give them enough room to establish their own rules.

Here are some advice on the do’s and don’ts when going through this difficult stage with your team:

Do Don’t
  • Celebrate success! Due to association principle, people are eager to associate themselves with the success of others [Cialdini, Influence]. This will help the team members to feel more accepted in the group.
  • Take care of a safe environment where conflicts can be managed and solved
  • Coaching and training (soft-skills, feedback, assertive communication)
  • Encourage Win-Win attitude (by own example)
  • Ensure proper communication practices:
    • Talk about mutual needs
    • Focus on facts but don’t neglect emotions
    • Active listening
    • Frequent constructive feedback
    • Appreciations
    • Non-violent communication
  • Retrospective sessions that focus on appreciation of differences and mutual understanding of needs
  • Help to solve escalated conflicts
  • Show the difference between conflicts around tasks (good) and personal conflicts (bad)
  • Use tools to talk about values and strengths and how to help the team recognize and appreciate their differences:
    • StrengthsFinder
    • Abigale’s dilemma (careful about that :)
    • M. Belbin team roles
    • Moving Motivators (J. Appelo)
  • Quench every smallest conflict personally
  • Take sides
  • Start conflict with the group (sometimes unavoidable)
  • Impose your rules
  • Avoid feedback
  • Use your authority/power to solve conflicts
  • Panic
  • Escalate difficult situations too early
  • Ignore the whole situation
  • Focus only on tasks and ignore the emotional side
Data Driven Organisation Blog Ebook 416X300
Paweł Słowikowski
Scrum Master by trade, Trainer by choice, Human Being from birth. Interested in agile methodologies and leaning towards Lean. More than 8 years of experience in a multi-cultural IT projects, including 5 years as a Scrum Master and 1 year as an Agile Coach. Over 300 hours as trainer of Agile methodologies and soft-skills. Currently supporting front-line agile projects in Objectivity.
See all Paweł's posts


Start your project with Objectivity

CTA Pattern - Contact - Middle