You have a team of competent people, and yet things move slowly. Deadlines drift. Quality is inconsistent. The instinct is familiar: we need better people, or more of them.
Before you open that hiring req, pause. Most of the time, what looks like a people problem is a process bottleneck wearing a convincing disguise.
Here is how it usually plays out. A founder notices a repeated failure — deployments are late, customer issues linger, a quarterly goal slips. They look at the team responsible and conclude the team is underperforming. The next move is predictable: coach harder, performance-manage someone out, or start recruiting.
But adding a second engine to a car with a clogged fuel line does not make it faster.
The real drag is often structural. An approval that routes through one person who is in meetings six hours a day. A handoff between two teams where neither feels ownership. A weekly report that takes hours to compile and that nobody acts on. These are process chokepoints, and they create the same symptoms as a skill gap: slow output, missed targets, visible frustration.
The difference matters because the fixes are completely different. Hiring around a constraint is expensive and temporary. Removing the constraint is cheap and permanent.
Before blaming the people in the system, inspect the system itself. Three questions will get you most of the way to a diagnosis.
1. Where does work wait?
Pick a task that recently took too long. Walk it backward from completion to initiation. At each step, ask: was time spent doing work, or waiting for something? Approvals, reviews, access requests, information from another team — these are wait states. If more calendar time was spent waiting than working, you have a flow problem, not a capability problem.
2. Who owns the handoff?
Most bottlenecks live at boundaries. Team A finishes their part and tosses it to Team B. Neither team considers the handoff their responsibility. The work sits in a gap between two job descriptions. If you find a recurring handoff with no clear owner, you have found your constraint. The fix is usually naming an owner and giving them authority to pull work through, not adding headcount on either side.
3. Does this artifact change a decision?
Every recurring report, dashboard, or status meeting exists to inform action. Ask the last three consumers of that artifact: what did you do differently because of this? If the answer is nothing, the artifact is waste. It occupies someone's time without producing outcomes. Kill it or radically simplify it. The hours you free up may be the hours your team has been missing.
After running that diagnostic, you will have a short list of constraints. Now ask the question that should precede every headcount request:
If I removed this bottleneck, would the current team hit the target?
If yes — and it is surprisingly often yes — then hiring is the wrong move. You do not need a new person. You need a shorter approval chain, a clearer ownership boundary, or fewer artifacts that serve no purpose.
If genuinely no, then hire. But you will hire with clarity about what the new person actually needs to do, which means a better job description, sharper interviews, and faster onboarding.
Two reasons founders default to the people explanation.
First, people are visible and processes are not. You can see a teammate struggling. You cannot see the invisible queue of work waiting for a signature that takes three days.
Second, hiring feels like action. Opening a req, reviewing resumes, making an offer — it has momentum. Mapping a workflow and questioning whether an approval step should exist is slower, less dramatic work. But it is higher-leverage work.
Process fixes are not free. Removing an approval step means accepting more risk. Killing a report means losing a signal, even if nobody was using it. Reassigning ownership means a difficult conversation with whoever thought they owned it before.
These trade-offs are real, and worth making explicitly rather than avoiding them by throwing headcount at the problem. A team of eight moving without friction will outperform a team of twelve grinding through a broken workflow every time.
Pick the task that most recently frustrated you. Walk it backward. Find where it waited. Ask who owned the handoff. Ask whether the artifacts around it changed any decision. You will find your bottleneck, and it will probably not have a name and a LinkedIn profile.
Fix the constraint before you hire around it. Your team is likely better than your process is letting them prove.
Be the first to comment.
0 comments
Loading comments...