The Hire Was Right. There Was Nowhere For Them To Stand
There's a particular assumption that sits underneath most growth plans, rarely stated outright, rarely questioned.
More work is coming in. So more people get hired. The two are treated as if they're the same decision.
I heard a version of the more honest thinking recently, in a conversation between an MD and an Ops Director. The MD put it plainly. We'll need the right people to reach our potential. But it's just as important that we get the right frameworks in place, so new people joining the business don't start cold, and have something to work inside.
That second sentence is doing more work than it first appears to.
Most growing businesses hire well. They interview properly, they check references, they bring in people who are genuinely capable. What they don't always do, at the same pace, is build the thing a capable new person actually needs in order to become useful quickly, a defined way of working they can step into, rather than one they have to invent from scratch.
Without that, starting cold isn't a minor inconvenience that resolves itself in the first few weeks. It's a cost that lands somewhere, and it lands in one of two places.
The first is drag on the people who are already stretched. A new hire without a framework to work inside will lean on whoever's nearby, asking questions that would have been answered by documentation, if documentation existed. That doesn't add capacity to the business. It relocates the existing strain onto someone with even less time to absorb it, usually the same people the new hire was brought in to relieve.
The second is friction at every point the new hire connects with the rest of the business. A capable person without a defined way of working will build their own version of one, because that's what capable people do. Multiply that across several new hires, each solving the same problem slightly differently, and the business accumulates a set of interfaces between people and functions that all work a little differently from one another, none of them wrong exactly, none of them scalable.
Neither outcome shows up immediately, and neither shows up cleanly in conventional performance data. In the short term, the new hire is busy, work is getting done, everyone feels the relief of more hands. The cost is quieter than that, measurable less in output and more in the energy it now takes to do things that used to be ordinary, a question that used to take a minute now taking fifteen, a handover that used to be automatic now needing to be explained from scratch each time.
I think the reason this gets missed so often is that hiring feels like the strategic decision, and building the framework a new hire steps into feels like an operational detail, something that can be sorted out once they've started. But the framework isn't a detail. It's the difference between a new person adding capacity from their first week, and a new person quietly consuming the capacity of everyone around them while they work out, unassisted, how things are actually meant to be done here.
The MD who raised this had understood something that's easy to know in theory and genuinely rare to act on in practice. Hiring the right people was never the whole answer. It was only ever half of it.
Most growing businesses can describe how many people they've hired this year.
Fewer can describe, with the same clarity, what those people actually had to work inside once they arrived.
The question worth asking before the next hire isn't only whether the role is right.
It's whether there's something built for them to step into, or whether they're about to start cold, the same way the last person did.