Hiring Before You’re Ready vs. Hiring Before You’ve Shifted: What Nobody Tells You
“Hire before you’re ready” is one of the most common pieces of business advice for growing founders. The idea is that waiting for the perfect moment means waiting forever, that the discomfort of bringing someone on before everything is in place is exactly the point, that a little bit of chaos is the cost of momentum.
There is truth in that. Founders who wait for perfect conditions before hiring often wait too long.
But there is a different kind of readiness that the “hire before you’re ready” advice completely misses. And not being ready in this second sense is the reason hires fall apart, the reason the support does not stick, the reason founders find themselves back where they started six months after bringing someone on.
The two kinds of readiness are not the same. Conflating them is one of the most expensive mistakes a founder can make.
Operational Readiness: What Most Advice Addresses
When most people talk about being ready to hire, they are talking about operational readiness.
Operational readiness means you have enough revenue to support the hire. You have a clear enough scope for the role that you can describe what the person will do. You have at least the beginning of a system for onboarding them. The basics of the business are stable enough that a new person has something to plug into.
These things matter. A hire made before any of these basics are in place is a recipe for a chaotic onboarding and a short tenure.
But operational readiness is not what determines whether a hire sticks. You can have all of it — the revenue, the scope, the systems — and still watch a hire unravel over three to six months. The reason is that operational readiness addresses the business’s capacity to bring someone on. It does not address the founder’s capacity to actually use the help.
Leadership Readiness: What Nobody Talks About
Leadership readiness is the less-discussed dimension. It is the founder’s internal readiness to operate as the kind of leader the hire requires her to be.
A hire requires something specific from the founder: the ability to give real authority, to evaluate outputs against an externalized standard rather than against her own internal execution, and to stay out of the lane she assigned. These sound straightforward. For most founders who have built something from scratch, they are genuinely difficult.
Because the founder who built the business built it by being in every detail. Her judgment, her standards, her presence in the work — these were the quality control system. The business worked because she worked. And that pattern does not automatically update just because the business has grown and a new person has joined.
Leadership readiness means having made enough of the internal shift — from being the person who does the work to being the person who leads the work — that the hire has space to actually do their job. Without it, the hire will find themselves in a position where the formal authority of their role is constantly being overridden by the informal authority of the founder’s presence.
What It Looks Like to Hire Before You’ve Shifted
Here is the pattern that plays out when a founder hires before the internal shift:
The first weeks feel promising. The load is lighter. Someone is handling things. The founder feels relief.
Then the friction starts. The founder notices things that are not quite right. Not wrong, exactly, but different. She adds a review step. She sends a few corrections. She loops herself back in on something she technically handed off because it is faster and cleaner to just handle it.
The hire starts to navigate the founder’s moods and preferences rather than executing against a clear standard. They learn to check in before acting, to wait for approval before moving, to route everything up rather than owning decisions. Because owning decisions and then having them overridden is demoralizing. It is safer to not own.
Six months in, the founder looks at the hire and sees someone who is not performing to the level she expected. The hire looks at the situation and sees a role that was described one way and actually works another. Neither party is wrong about what they are experiencing. But the root cause is not the hire.
It is the gap between the role as described and the role as actually granted by a founder who has not yet made the internal shift.
The Shift That Comes First
The shift is not a certification. There is no moment when the founder is officially ready to lead differently. It is a practice that starts before the hire and continues through and after it.
What does the shift involve, practically?
Getting the standard out of your head. Before anyone is hired, the quality standard needs to exist somewhere other than the founder’s intuition. Not as a process document — as an outcomes document. What does a piece of work need to accomplish to be good enough to leave this business? What are the two or three things that are always true of work done right? Write those down. That is the beginning of a standard that can be held by someone other than you.
Defining what you are handing off in terms of ownership, not tasks. A hire who owns a function has accountability for outcomes. A hire who does a list of tasks has accountability for execution. Founders who have not shifted tend to hire for the second and describe it as the first. Getting clear on the ownership level before writing the job description changes the kind of person you look for and the kind of onboarding you build.
Accepting that different can be right. The hire will approach things differently than you do. Some of those differences will be innovations. Some will be learning curves. Very few will be actual quality failures. Building the muscle to distinguish between “different from what I would have done” and “wrong” before the hire starts means the hire has a chance of actually growing into their role rather than being quietly reclaimed.
The Sequence That Works
Hire before you’re operationally ready — that part of the advice is sound. Revenue readiness, role clarity, onboarding infrastructure: do not wait for perfect. Get close enough and go.
But do not hire before you’ve started the internal shift. The shift does not need to be complete. It needs to have started. You need to be able to answer: what does this person own? What does success look like for them that does not require me to evaluate every output? And what do I do with my time when this function is running without me?
If you can answer those questions with specificity, you are ready. If you cannot, spend the time before the hire working on those answers. They are the foundation the hire lands on.
The “hire before you’re ready” advice is right about the operational layer. It is silent about the layer that matters more. Now you know the difference.
Enjoyed this article? Follow Nata on Instagram for more practical insights, behind-the-scenes lessons, and tools to help you lead your business with more clarity and less overwhelm.
→ Instagram: @accidentalceo.co
→ Website: AccidentalCEO
