The Best Person for the Job Isn't Always the Best Person for the Team

Hiring usually means finding the best person for the job. Define the role, list the required skills and experience, then evaluate candidates against that list. Whoever has the strongest mix of expertise, experience, and accomplishments wins.

It's intuitive. It's also built on an assumption: that the individual is the right unit of analysis.

What if the question isn't "who's the most capable candidate?" but "who would make the team more capable?"

The difference sounds small. The hiring decision it produces often isn't.

Peter and Louise

We've used a simple scenario for years to help leaders think about this differently.

Imagine you're hiring for an open role, and it's come down to two candidates. Peter has deep, directly relevant expertise — his background maps closely to the job description. Louise is just as capable, but her path is less conventional. She brings relevant skills too, plus experiences and perspectives the team doesn't already have.

Most hiring managers pick Peter.

We'd push back on that.

The reason shows up once you stop evaluating candidates on their own and start looking at the team they're joining. If Peter's expertise already exists on the team, hiring him reinforces a strength the team already has. Louise's expertise might push the team somewhere new.

We call this expanding the box.

What’s Actually in the Box

Think of the box as everything a team can draw on: its expertise, experience, perspectives, networks, and ways of approaching problems and making sense of the world.

Every person adds something to it. But not every hire makes it bigger.

Organizations can end up with teams full of exceptional people whose expertise and experience largely overlap. Each hire looks great on paper. Collectively, though, the team keeps operating within the same boundaries.

Expanding the box means looking at what a candidate brings and what the team already has.

Maybe the team has deep technical chops but little experience bringing products to market. Maybe everyone built their career in the same industry. A candidate who's worked across very different environments may spot patterns others miss. A neurodivergent teammate may process information or approach problems differently. Someone from a seemingly unrelated discipline may create connections no one saw coming.

The goal isn't difference for its own sake. It's understanding which additions expand what this particular team can see, consider, and do.

That's the idea at the heart of The Medici Effect: extraordinary things happen when different fields, disciplines, experiences, and perspectives intersect. More of the same expertise deepens what we already know. Something different expands what's possible.

The same principle applies to building teams.

Adding Louise Isn't Enough

There's another part of the Peter and Louise story that matters.

Hiring Louise doesn't automatically expand the box.

If the rest of the team shares similar experiences and ways of thinking, what she brings may struggle to gain traction. Her perspective gets heard, but it doesn't move the work. Over time, the pull of the existing team can be strong enough that she adapts to how everyone else already thinks and operates.

The box hasn't really expanded at all.

That's why the next hire matters — not to compensate for something Louise lacks, but to keep adding capability while reinforcing what she introduced. Someone new might echo part of Louise's perspective while bringing something entirely their own.

Now the boundary moves again.

Seen this way, building a team is less about filling vacancies and more about making deliberate decisions about the capability of the whole. Each addition changes the context for the next.

Rethinking the Best Candidate

None of this diminishes expertise. People still need to be capable of doing the work.

But expertise is contextual. If five people already have a particular capability, adding a sixth may create less value than adding someone whose experience lets the team approach its work in ways it couldn't before.

Yet most hiring systems aren't built to see talent this way. We assess individuals against roles. We compare candidates to each other. We ask who has the strongest experience, who's done the job before, who most closely matches what we pictured when we wrote the job description.

Even when the team joins the interview process, the focus is often on compatibility: Will this person work well with us? Do they fit? Those are fair questions, but they tend to reinforce what's already there. We rarely ask the harder one: How might this person expand what the team is capable of?

Those processes are good at finding Peter.

They're not as good at recognizing why the team might need Louise.

Building collective capability means looking at both. The individual still matters — but so does the system they're entering. The question isn't just what someone brings. It's how what they bring changes what's already there.

So maybe the goal isn't always finding the person who fits most completely inside the box we've already drawn.

Sometimes the better hire is the one who helps us expand it.