Skip to main content

Building & Leading High-Performance Teams

Module: Module 3 — Strategy & Senior LeadershipCode: BLHPT (MVI)Faculty: Prof. Mit VachhrajaniSessions: 2Status: ✅ Drafted

Big idea​

Prof. Mit Vachhrajani frames high-performance teams as small groups with complementary skills, shared commitment to a common purpose, performance goals, and approach for which they hold themselves mutually accountable — Katzenbach & Smith's working definition. The journey is sequential: Bruce Tuckman's Forming → Storming → Norming → Performing → Adjourning model says teams must pass through productive conflict before they reach peak performance. Google's Project Aristotle measured 180 teams and found that who is on the team mattered less than how they work together — with psychological safety as the strongest predictor, followed by dependability, structure & clarity, meaning, and impact. The leader's job is to set a sharp goal, choose the right people, build psychological safety, surface and resolve conflict, and celebrate the win.

Key concepts​

  • What makes a team (Katzenbach & Smith). Small number, complementary skills, common purpose, common performance goals, common working approach, mutual accountability. If any of the six is missing, it's a working group, not a team.
  • Tuckman's stages of team development. Forming (polite, dependent on leader) → Storming (conflict, jockeying for role) → Norming (rules and norms agreed) → Performing (high autonomy, high output) → Adjourning (closure, celebration). Skipping Storming is the classic anti-pattern.
  • Google's Project Aristotle — five enablers. Psychological safety (most important), Dependability, Structure and clarity (roles, plans, goals), Meaning (work matters to me personally), Impact (work matters beyond me).
  • Belbin team roles. Nine roles in three clusters: Action-oriented (Shaper, Implementer, Completer-Finisher), People-oriented (Coordinator, Teamworker, Resource Investigator), Thought-oriented (Plant, Monitor-Evaluator, Specialist). Balance across roles predicts effectiveness.
  • Productive conflict (Lencioni's 5 dysfunctions, inverted). Absence of trust → fear of conflict → lack of commitment → avoidance of accountability → inattention to results. Building trust at the base unlocks the pyramid.
  • Leader's high-performance team checklist. Sharp shared goal, right people in the right roles, explicit norms, psychological safety, fast feedback loops, regular retrospectives, visible celebration of wins.

Self-check​

A leader prides herself on a 'no-conflict' team — meetings are pleasant, decisions are unanimous, no one raises objections. Quarterly delivery has been mediocre for three quarters. Through Tuckman + Lencioni + Project Aristotle, what is the most likely diagnosis?

  • A. Team is highly aligned
  • B. The team is stuck before Storming. The absence of visible disagreement signals either low psychological safety (people fear consequences of dissent) or absence of trust (Lencioni base of the pyramid). Without productive conflict the team cannot norm on real trade-offs, cannot commit because commitments were never debated, and cannot hold each other accountable — hence the mediocre output
  • C. Team needs more meetings
  • D. Team should focus on tasks not relationships
Katzenbach & Smith — definition of a team
Small number of people with complementary skills, committed to a common purpose, common performance goals, and a common working approach, for which they hold themselves mutually accountable. Missing any element — it's a working group, not a team.

Click the card to flip

1 of 4

Continue learning​

📄HBR · ReadThe Discipline of Teams (Katzenbach & Smith)The classic HBR statement of the team-vs-working-group distinction, with the six required elements that define real teams.📊Google re:Work · ReferenceProject Aristotle GuideGoogle's open guide on what makes teams effective — with the five enablers, ranked, and the operational definitions used in the study.🧰Table Group · ToolFive Dysfunctions of a Team (Lencioni)Patrick Lencioni's own working library on the dysfunction pyramid — absence of trust, fear of conflict, lack of commitment, avoidance of accountability, inattention to results.🧰Belbin · ToolBelbin Team RolesThe official Belbin library on the nine team roles — with the self-perception inventory used to map team composition and identify role gaps.
🪞 Apply it — reflection prompts
  1. Run Katzenbach's six tests on your current leadership team. Which element is weakest — shared purpose, common approach, mutual accountability — and what's the smallest change that would strengthen it?
  2. Where is your team in the Tuckman cycle? If meetings feel artificially harmonious, what's the first piece of dissent you could deliberately invite next week?
  3. Score your team on the five Project Aristotle enablers (1–5). The lowest score is your binding constraint — what one ritual would lift it in the next 30 days?

📝 Going deeper. Jon Katzenbach & Douglas Smith, The Wisdom of Teams (1993; updated 2015) remains the foundational text. Patrick Lencioni, The Five Dysfunctions of a Team (2002) is the most accessible diagnostic. Charles Duhigg's New York Times Magazine piece "What Google Learned From Its Quest to Build the Perfect Team" (Feb 2016) is the canonical Project Aristotle write-up.