Successor Readiness
You’ve been asking instead of telling. You’ve run the Z. You’ve watched your Just Ask Number climb from 15/85 to something closer to even. By every measure you’ve been tracking, you’re doing the work.
So why can’t you answer the question with confidence: is this person actually ready?
Most leaders can point to effort. Fewer can point to evidence. And the gap between the two is where succession plans quietly fail, not because the leader stopped developing someone, but because no one defined what “ready” would actually look like when it showed up.
This is the part of the discipline nobody talks about. Building the capability is the first half. Recognizing it, without your own bias getting in the way, is the second — and it’s the harder half, because by now you’re emotionally invested in the answer being yes.
Why Leaders Get This Wrong
Two failure modes show up here, and they pull in opposite directions.
The first is impatience. You’ve put in the work, so you start crediting readiness that isn’t there yet. Someone handles one hard conversation well and you decide the job is done.
The second is the opposite: a leader who has spent years being the answer never quite trusts that someone else can be. Every genuine sign of readiness gets explained away.
“They got lucky.”
“They had help.”
“It was a small decision.”
The bar quietly moves every time someone gets close to clearing it.
Both failure modes have the same root cause. You’re using your gut instead of a signal. And your gut, on this particular question, is not a neutral instrument; it’s had years of practice defending your own indispensability.
What you need instead is something observable. Not a feeling. A tell.
The Tells, One Per Mode
Here’s the reframe: the four PEAK modes aren’t just something you do to develop someone. They’re also the four places you should be watching for evidence that the development took.
Professor — the tell is initiation. You’re not looking for whether they can answer a Professor-style question when you ask it. You’re looking for whether they start asking it themselves, unprompted, before a decision gets made. A successor who’s absorbed this mode walks into a problem and maps the terrain on their own — what do we actually know here, what are we assuming — without waiting for you to slow them down first. If you’re still the one supplying the pause, the mode hasn’t transferred yet.
Innovator — the tell is volume before you ask. Anyone can generate one more option when pressed. The tell is whether they arrive with three before you’ve asked for any. A successor who has internalized Innovator mode treats the first idea as a starting point, not a conclusion, without needing you in the room to insist on it. If their first answer is still their only answer, they’re borrowing your Innovator brain, not running their own.
Judge — the tell is a defended trade-off. This is the mode most leaders get wrong when evaluating readiness, because Judge-mode competence looks like confidence, and confidence is easy to fake. The real tell isn’t the decision — it’s whether they can tell you what they gave up to make it. Someone truly operating in Judge mode can say “I picked A over B because of X, and I know that costs us Y.” Someone still performing readiness will defend the decision but go quiet the moment you ask what it cost. Judgment without an owned trade-off is just a guess with good posture.
Director — the tell is action without a check-in. Not asking permission before deciding — that’s Professor still running the show behind the scenes. Not asking permission after deciding, either — that’s the permission tax in reverse, where they’ve made the call but still need you to bless it before it’s real. The tell is a successor who decides, acts, and tells you what happened, past tense. If the last step still routes through you, the seat isn’t actually occupied yet, no matter what the title says.
The False Positive Worth Naming
Here’s the one that catches leaders off guard most often: enthusiasm is not a tell.
A successor who is engaged, asks good questions in the room, and clearly wants the role can still be nowhere close to ready. Wanting it and being able to run it independently are unrelated variables, and conflating them is how leaders end up handing over a seat six months too early — or, just as often, using someone’s visible eagerness as an excuse to hand over nothing at all, since “they’re so hungry, they’ll figure it out.”
Watch for the four tells specifically. Not tone. Not energy. Not how they perform in the meeting where you’re still in the room.
Running the Test Without Announcing It
You don’t need a formal evaluation to check for these signals. You need to stop being in the room.
Give someone a real decision, with real stakes, and go quiet. Not the theatrical quiet of a leader waiting to be asked for permission. Actual absence — a trip, a delegated project, a meeting you skip on purpose. Then watch what comes back.
Did they map the terrain first?
Did they arrive with options?
Can they name the trade-off?
Did they act and report, or wait and ask?
That’s the readiness test. It was never a document. It’s what happens when the six-month bus-test question stops being hypothetical.
Get the Full Framework
The four tells only mean something if you know how to build toward them in the first place. The full PEAK Inquiry Framework breaks down each mode in depth, the Z-pattern sequence that builds readiness on purpose, and the diagnostic tools — including your own Just Ask Number — to track whether the person you’re developing is closer to ready than you think, or further than you’d like to admit.
Download the PEAK Inquiry Framework and find out which mode is still waiting on you.
