Hiring will not fix a structure problem
More hands does not automatically mean fewer questions land on your desk. Sometimes it means more.
The busier the wedding season got, the more freelance hands I brought in. Logically, more people should have meant less landing on me. In practice, every extra person I brought in arrived with more questions, not fewer, because I had never actually decided, on paper, who was allowed to make which call without checking with me first.
This is not a headcount problem. It is a structure problem.
And structure does not arrive on its own just because the team gets bigger. Somebody has to design it, and hiring is not the same activity as designing it.
Where it actually starts
In a very small team, everyone naturally knows what everyone else does. Structure is implicit, and it works, right up until the team grows past a handful of people. Nobody notices the moment it stops working, because hiring feels like the fix for a growing business – we just need more capacity. But, the actual problem, that nobody owns which decisions, never gets named. It just gets bigger, one hire at a time.
Why founders avoid designing it
- Hiring feels like progress. Structure feels like admin. A new hire is exciting. A decision-rights chart is not. Founders default to whichever one feels like momentum.
- It feels presumptuous to formalise something so early. As if you are playing at being a proper big company before you feel like one. So structure gets pushed off until the business is big enough to deserve it, which is backwards – the pain arrives well before that point.
- The founder is often the only person who can see the whole picture, which means nobody else is positioned to design the structure, and the founder is usually too busy inside the business to step back and do it.
What it is quietly costing you
- Every new hire adds to the founder’s load rather than reducing it, because more people means more requests for a decision only the founder feels able to make.
- Good people leave, quietly frustrated, because they were never told clearly what they were actually responsible for owning.
- Growth plateaus at exactly the headcount the founder can personally still oversee, a ceiling nobody chose on purpose.
What your thinking style has to do with it
- Driver: hires fast to solve a capacity problem, and only notices the structure problem once three new people are all asking the same unanswered question.
- Navigator: has the org chart clear in their own head, and assumes it is equally clear to everyone else, because they have never had to say it out loud.
- Connector: avoids formal role definition because it can feel bureaucratic, preferring people to figure it out together which works, until it doesn’t.
- Analyst: over-engineers the structure on paper before a single person is hired into it, and the plan is out of date by the time real people with real quirks fill the boxes.
If every new hire adds to your workload instead of taking from it, the problem was never the team. It was the shape around them.
What actually changes it
The coaching side surfaces why structure keeps getting deprioritised, and which pattern is yours. The operational side, alongside or before the next hire rather than after it, is actually mapping who owns what.
- A simple map of the five or six decisions that currently only get made by you.
- A named owner for each of those, even if that owner is you, for now, on purpose rather than by default.
- A short brief for the next hire that says what they own, not just what they do.
This is the sibling problem to the founder bottleneck. Where that piece is about trust and briefing, this one is about the shape the team is hired into. For agencies working through a real restructure, this is usually the kind of thing that needs sitting alongside someone for a while rather than fixing in half a day, which is where the Embedded Partnership tends to come in.
I hired good people. I just never gave them a shape to sit inside. That is not their failure to fix. It was always mine.
Further reading
Gino Wickman’s Traction sets out a simple, practical model for building the accountability structure underneath a growing team, well before it becomes urgent.
- Ready to charge what your work is actually worth?