Why Hiring More People Doesn’t Solve a Structural Problem

Home – Blog
Six months ago, you hired someone to take the pressure off. You wrote the job spec, sat through the interviews, made the offer, absorbed the salary. And here you are, working the same hours you were before, only now you are also managing the person you hired to help.

Six months ago, you hired someone to take the pressure off. You wrote the job spec, sat through the interviews, made the offer, absorbed the salary. And here you are, working the same hours you were before, only now you are also managing the person you hired to help.

The instinct that follows is almost always the same: the hire was wrong, or you need another one. Neither is usually true. The reason the pressure never lifted is that hiring adds capacity, and what you had was not a capacity problem. It was a structural one. A structural problem does not care how many people you put against it.

This article draws a distinction most business advice skips straight past: the difference between a business that needs more hands and a business that needs redesigning. Get that distinction wrong and every hire you make from here inherits the same fault, replicates it, and attaches a salary to it. Get it right and you will know, before you write the next job spec, whether headcount is the answer or the most expensive way to avoid the real one.

Why doesn’t hiring more people fix the problem?

Hiring adds capacity to a business without changing its design. When the constraint is structural — the model, the offer, the way work is defined — a new person inherits that structure rather than repairing it, so the pressure moves instead of lifting.

Capacity and structure are easily confused when you are stretched, but they are not the same thing. Capacity is how much work the business can carry. Structure is how the business is put together underneath the work: what it sells, to whom, at what margin, and through what model the value actually moves.

A new hire changes the first and leaves the second exactly as it was. If the design is sound and you are simply out of hands, hiring works, and it works cleanly. If the design is faulty, the new person does not repair it. They join it. They learn the workarounds everyone else learned, absorb the ambiguity that was already there, and become one more place the strain can show.

Is it a capacity problem or a structure problem?

A capacity problem is when well-designed work simply exceeds the hands available. A structure problem is when the work itself is poorly defined, wrongly routed, or priced below its cost. No volume of hands resolves the second.

This is where most advice on the subject stops short. The common counsel is sensible as far as it goes: do not hire into chaos, fix your processes first, get your operations clear before you add people. It is right that hiring will not fix a mess. But it misdiagnoses the mess.

Processes and systems are the operational layer — how work flows once the business has decided what work it does. Structure sits beneath that. It is the design decision the process is expressing. You can document a workflow to perfection and still be documenting the wrong thing perfectly. Tidy the process around a broken model and you have built a cleaner version of the wrong business, then staffed it.

A system problem is “we do the right work, badly organised.” A structure problem is “we have organised ourselves efficiently around work that should not exist.”

Rob Spedding

That is the flaw in “fix your systems first.” It treats structure and systems as the same job. They are not. The first is resolved with clarity and documentation. The second is resolved only by changing the design — a client who should never have been yours, a price that never covered its cost, a service you kept because it was there rather than because it worked. No amount of process discipline substitutes for that decision.

What happens when you hire into a structural fault?

The fault does not disappear. It scales. Coordination cost rises, the founder becomes the integration layer holding the pieces together, and the same structural weakness now runs at higher headcount and higher payroll.

When you add a person to a well-designed business, they slot in. The design tells them what their work is, where it begins and ends, and how it connects to everyone else’s. When you add a person to a faulty one, none of that is waiting for them, so three things happen in sequence.

First, coordination cost rises faster than output. Every new person adds communication paths, handoffs, and places for the undefined to become the misunderstood. In a sound structure that cost is worth paying. In a faulty one you are paying it for confusion.

Second, you become the integration layer. Because the design does not hold the pieces together, you do — in your head, in your inbox, in the constant low-level translation between people who each hold a fragment of how things work. The hire was meant to reduce that load. Instead it added a fragment to reconcile.

Third, the fault compounds. Whatever was wrong at three people is now wrong at five, running through more salaries and more dependencies, and harder to change because more of the business is now built on top of it. The problem did not get solved. It got more expensive to solve.

