If the work outgrows the hours, hire. If the hours are spent badly, a hire joins the same mess. The test: can you say exactly what the new person does all day before the job post goes out?
What you get
The posting test
Write what the new person does on an ordinary Tuesday, hour by hour, with real named work. If the day will not fill, you are hiring to make a feeling go away.
Volume or friction
Volume is more work than there are hours. Friction is the same work taking longer than it should. Another person solves the first and multiplies the second.
What a hire makes permanent
A tool can be cancelled and a sequence can be rewritten. A role gets an owner, a defender and a reason to keep the work exactly as it is.
When hiring is clearly right
When the work needs judgment, a relationship, or somebody accountable in the room. No system does those and no automation should pretend to.
The half answer
Fix the worst two hours of the week first, then hire against what is left. The role comes out smaller, clearer and much easier to fill.
What nobody counts
The months to post, choose, onboard and reach useful. That sits beside the weeks a fix would take, and it usually decides the order.
How to decide, in order
The request is almost always the same. We need another person. It gets made when something is late, usually by whoever is closest to the lateness, which makes it sincere and makes it unreliable as a diagnosis.
Start with the posting test. Write what the person does on an ordinary Tuesday, hour by hour, with real named work rather than areas of responsibility. If the day fills easily the work is there. If it will not fill, the hire is answering a feeling and the feeling comes back.
Then separate volume from friction. Volume is more work than there are hours to do it in. Friction is the same work taking longer than it should, because it waits on somebody, gets carried between places, or gets typed twice. One of those is solved by a person.
A hire is a standing decision. That is not a criticism of anybody, it is what roles do: the work gets an owner who is measured on it, and the shape of the work stops being an open question.
Where it is friction, fix the worst two hours of the week and look again. The role that is left is smaller and clearer, it is easier to hire for, and the person who takes it starts on work worth their time instead of inheriting the mess.
And where the work needs judgment, a relationship or somebody accountable, hire, and stop looking for a system. Those are the parts no process removes, and trying to remove them is how a company ends up with a system nobody trusts.
When a person is the answer, a dedicated team supplies one this month. The delegation split shows how many hours a new person would actually take.
Questions we get
What if we are behind right now?
Behind is a backlog, and a backlog is cleared rather than staffed. A temporary spike answered with a permanent role is how a team ends up overstaffed at the next quiet quarter.
Clear it first, then measure the steady state.
Is a contractor a middle option?
A good one, because it ends. A contractor absorbs the volume while you find out whether it was really volume.
Agree the end date in advance, or it becomes a role by default.
What if the overloaded person is me?
Same test, and it is harder to be honest about. Write the Tuesday.
Most founder overload turns out to be a small number of tasks repeating rather than a full role waiting to be filled.
Could automation replace the hire entirely?
Sometimes, and it is a narrow sometimes. The work has to be the same every time, arrive on its own, and be checkable afterwards.
Where it is not, you are buying something somebody has to supervise, which is a hire with extra steps.
What do we tell the team meanwhile?
Which of the two you are doing and by when. Most of the frustration in an overloaded team is not the hours, it is not knowing whether anybody is going to act.
How fast can a fix land?
One sequence is days rather than quarters. A hire is months to post, choose, onboard and reach useful.
That gap is the strongest argument for looking at the system first, whatever you decide in the end.
More in the guides and every answer in one place.
Shaheer leads the work, with engineers, writers, filers and analysts behind him. C-suite operations for a San Francisco AI company, Six Sigma on the process side, Anthropic certified on the Model Context Protocol, ten years across eight industries. See what we have built