Building and leading teams

Welcome to Building and Leading Teams!

Hello! Welcome to one of the most practical and interesting chapters in the E2 curriculum. In this section, we move from the "what" of performance to the "who." After all, even the best strategy in the world won't work if the people expected to carry it out aren't working well together.

Don't worry if you’ve ever found "people management" a bit fluffy compared to financial accounting. This chapter provides clear, structured frameworks that explain exactly how groups turn into high-performing teams. Let’s dive in!

1. Groups vs. Teams: What’s the Difference?

In everyday conversation, we use these words interchangeably. But in the CIMA E2 exam, there is a very specific difference.

A Group is just a collection of people who may interact but don't necessarily have a shared goal. Think of people waiting at a bus stop. They are in the same place, but they aren't helping each other catch the bus!

A Team is a small number of people with complementary skills who are committed to a common purpose and hold themselves mutually accountable.

The "Magic" of Synergy:
The reason we build teams is to achieve synergy. This is the idea that the output of the team is greater than the sum of the individual parts.
Analogy: If one person can lift 50kg, and another can lift 50kg, synergy is when they work together to lift 120kg. In a team, \( 1 + 1 = 3 \)!

Quick Review: Characteristics of an Effective Team

• Common goals: Everyone knows where they are going.
• Shared values: A common culture and way of working.
• Complementary skills: Members have different strengths that fit together.
• Mutual trust: People feel safe to speak up and take risks.

2. How Teams Grow: Tuckman’s Stages of Development

Teams don't just "happen" overnight. They go through a predictable lifecycle. Bruce Tuckman identified five stages that almost every team goes through.

Memory Aid: Use the "5 -ing" words: Forming, Storming, Norming, Performing, and Adjourning.

Stage 1: Forming

The team is just meeting. Everyone is on their best behavior, but people are often anxious and unclear about their roles.
Key focus: Defining the task and getting to know each other.

Stage 2: Storming

This is where the "honeymoon phase" ends. Members start to compete for positions, challenge the leader, and disagree on how to do things.
Key focus: Resolving conflict and clarifying expectations. Don't worry if this seems tricky! Conflict is actually a sign of progress in this model.

Stage 3: Norming

The team starts to settle down. They agree on "norms" (unwritten rules) about how to work together. Trust begins to build.
Key focus: Cooperation and developing working methods.

Stage 4: Performing

The team is now a "well-oiled machine." They are focused on the goal and work together seamlessly. The leader can step back and let them get on with it.
Key focus: Achieving results and high productivity.

Stage 5: Adjourning (or Mourning)

The task is finished, and the team breaks up. This can be a sad time if the team worked well together.
Key focus: Reviewing performance and saying goodbye.

Common Mistake to Avoid: Many students think "Storming" is a failure. It’s not! It’s a necessary stage to get to "Performing." If a team never storms, they might be "Groupthinking" (just agreeing to avoid trouble), which is bad for performance.

3. Who Does What? Belbin’s Team Roles

Have you ever been in a team where everyone wanted to be the boss? Or a team where everyone had great ideas but no one actually did the work? Meredith Belbin argued that for a team to be successful, it needs a balance of different roles.

Belbin identified nine roles, grouped into three categories:

Action-Oriented Roles

• Shaper: The "engine" of the team. They challenge others and push for results.
• Implementer: The "organizer." They turn ideas into manageable tasks and schedules.
• Completer Finisher: The "perfectionist." They check for errors and ensure the project is finished on time.

People-Oriented Roles

• Coordinator: The "chairperson." They clarify goals and delegate work.
• Teamworker: The "glue." They listen, build relationships, and reduce friction.
• Resource Investigator: The "networker." They look outside the team for ideas and resources.

Thought-Oriented Roles

• Plant: The "creative genius." They come up with original (but sometimes impractical) ideas.
• Monitor Evaluator: The "judge." They analyze ideas logically to see if they will work.
• Specialist: The "expert." They provide deep technical knowledge in a specific area.

Key Takeaway: A team doesn't need nine people. One person can play more than one role! The important thing is that all roles are covered and the team is balanced.

4. Leading the Team

Building a team is one thing; leading it is another. In the E2 syllabus, we focus on how a leader manages performance within the team environment.

The Leader's Role in Building the Team

1. Setting the Vision: Giving the team a "North Star" to follow.
2. Allocating Roles: Using Belbin’s ideas to put the right people in the right spots.
3. Facilitating Communication: Ensuring information flows freely.
4. Removing Obstacles: Handling the politics or resource issues so the team can work.

Did you know?

High-performing teams often have a "Shared Leadership" model where different people take the lead depending on the situation. For example, the Specialist might lead during a technical crisis, while the Coordinator leads during the planning phase.

5. Potential Pitfalls in Team Performance

Even with great people, teams can fail. Watch out for these terms in your exam:

1. Social Loafing (The "Free Rider" Effect):
This happens when an individual puts in less effort because they are part of a group. They think, "Someone else will do it."
How to fix: Make individual contributions visible and hold people accountable.

2. Groupthink:
This happens when the desire for harmony is so strong that the team ignores better ideas or ignores risks just to avoid an argument.
How to fix: Encourage a "Devil's Advocate" to challenge ideas (the Monitor Evaluator role is great for this!).

Summary Checklist

Before you move on, make sure you can answer these questions:

• Can I explain the difference between a group and a team?
• Do I know the 5 stages of Tuckman’s model in order?
• Can I name at least one role from each of Belbin’s three categories?
• Do I understand why "Storming" is a normal part of development?
• Can I define Social Loafing and Groupthink?

You’ve got this! Understanding teams is as much about common sense as it is about theory. Think about your own experiences in study groups or at work, and these concepts will stick much better. Happy studying!