06 Scaling Operations
The Startup
Generalist Trap
What works early often breaks later.
The generalist evolution
Speed
Generalists move fast with low overhead
Flexibility
Everyone covers everything
Overload
Ownership becomes unclear under growth
Role clarity
Defined ownership restores execution speed
Generalist structures are optimised for survival. Role clarity is optimised for scale. The transition between them is the trap.
Why this matters
Generalism is the right answer — until it isn't.
Early-stage startups survive because of generalists: people who move fast, cover gaps, take ownership of whatever needs doing, and don't stop at the edge of their job description. This is exactly what the company needs when it has limited resources, undefined processes, and a product that isn't working yet.
The trap is that the same structure that creates early speed creates later friction. As the company grows, undefined ownership becomes a bottleneck. Generalists who were heroes at 15 people become overwhelmed at 50. The informal coordination that worked when everyone sat in one room fails when the team spans three time zones.
The generalist trap is not a people failure — it's a structural one. The people didn't change. The organisation grew past the structure that was designed for a different stage.
Founder reality
Diagnose whether the generalist structure has become a constraint:
Are there team members who are responsible for too many different things to be excellent at any of them?
When something goes wrong, is it ever unclear who owned that area?
Are decisions slowing down because the people who need to make them are overloaded with other responsibilities?
Have we promoted generalists into specialist roles they're not suited for — because they were available and trusted?
Is there work that nobody owns — not because it's unimportant, but because everyone assumed someone else was handling it?
The generalist trap often becomes visible through a pattern of small execution failures — not one large one.
The framework
Four stages of the generalist lifecycle
Recognise the stage. Design the transition before it becomes a crisis.
01
Speed — generalism creates competitive advantage in early stages
At sub-20 people, generalist structures are optimal. Low coordination overhead, fast decisions, high ownership density, and adaptive coverage of emerging needs. The structure matches the stage. Don't redesign it prematurely.
02
Flexibility — generalism stretches as the team grows
As the team approaches 30–50 people, generalism starts straining. Key generalists are responsible for too many domains. Informal coordination becomes insufficient. The structure is still working — but the cracks are visible. This is the early warning stage.
03
Overload — generalism creates the problems it used to solve
Past 50 people, unresolved generalism produces execution drag: decisions delayed because the right person is stretched, accountability gaps because nobody clearly owns an area, and key-person dependencies that create organisational fragility. The structure is now working against the company.
04
Role clarity — defined ownership restores execution speed
The solution is not to hire more people into the same structure. It's to redesign the structure: clearer ownership, defined domains, explicit handoffs, and the willingness to have honest conversations with generalists about evolving their roles — or their exits.
Common mistakes
01
Waiting for a crisis to redesign roles
Role redesign under pressure produces rushed, political decisions. The best time to address the generalist trap is 3–6 months before it becomes a crisis — when there's still space to think carefully.
02
Assuming your best generalists will become your best specialists
Some generalists thrive in specialist roles. Many don't — the skills that made them excellent generalists (breadth, adaptability, coverage) are not the same skills that make excellent specialists (depth, focus, mastery). Assess honestly.
03
Adding headcount without changing the structure
Hiring more people into a structurally unclear organisation adds complexity without adding clarity. New hires inherit the ambiguity and amplify it.
04
Redesigning roles without involving the people in them
Role redesign that happens to people rather than with them produces resentment, disengagement, and attrition. The best role redesign processes are collaborative — even when the outcome is difficult.
Example scenario
A Series A AI company, 45 people, growing from 20 in 18 months. Engineering lead had been the de facto head of product, infrastructure, and team management simultaneously. Execution was slowing. The lead was burning out.
The diagnosis
Role audit conducted: engineering lead responsible for technical architecture, product prioritisation, engineering hiring, team 1:1s, and board reporting on engineering progress. Any one of these would be a full-time role at a larger company. All were being done simultaneously.
The redesign
Product prioritisation transitioned to a newly hired product manager over 6 weeks.
Engineering hiring process redesigned with a structured system that reduced the lead's involvement from 80% to 30%.
Team management split: two senior engineers given team lead responsibilities for sub-teams.
Engineering lead retained: technical architecture, strategic technical decisions, and board reporting.
The outcome
Engineering lead's output on technical architecture improved immediately — not because they worked more, but because they worked on fewer things. Team velocity increased measurably within 6 weeks. The lead remained at the company; a departure had been likely without the redesign.
Takeaway
Generalism is a feature at one stage and a bug at another.
The transition is not about replacing generalists — it's about evolving the structure around them. Done well, it preserves the best of what made them effective while removing the structural weight that was slowing everyone down.
Continue reading
Why Teams Suddenly Feel Heavy