The first senior people hire is a systems decision, not a culture one.
Founders treat it as a vibe match. It's an operating decision — and getting the sequence wrong is expensive twice.
The first senior people hire usually gets made for the wrong reasons. The founder is tired, the team is asking for someone, and a warm, likable candidate appears. Culture fit, everyone nods. Offer goes out.
Six months later the function still isn't shipping, because likability was never the constraint. The constraint was that nobody had defined what the function is supposed to produce — so the new hire inherited the same fog, at a higher salary.
Hire the system first. The person second. A senior leader dropped into an undefined function will spend their first year defining it — on your clock.
Define the mandate before the search
Before you write the job description, you should be able to answer three questions in a sentence each: what does this function ship, what does it own, and what does success look like in 12 months. If you can't, no candidate will be able to either.
Then decide if it's even a full-time role
Sometimes the honest answer is that you need the function rebuilt, not a permanent executive added to payroll. A fixed engagement can stand up the system and tell you exactly what the eventual full-time hire should own — so the search is scoped, not speculative.