Confront, decode, or quietly start interviewing? What three executive coaches would do with that sentence

The conference room door never fully clicked shut. Your boss is on the phone with his own boss, and the fragment that reaches you is about your readiness: "She's not quite ready." You don't catch the question that prompted it, or anything that followed, because you step away, as any level-headed professional would. Back at your desk, you've run the words through your head a dozen times already.

At 46 and working as a senior director, you have spent the past seven months shouldering VP-caliber responsibilities in Nashville while your title stayed where it was. Two weeks ago that VP role went up on the internal board. Someone has concluded you aren't prepared for it, and no one has explained what prepared actually means.

Option A: Take It Straight On

Back in his office, you take a seat again. "I caught part of your call. I'd prefer to hear the rest from you." The drawback is that you've owned up to lingering outside a door, and he may get defensive. Certain leaders respect the directness. Others quietly file you as both a concern and not yet ready. The advantage is speed. By Friday you'll know whether "not quite ready" rests on an actual definition or is simply a habit of speech dressed up with a title.

Option B: Analyze

You drop the phone call from the picture entirely. Instead you ask the question you should have raised seven months ago: "What would I need to demonstrate for you to see me as the clear choice for the VP role?" Write his answer down, send it back to him in an email, and work through the list. What you give up is time, and you also run the danger that the target keeps shifting under you. The payoff is a paper trail. If the list keeps expanding each time you check something off, you'll have it documented, and that record is worth more than anything you overheard.

Option C: Quietly Start Looking Around

You take a couple of calls. The downside is the energy you're already short on, plus a decision that may arrive sooner than you'd like. The upside is leverage you can't build any other way. Nothing clears up "not quite ready" faster than a competitor who believes you're ready.

Guidance from experienced executives

Leaders who have sat on both sides of conversations like this say "not quite ready" rarely describes a skill gap. Most of the time it reflects how at ease the speaker feels, far more than any objective standard. A 2025 McKinsey and LeanIn report found that for every 100 men promoted to manager, 93 women were, and that 80 percent of women want a promotion compared with 86 percent of men, a gap that closes when support is equal. Tara Mohr's HBR survey found that women tend to skip roles mainly because they treat posted requirements as hard rules rather than because of any lack of confidence. Saying "ready" walks you into the very same pitfall, just phrased another way. You're hearing a rule. He might have been talking about how he felt at the time.

They also warn that Option B is toothless without a deadline, and Option A is hollow without a specific question. Those who secured the role managed three things: they requested the definition in writing, pinned it to a specific date, and made one outside contact that same week so the deadline had genuine force behind it.

Verdict reached

Whether it works out hinges on if he is able to spell it out. This week, press him for the definition, which is the path labeled Option B. Should his reply arrive specific and tied to a date, begin moving toward that goal. If it stays vague, or a fresh requirement appears every month, Option C is already your answer, and the email you saved will back you up.

Your choice

Given the choice, would you confront, decipher, or discreetly interview? Cast your vote below. We'll publish the results next week, along with the question most of you say you'd ask.