Hire Into a Vacuum and the Vacuum Wins.

Written and narrated by Serguei Poppeleer.

I once watched a brilliant senior hire wash out in ninety days. Not because they were wrong for the job. Because there was no system, just a vacuum with a title.

Great CV. Ran bigger programmes than ours. We hired them to bring structure and take things off my plate. Three months in, they were quietly building their own private way of working, nobody else understood it, and I was more involved than before. We had bought chaos at a senior rate.

A strong hire cannot perform inside a system that does not exist. You do not get structure. You get a more expensive version of the gap.

The belief

Get the right person and the system will follow

This is the most expensive belief in a founder-led firm. Smart, senior people do not conjure a system out of a vacuum. They each invent their own, in self-defence, and now you have as many versions of your business as you have senior hires. The right person amplifies whatever they land in. Land them in chaos and they amplify chaos.

People run systems. They do not replace them. Hire into a vacuum and the vacuum wins.

The shift

Systematise first. Then hire into it.

The order is the whole game. The system has to exist on paper before a person can perform inside it. Write the delivery architecture — the 5Cs, one page each — and the next senior hire inherits a structure they can be excellent inside, instead of a blank page they have to privately fill.

Field note

The hires who succeeded for me did not arrive to figure it out. They arrived to a written method, a defined cadence, and decisions that already had owners. Their talent went into the work, not into reinventing how the work runs. Same calibre of person. Opposite result. The only variable was whether the system was there when they walked in.

Systematise, then scale the team. Reverse it and you are paying senior salaries to onboard from the one person who has no time: you.

What to do
1 - Freeze the next senior hire until the system is written

If you cannot hand them a one-page method per C, you are not ready to hire. You are ready to delegate your chaos.

2 - Write the architecture, not the job description

The job description says what they own. The architecture says how it runs. They need the second one more.

3 - Onboard into the cadence, not into your calendar

Day one is the playbook and the control rhythm, not a week of meetings with you.

4 - Measure performance against the system

If they can only succeed by routing through you, the system is not done, and it is not their fault.

But...
But I need the help now.

Then write the one page now. It is a day of work that turns a six-month onboarding into a one-week one.

But great people want freedom, not a manual.

Great people want a clear game to be excellent at. A system is not a cage. It is the field markings. They still play. They just stop guessing where the lines are.

But our best hire built their own system and it worked.

For them. The test is whether the next person can run it. If it left when they left, you did not hire a system. You rented one.

AI Reality Check

AI can compress writing the playbook from weeks to a day, and can onboard a new hire by answering how-do-we-do-X-here from your documented method around the clock. What it cannot do is supply the method if you never wrote one. Feed it a vacuum and it confidently makes things up. Write the system. Then AI can teach it.

Hiring is not how you build a system. It is how you scale one that already exists. Build first. Then hire into it, and watch the same calibre of person finally perform.

Find where delivery still depends on you.

Get your Delivery Score. Fifteen Yes/No questions, about four minutes. It shows which of the five controls is weakest as you scale.