You hire the candidate with the best qualifications. They're technically excellent. But somehow the team gets worse, not better.
I've seen this happen so many times it barely surprises me anymore. A hiring manager calls me two months after making what they thought was a brilliant hire, and says, "I don't understand. On paper, they're the strongest person on the team. But the team dynamic has deteriorated."
What happened? They hired for individual capability without considering team composition. And that's one of the most common — and costly — hiring mistakes I encounter.
Why Strong Hires Sometimes Weaken Strong Teams
Teams need all four work styles to function well:
- Reasoning for analysis and quality
- Creating for innovation and possibility
- Relating for cohesion and communication
- Doing for execution and results
Most teams over-index on one or two styles — often reflecting the leader's own preference — creating blind spots that nobody notices until things start breaking down.
Let me give you an example. I was working with a software development team at a tech firm in Petaling Jaya. The team lead was a strong Reasoning type, and over three hiring rounds, he'd built a team of five — all strong in Reasoning. Their code quality was exceptional. Their technical discussions were sophisticated. But they couldn't ship anything on time, struggled to communicate with stakeholders, and had almost zero creative problem-solving when requirements were ambiguous.
He didn't have a performance problem. He had a composition problem. And no amount of process improvement was going to fix it.
Diagnosing What You Actually Need
Before hiring, assess what you have:
Over-indexed on Reasoning: Deep analysis, slow decisions, potential paralysis
Over-indexed on Creating: Many ideas, poor execution, constant pivots
Over-indexed on Relating: Strong relationships, unclear direction, conflict avoidance
Over-indexed on Doing: Fast execution, strategic gaps, potential burnout
What style is underrepresented? That's what you need most. Not necessarily the most technically skilled candidate — the candidate who brings the perspective your team is missing.
A Four-Step Approach to Balanced Hiring
Step 1: Map Your Current Composition
Assess each team member's work style. Create a visual of where you're heavy and light. This doesn't need to be complicated — even a rough mapping gives you useful signal.
Step 2: Name the Gap
Which perspective is missing? What problems recur because no one naturally catches them? If your team keeps generating ideas but struggling to execute, you probably need Doing energy. If decisions take forever, you might be short on Doing or Creating types who push for resolution.
Step 3: Screen for the Gap
Add style considerations to your hiring criteria. Technical skills remain important, but add: "Ideally brings strong Reasoning/Creating/Relating/Doing orientation." Make it explicit, not just a vague feeling during the interview.
Step 4: Interview With Style in Mind
Ask questions that reveal work style:
- "Walk me through how you approach a complex problem" (reveals Reasoning)
- "Tell me about a time you proposed something unconventional" (reveals Creating)
- "How do you build relationships with new teammates?" (reveals Relating)
- "Describe how you push projects to completion" (reveals Doing)
Listen not just to their answers but to how they answer. What energises them when they talk? What do they gravitate toward? That tells you as much as the content of their response.
The Hiring Traps I See Most Often
Cloning yourself. This is the big one. Hiring people who think like you is comfortable but creates blind spots. I've watched entire leadership teams wonder why they keep hitting the same problems — and it's because they all approach problems the same way. But how many hiring managers are honest enough to admit they prefer candidates who remind them of themselves?
Skills-only focus. Technical qualifications matter, but they don't predict team fit. A brilliant individual contributor who disrupts team function is a net negative.
Ignoring dynamics. Every addition to a small team shifts the entire composition. Hiring without considering that shift is like adding an ingredient to a recipe without tasting first.
Assuming adaptability. People can stretch, but they shouldn't have to fight their nature constantly. Hiring someone and expecting them to operate outside their natural style indefinitely is unfair to them and unproductive for you.
When Balance Matters Even More
Small teams. With few people, each addition dramatically shifts composition. One hire can transform the dynamic — for better or worse.
Cross-functional work. Teams that need all capabilities represented must have style diversity. A cross-functional team stacked with one style isn't really cross-functional.
Innovation challenges. Teams stuck in patterns need styles that break them. If you've been doing things the same way and getting diminishing results, you don't need more of the same.
Execution challenges. Teams that generate but don't deliver need styles that finish. Ideas without execution aren't innovation — they're noise.
Your Role as the Hiring Manager
This is where most organisations get it wrong. They treat hiring as an HR process when it's fundamentally a team design decision. As the hiring manager:
- Know your own style biases — you'll unconsciously favour similar candidates unless you actively check for it
- Involve team members with different styles in interviews — they'll notice things you miss
- Make style fit explicit in hiring criteria — write it down, don't just keep it in your head
- Be willing to choose the "less similar" candidate when balance requires it — this takes discipline, but it's where the real team-building happens
The Team That Performs Beyond Its Parts
Teams built for balance outperform teams built for individual excellence. They catch each other's blind spots, compensate for weaknesses, and produce results that homogeneous teams cannot.
The best hire isn't always the most qualified candidate. It's the candidate who makes the whole team better. I've seen mid-level hires elevate an entire team's performance because they brought the missing perspective — and I've seen star hires drag a team down because they amplified an existing imbalance.
The bottom line is this: hire for the team you need, not just the role you're filling.
