I hired a specialist first, a genuinely skilled designer, when what my business actually needed was someone capable of handling design, basic customer support, and light operational work across a given week. She was excellent at design and visibly frustrated whenever I asked her to help with anything outside that lane, and I don’t blame her. I’d hired for a narrow skill set into a role that actually needed breadth, and the mismatch was mine to own, not hers.
This is one of the most common early hiring mistakes, and it’s rarely obvious in the moment, because specialists often look more impressive on paper, with clearer credentials and more polished portfolios in their specific area, than generalists do.
Why Specialists Feel Like the Safer, More Impressive Choice
A specialist candidate typically has a stronger, more focused portfolio in their specific area than a generalist would, since a generalist’s experience is spread across multiple functions rather than concentrated deeply in one. That concentrated strength is genuinely appealing when you’re evaluating candidates, and it’s also frequently the wrong signal to optimize for in a very early-stage hire, where the actual day-to-day need is breadth across multiple functions rather than deep excellence in just one.
I chose the specialist designer partly because her work was visibly more impressive than any generalist candidate’s portfolio, without stepping back to honestly assess whether the role I actually needed filled matched what her specialization offered.
The Actual Question: What Does the Role Genuinely Require Day to Day
The right choice depends entirely on the actual shape of the work, not on which type of candidate seems more impressive in isolation. If the role genuinely involves one deep, consistent function, sustained software development, for instance, or a specific, ongoing technical skill that the business needs applied consistently and expertly, a specialist is the right call, and hiring a generalist into that role often means real skill gaps in exactly the area that matters most.
If the role, especially a very early hire in a small business, genuinely requires flexibility across multiple different types of tasks throughout a typical week, customer support today, some operational work tomorrow, occasional involvement in a marketing task the day after, a generalist who’s reasonably capable across several areas will consistently outperform a narrow specialist who resents or simply can’t effectively handle the tasks outside their specific lane.
Why Early-Stage Businesses Usually Need Generalists More Than They Assume
The nature of early-stage work is inherently unpredictable and variable, and a role description written before the business has much operating history is often an incomplete guess at what the position will actually require once real day-to-day demands reveal themselves. A generalist’s adaptability handles that unpredictability naturally, while a specialist’s narrow focus, valuable once the business has scaled enough to genuinely need deep expertise applied consistently, can become a real limitation when the actual day-to-day work keeps shifting beyond their specific area.
My actual first-hire need, in hindsight, was clearly a generalist role. Design was one recurring task among several, not the role’s sole defining function, and I’d let an impressive portfolio in one specific area override an honest assessment of what the position actually needed across a typical week.
The Signs You Genuinely Need a Specialist, Even Early
To be fair to the other side of this, some early-stage needs genuinely are specialist needs. If a specific, technical function is both mission-critical and requires real depth of expertise that a generalist couldn’t reasonably develop or maintain, sophisticated software development, specialized regulatory compliance work, a highly technical production process, hiring a generalist into that role creates real risk in exactly the area that most needs deep competence. The distinguishing question is whether the function needs to be done deeply well, consistently, or whether it needs to be handled adequately alongside several other varied responsibilities.
How to Actually Diagnose Which You Need Before Hiring
Write out a realistic week of the role’s actual responsibilities before writing the job posting, based on genuine, honest observation of your current workload rather than an idealized, narrow job description. If that week genuinely centers on one deep function with occasional light tasks elsewhere, hire the specialist. If that week genuinely spans several different types of tasks with no single function dominating, hire the generalist, even if the generalist candidates in front of you look less immediately impressive than a narrow specialist’s polished portfolio.
What I’d Tell Someone Making Their First Hire Today
Resist being swayed by an impressive, narrow portfolio if the actual role you need filled genuinely requires breadth. A generalist who handles four different types of tasks adequately is often more valuable in an early-stage business than a specialist who handles one task excellently and struggles with, or resents, everything else the role actually demands day to day.
What to Do Now
Before your next hire, write out an honest, realistic week of the actual role, based on your genuine current workload rather than an idealized job description. If that week spans multiple different types of tasks, prioritize adaptability and range in your candidate evaluation over a narrow, impressive specialization that only covers part of what the role will actually require.
