Performing teams

 

Great things in business are never done by one person. They’re done by a team of people.

Steve Jobs

The first teambuilding I was involved in as a facilitator was in 1988; it was a week-long outdoor based event for the twelve-member management team of the Rolls-Royce training department.

Since then, I have lost count of the number of teambuilding’s I have been involved in; I have run them for corporate giants, SME’s, start-ups and charities, I have run them for Boards of Directors, Business Unit Management Teams, Project teams and sales teams; in Europe and North America and I have run them in both English and French.

Tuckman’s famous, “Forming, Storming, Norming, Performing” was my reference in my early years along with Cog’s Ladder (a model of team growth) and the work of people like Fisher on small team decision making. In the early nineties I discovered Jones’s Team Development Matrix, which I considered to be a two-dimensional version of Tuckman’s approach; this became “my model” for numerous teambuilding’s and is still something that I use today to help teams understand how they function – the model is an excellent example of how “an image paints a thousand words”.

So, is there a “road” that will lead to the high performing team?

Coming together is a beginning. Keeping together is progress. Working together is success

Henry Ford

Clearly, high performance within in a team isn’t instantaneous; a collection of disparate individuals needs time to become a cohesive and supportive whole, heading in a common direction. The journey from “forming” to “performing” is not linear, it is not timebound and the destination is always changing.

Virtually all team development models identify four common “phases” or “configurations” that teams go through in their search for the holy grail of team performance.

An initial phase of getting to know one another and understanding what the team is about.

The starting point for new teams. Depending on the model chosen this phase goes under a variety of names, forming phase, polite phase, orientation phase, etc. Team members will be attempting to learn what the organisation expects of them as a functioning team, what their tasks are, how to do them and what the standards are. In this low level of team maturity phase, low levels of task productivity and a great deal of leader dependency can be expected.

Team members will generally be mildly to moderately eager to engage, have generally positive expectations, and show some anxiety about the task and each other.

You can expect to see a certain lack of involvement & commitment, one-way communication, hidden feelings and poor listening.

During this phase the Leader needs to be “out in front”, providing a vision for the team and clarifying expectations about how the team process will be initiated. Communication will be primarily one-way from team leader to team members.

Time needs to be allowed for team members to get to know one another, build a shared purpose/mission and continuously clarify team outcomes while working on personal commitment by linking personal goals to team roles; this will help the team to start to move forward on its journey.

Action steps for moving forward

  • Build a shared purpose/mission and continuously clarify team outcomes.
  • Create a sense of urgency and rationale for the purpose/mission.
  • Invest time in allowing team members to share skills, experience and personal goals.
  • Bring individuals together to work on common tasks.
  • Define recognition and rewards, both individual and team-based.
  • Work on personal commitment by linking personal goals to team roles.

A divergence phase where “like-minded” sub-teams or cliques are formed.

Storming or Bid For Power, depending on the chosen model, begins when team members begin to engage with the team and the task. Members put forward ideas about how things should be, and a kind of power struggle takes place. If there is a designated team leader, that person may be challenged. Storming may seem like an uncomfortable or unwelcome process, but it is necessary before the team can settle into a generally accepted way of doing things. Without it, members would be disengaged from the team and unclear about where they stand in relation to the team. Work or tasks during this phase are often executed by cliques or sub-teams within the team, hence the term “Fragmented Team” in the Jones Model and “Conflict” in the models of Tubb’s and Fisher.

Success is often due to the efforts of a “clique” and is not a real collective success.

You would expect to see a lack of cohesion, inconsistency, conflicts with team members appearing confused and expressing concern about the objectives or the organisation of the team.

In order to move the team forward, it is important to pull the “fragments” of the team together in order to achieve a collective rather than individual output. Team members need to be encouraged to express their differing opinions, ideas, and feelings so as to raise issues, confront deviations from commitments and make connections between divergent perspectives. Realistic targets need to be set for the team to enable them to start achieving performance goals and tasks.

The team leader needs to concentrate less on being “out in front” and become a “facilitator” helping them focus on goals & expectations, managing process and conflict, generating ideas, and explaining decisions.

