Hiring and Building Teams

A leader rarely does the work alone; they assemble the people who will, and then shape how those people work together. This makes hiring one of the highest-leverage decisions a leader makes, because a single wrong seat can drag on a team for years, while the right addition can lift everyone around them. Yet most managers hire on instinct — favouring candidates who impress in a conversation or who remind them of themselves — and are then surprised when a group of talented individuals produces mediocre results.

The deeper lesson is that a team is not the sum of its résumés. How members treat one another, whether they can disagree openly, and whether they feel safe admitting they are stuck often matter more than any individual's brilliance. Building a team, then, is two jobs at once: choosing who joins, and creating the conditions under which their strengths actually surface.

Hiring for complementary strengths

Strong teams are built from people whose strengths cover one another's gaps, not from clones of the best performer. A team of five brilliant strategists with no one who ships daily work will stall. Before hiring, a leader should name what the team actually lacks — a skill, a temperament, a perspective — and hire against that gap. This is different from the common instinct to hire the most generally impressive person in the room.

Fit without sameness

"Fit" is one of the most misused words in hiring. Useful fit means shared standards: how carefully people work, how they handle disagreement, whether they follow through. It does not mean shared background, hobbies, or personality, and confusing the two quietly builds a uniform team that cannot see its own blind spots. Structured hiring — asking every candidate comparable questions tied to the real work — reduces the pull toward hiring people who simply feel familiar.

Team dynamics and roles

Once people are in the room, dynamics take over. Who speaks and who stays quiet, whether credit is shared, how conflict is handled — these patterns determine whether the group's combined judgement is better or worse than its members'. Clear roles help: when people know what they own, they stop competing for the same ground and start covering more of it.

Psychological safety

Psychological safety is the shared belief that it is safe to take interpersonal risks — to ask a naive question, admit an error, or challenge a decision — without being punished or humiliated. It is not the absence of standards; high-safety teams often hold very high standards. Rather, it is the condition that lets skill, honesty, and dissent reach the surface instead of staying hidden behind fear.

A product team keeps missing deadlines. The manager's first instinct is to hire another senior engineer. Looking closer, she sees the team already has strong builders but no one who tests assumptions with customers, so they build the wrong things quickly. She hires for that gap instead. She also notices junior members never flag problems until it is too late, so in the next retrospective she publicly thanks someone for surfacing a mistake early. Over a few weeks, problems start being raised sooner — the team's real bottleneck was silence, not headcount.

Psychological safety is not comfort or the avoidance of hard conversations. A team where no one is ever challenged, where weak work is praised to keep the peace, feels pleasant but drifts. Real safety pairs with directness: people can be told their work missed the mark precisely because the relationship can survive the honesty. A group that mistakes niceness for safety lowers its standards and calls it kindness.

Between roughly 2012 and 2016, Google ran an internal research effort commonly known as Project Aristotle to identify what made some of its teams more effective than others. The researchers expected the answer to lie in who was on the team — seniority, individual talent, or personality mixes. Instead, they reported that group norms mattered more than group composition, and that psychological safety stood out as the most important factor distinguishing higher-performing teams. The concept drew on earlier academic work by Harvard's Amy Edmondson, who studied how safely people could speak up on medical and other teams. As with any single company's study, these findings come from one organisation and are best read as a strong, widely echoed pattern rather than a universal law.

• "Hire the most impressive person available." Hire against the gap your team actually has; impressive in isolation can still be redundant.
• "Fit means people like us." Useful fit is shared standards, not shared personality or background.
• "Psychological safety means being nice." It means it is safe to take risks and be honest, which often raises standards.
• "A team is just its best members." Dynamics and norms can make a group perform far above or below its individual talent.

Given a team with a stated goal and a set of gaps, choose who to hire and which norms to reinforce, then watch how each decision shifts the group's speed, honesty, and results.

Think Like a Maester: A team's real strength is not the talent it contains but the truth it is willing to say out loud.

1. Why should a leader hire against a team's gaps rather than for the most generally impressive candidate?
2. What is the difference between fit as shared standards and fit as sameness?
3. What is psychological safety, and why is it not the same as being nice?
4. What did Google's Project Aristotle report as the most important factor distinguishing effective teams?
5. How can team dynamics make a group perform worse than its individual members?

Building a team is two jobs: choosing who joins and shaping how they work together. The best hiring targets complementary strengths and shared standards rather than the most impressive individual or the most familiar personality. Once people are in place, dynamics and roles decide whether their strengths combine or collide — and psychological safety, the shared sense that honesty and risk are safe, is what lets those strengths surface at all. Google's Project Aristotle offered strong evidence that how a team behaves matters more than who is on it, a pattern echoed well beyond one company.

• Teams, Leadership, and Culture
• Leading Through Communication