Hire Now or Resequence the Work: How to Tell the Difference

The backlog is growing, everyone is busy, and someone says the obvious thing: we need another person. Before you agree, work out whether you have a staffing problem or an ordering problem. Deciding to hire now or resequence the work is the difference between a permanent cost and a temporary rearrangement, and most teams get it wrong in the same direction. They hire against a peak that lasts a quarter and then carry the salary for years.

Here is how to tell the two apart.

Test one: does the queue shrink if you stop starting things?

Pick the next two weeks and start nothing new. If the backlog drains steadily, you have an ordering problem. Too much work is in flight at once, everything is half done, and finishing rate looks low because nothing crosses the line.

If the queue keeps growing even with nothing new started, that is genuine demand outrunning supply. That is a staffing signal.

Test two: where does work wait?

Track a handful of items and note where they sit still. Waiting for review. Waiting for a decision. Waiting for a client answer. Waiting for one specialist.

If most of the waiting is at handoffs and approvals, hiring will not help much. A new person adds throughput at the doing stage and nothing at the waiting stage. You will have more work sitting in the same queue.

If the waiting is genuinely at the doing stage, with people working steadily and the queue still building, that points to headcount.

Test three: is the peak seasonal?

Look at the same period last year and the year before. If the pressure arrives at a predictable time and then eases, you are looking at a peak rather than a trend. Hiring for a peak means paying for it during the trough as well.

The alternatives to a permanent hire for a genuine peak are the boring ones: contract help, moving lower priority work out of the busy window, and telling clients the truth about dates. None of them are exciting. All of them are reversible.

Test four: is it one person or the whole team?

If the constraint sits on one role, adding a general hire does nothing. A team where everything routes through one reviewer, one designer or one person who knows the old system has a bottleneck, not a shortage.

The fix for a bottleneck is usually to spread the knowledge rather than to add another body somewhere else. Ask what would have to be written down or taught for two more people to do that work. That is often a few weeks of effort against years of salary.

Test five: what happens if you cut the list in half?

Take the backlog and mark the items that would genuinely cost you something if they never happened. Be strict. Many backlogs are a graveyard of ideas nobody has the heart to close.

If half the list can go and the remaining half fits the team, you had a prioritisation problem wearing a staffing costume.

When hiring is the right answer

Hire when the demand is steady rather than spiky, when the waiting is at the doing stage, when the load is spread across the team rather than stuck on one person, and when the backlog survives an honest cull. Those four together are a real signal, and delaying a hire in that situation just burns out the people you have. It also has a price you can measure, because a vacant role costs a countable number of delivery days.

Hire also when you are carrying a single point of failure and the only way to remove it is a second person in that role. That is a risk decision rather than a capacity one, and it is worth making explicitly. If the candidate is moving country for it, budget for the first month questions a relocation brings too.

Why this is hard to see clearly

The information needed for these tests usually sits in three places. Delivery history is in a project tool, absence and role data is in an HR system, and the real story of who is overloaded is in someone's head. Nobody can see capacity and commitments on one screen, so the argument gets settled by whoever sounds most stretched.

SicherOne puts project management and HR on one set of records for exactly this reason: the plan and the people are the same data, so a manager can see who is actually available before deciding that the answer is another seat.

Whatever you use, run the five tests before you write the job description, and remember the clock: notice period maths means a hire agreed today often lands a quarter from now. A resequencing decision can be undone next month. A hire cannot.