Action steps for moving forward

  • Build a common understanding by periodically communicating the team’s purpose/mission.
  • Acknowledge times when the team is struggling and take time to discuss ways to move toward “Cohesive group.”
  • Set out to achieve a few performance goals and tasks.
  • Encourage members to express their differing opinions, ideas, and feelings by asking open-ended questions.
  • Make connections between divergent perspectives; acknowledge where there are differences.
  • Build a set of operating agreements (rules for team behaviour).
  • Raise issues, confront deviations from commitments, and allow conflict to occur.

A coming together phase with a realisation that the team needs to share in order to move forward.

This, “Norming” or “Cohesive” phase is where the team begins to generate its own culture or accepted understandings about how things are done. Team norms may be overt and written, like ground rules, or unspoken, unacknowledged practices that arise. It is in this phase of the team’s development that the individuals start to feel like a “collective.” Team members share information, ideas and perceptions as they emerge and a consensus is sought as to how to become truly effective.

In this phase the leader is more “alongside”, acting primarily as a coach providing encouragement, helping to build consensus, and giving feedback.

Action steps for moving forward

  • Develop shared leadership based on expertise and development needs.
  • Translate common purpose and team expectations into performance goals that are specified and measurable.
  • Build consensus on overarching goals and approaches.
  • Formally give and receive feedback within the team.
  • Maintain focus on external relationships: commitments, requirements, feedback, and competitive realities.
  • Take risks by setting stretch performance goals while simultaneously encouraging the disclosure of fears.
  • Celebrate successes, share rewards, recognise team and individual achievements.

A final phase where the team is able to reconcile both individual and team needs

Once the team culture is established, the team can really start to work; ‘Performing’ in the terms of Tuckman, ‘Effective Team’ for Jones and the ‘Constructive’ phase for Cog.

A team, and its members, in this phase will have incorporated not only tasks and people needs, but also individual and collective needs. Leadership is often shared in this phase with the designated leader becoming more of a participant, but ready to stand-in when necessary. It is in this phase that the synergy created brings about an excellence which goes beyond the sum of the individual contributions.

Two relatively common configurations that teams can find themselves in are “Productive Team” and “Social Team”

Teams often find themselves in the productive team configuration when they have sacrificed the human element in favour of getting stuff done. The team will probably be producing under difficult interpersonal circumstances and be dependent on the formal team leader; they will probably rely on the over application of processes and procedures.

Low morale, lack of empowerment, resentment and, in many cases, high turnover are often the tell-tale signs.

Teams often find themselves in the social team configuration because they have overly concentrated on relationships to the detriment of delivering on their objectives. Team members tend to become tightly knit with a feeling of trust and ”we-ness” within the team; there is often a lot of interpersonal support and effective communication will usually exist but with little real task accomplishment.

The tell-tale signs are conviviality, understanding, sharing, mutual helping and cohesion; a certain degree of flexibility may be apparent.

The whole team development process is not a linear, mono-dimensional journey. Teams can accelerate, become derailed, fall-back, get lost and, in some case, implode and disintegrate.

What is paramount for the team leader is to be able to fully endorse the different “roles” or “styles” of leadership depending on where the team is in its development; out in front showing the way forward in the early stages, facilitating and creating “weeness” as the team starts to move forward, coaching from the side-lines to empower the team as it starts to become cohesive and finally aligned with the team when it becomes a performing team.

A single twig breaks, but the bundle of twigs is strong

Tecumseh, a Shawnee Indian chief

Collections of individuals or groups masquerading as teams can be found at all levels of an organisation; from the production team to the board team and everywhere in between – sales teams, project teams, support teams ….

Measuring a team’s performance and mapping its development is clearly not an exact science, if indeed it is a science at all. However, there are ample frameworks, models and research that can be used to contribute to concrete improvements in how people work together.

These models and frameworks integrated into a coherent team development process, as opposed to a series of “stand-alone activities” can significantly accelerate team development and performance and help teams through the critical stages of their life together.