Where do structural faults actually hide?

Structural faults tend to sit in one of five places: the clarity of the vision, the strategy, the way the business is structured, how it executes, or how it is optimised. A new hire lands on top of all five and changes none of them.

If the problem is not headcount, it helps to know where it actually lives. In practice, structural faults cluster in five areas — the same five the Architecture Gap examines:

  • Vision. The business has grown past the clarity it was founded on, and no one, including you, can say precisely what it is now for.
  • Strategy. You are competing on terms that no longer fit the business you have become, so effort scatters across too many fronts.
  • Structure. Roles, ownership and decision rights were never designed. They accumulated. Accountability is ambient rather than assigned.
  • Execution. The work gets done through memory and effort rather than design, which is exactly why a new person cannot simply pick it up.
  • Optimisation. The model runs, but at a margin or a pace that quietly taxes everything, and more people make the tax bigger, not smaller.

You cannot recruit your way out of a vision that has gone vague or a margin that never worked. That is the whole point of the distinction. The hire is real, capable, and willing. The fault is simply somewhere the hire cannot reach.

How can you tell the difference before you hire?

Ask what the new person would inherit. If they would step into clearly defined, well-priced, correctly routed work, it is capacity. If they would inherit ambiguity, workarounds and undefined ownership, it is structure — and the hire inherits the fault with it.

Before you write the next job spec, three questions separate the two cases.

  1. If this role were filled tomorrow by a capable stranger, could they tell what their work is without you explaining it? If the answer depends on you being available to translate, the work is not defined. That is structure, not capacity.
  2. Is the work you would hand over actually profitable, or does it only feel urgent? Volume of unprofitable work is not a hiring signal. It is a pricing or model signal wearing a hiring costume.
  3. Are you hiring to do more of something that works, or to relieve a pressure you cannot quite name? The first is capacity. The second is almost always structure asking to be diagnosed rather than staffed.

If those questions point to structure, the honest next step is not a recruiter. It is a diagnosis — finding which of the five dimensions is actually the constraint, so you fix the design before you build more of the business on top of it.

When is hiring actually the right move?

Hiring is right when the design is sound and demand genuinely exceeds capacity: the work is clear, well-priced and correctly routed, and you simply need more hands to do more of what already works.

None of this is an argument against hiring. Businesses grow by adding people, and adding them at the right moment is one of the most productive decisions a founder makes. The point is sequence, not prohibition.

Hire when the work is defined well enough that a capable person can own it without you narrating it. Hire when the thing you are scaling is profitable, so more of it makes the business stronger rather than merely busier. Hire when the constraint is genuinely a shortage of hands against sound work, not a fault the hands would be asked to absorb.

Get the design right first, and the same hire that would have inherited chaos instead inherits a clear seat in a business that works. The person does not change. What they walk into does.

The question underneath the question

The instinct to hire when you are under pressure is a good instinct pointed at the wrong target. It reads the symptom — too much to do — and prescribes the obvious cure — more people to do it. But if the pressure is coming from the design rather than the volume, more people is the most expensive way to leave the real problem in place.

The question was never how many people you need. It is what you would be asking those people to compensate for.

BEFORE YOU WRITE THE JOB SPEC

The Architecture Gap Scorecard assesses all five dimensions and returns the one that matters: your primary lever — the place your design gave out. Find out whether your next move is a hire or a redesign, before you commit a salary to the wrong one.

Picture of Rob Spedding

Rob Spedding

Rob is passionate about guiding individuals and businesses to reach their highest potential through high-performance coaching and innovative digital solutions. Rob is a driven entrepreneur committed to nurturing excellence, embedded within a foundation of honesty, integrity, loyalty and trust.

About Rob

Rob is passionate about guiding individuals and businesses to reach their highest potential through high-performance coaching and innovative digital solutions. Rob is a driven entrepreneur committed to nurturing excellence, embedded within a foundation of honesty, integrity, loyalty and trust.

Recent Posts

Follow Me