Sometimes the problem is not headcount.
Kristina Golovko
MindDesign
The decision matrix
Hire
Persistent, internal, strategic
System
Repeatable, automatable, scalable
Outsource
Time-bound, specialised, external
Wait
Premature, unclear, not yet real
Every business problem sits in one of these quadrants. Only one of them requires a hire.
Why this matters
Founders default to hiring because it feels like action. A problem exists, a person is hired to solve it. The logic is intuitive — and often wrong.
Most operational problems that get solved by hiring could have been solved by a better process, a clearer system, or a more honest conversation about ownership. The hire adds cost and complexity to a problem that didn't require either.
The discipline isn't about avoiding hiring. It's about understanding what kind of problem you actually have before deciding how to solve it.
Founder reality
Before opening the role, test the problem against these questions:
Could a clear process replace the need for this person?
Is this problem persistent, or does it spike and fade?
Does the solution require internal ownership — or just external expertise for a defined period?
Could automation handle 60–80% of the underlying task?
Is this problem real today, or are we anticipating a problem that hasn't arrived?
If more than two answers point away from hiring, explore the alternative first.
The framework
Four paths, each with different conditions. Choose the path that fits the problem — not the one that feels most like progress.
Hire — when the problem is persistent, strategic, and requires internal ownership
Hiring is right when the work is core to the business, requires judgment developed over time, and will only grow in importance. If the problem will still exist in two years and requires internal accountability — hire.
Build a system — when the problem is repeatable and structural
If the same problem recurs because there's no process, playbook, or tooling to handle it — the solution is a system, not a person. Systems scale. People don't replicate.
Outsource — when the problem is real but time-bound or highly specialised
Specialist work with a clear deliverable, a defined timeline, or a peak demand pattern is often better handled externally. Outsourcing keeps you lean and focused. The cost of a bad hire far exceeds the cost of a good contractor.
Wait — when the problem isn't yet proven to be structural
Some problems feel urgent but haven't yet demonstrated persistence. A new product launch creates temporary demand spikes. A growth phase creates short-term operational pressure. Hire too early and you're managing overhead before you have the revenue to support it.
Common mistakes
01
Hiring to relieve founder anxiety
Hiring doesn't resolve strategic uncertainty. It adds payroll to it. Make the business decision first.
02
Treating outsourcing as a permanent solution
Outsourcing works for defined scope. When the work is open-ended and strategic, external ownership creates misalignment.
03
Building systems too late
Waiting until the team is overwhelmed to build process means you're now managing chaos and a hiring process simultaneously.
04
Confusing headcount with capability
Adding people doesn't add capability if the new people inherit broken processes. Fix the system first.
Example scenario
A deep-tech startup, 12 people, pre-Series A. The founder wants to hire an operations manager because 'things are slipping through the cracks.'
The surface problem
Tasks are being forgotten. Deadlines missed. The founder is fielding too many operational questions.
What investigation revealed
There was no shared task system — decisions lived in Slack threads and memory.
The founder had not delegated any documented process — every decision came back to them by default.
Three recurring admin tasks were consuming 6+ hours per week and were fully automatable.
The actual bottleneck was a missing coordination layer, not a missing person.
The decision
A project management system was implemented. Automations were built for recurring admin. Three clear process owners were named. The operations manager role was deferred by six months — by which point the actual need had become clear and scoped.
The question isn't whether to hire.
It's whether the problem in front of you is actually a hiring problem. Often it isn't. And the cost of hiring into the wrong diagnosis is far higher than the cost of thinking it through.
Continue reading
Hiring Too Early Costs More →