Hiring for Capability vs Hiring for Comfort
Why the people who feel “right” aren’t always the ones who move the system
In my last piece, I wrote about Talent Acquisition as an operating system. Today, I want to zoom in on one of the most common ways that system fails: by hiring for comfort instead of capability.
Most leaders don’t do this intentionally. In fact, the decisions often look quite rational. CVs are strong. Interviews go well. References check out. “I could work with this person” comes up a lot.
And yet, a few months later, the bottleneck hasn’t moved.
I’ve seen people resign after weeks, and once, I even had a team member ghost five days after starting. When that happens, it’s rarely because the hire was “bad.” It’s usually because the leader hired to reduce their own anxiety, rather than to remove a real constraint.
What “Comfort Hiring” actually is
Comfort hiring is a stress response. Under pressure, our biology naturally leans toward psychological safety. We look for people who feel familiar, predictable, and easy to integrate.
Comfort hires usually:
Speak the same language as leadership.
Mirror existing strengths (and existing blind spots).
Reduce anxiety in the moment.
Fit neatly into the current, already-strained rhythms
None of this is irrational. It’s human. But a system that only hires for comfort ends up very stable (and very stuck).
Capability hiring feels uncomfortable by design
Capability hiring starts from a different question: What does this system actually need in order to move?
Instead of focusing on titles or experience, it looks at what someone can do. It assesses whether their strengths can transfer into a complex, less-defined environment.
True capability hires:
Remove a specific constraint.
Surface gaps leaders have been ignoring or avoiding.
Ask inconvenient questions in interviews.
They don’t immediately feel safe because they disrupt rhythms and force fuzzy ownership to be clarified. That discomfort is usually the signal that something important is about to change.
Why role-based hiring breaks under complexity
Role-based hiring works when the system is stable and work is repeatable. But under growth or restructuring, roles lag reality.
Hiring “a Head of X” doesn’t fix the problem if the real issue is administrative debt—the invisible pile of decisions, vague priorities, and bottlenecks upstream. If you hire a “safe pair of hands” to handle a messy process, you haven’t solved the mess; you’ve just hired someone to watch it with you.
Hiring as a response to constraints, not headcount
Most organizations ask: Who do we need next? Capability-driven hiring asks:
Where does work pile up?
What decisions are endlessly escalated?
What are we compensating for manually?
Then you hire for that capability. Not for titles. Not for symmetry.
A simple reframe before you approve a hire
Now, I invite you to reflect before signing off on your next opening. Pause and ask:
What constraint does this person actually remove?
What decision will move faster because they’re here?
If nothing changes systemically, why are we hiring at all?
If the answer is “they’ll help”—pause. If the answer is “they’ll change this”—you’re closer.
Hiring for comfort keeps the system feeling stable. Hiring for capability is what actually makes it resilient. And under pressure, resilience matters far more than familiarity