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

You are standing just outside a conference room in a Tampa or Jacksonville office, the door never quite shut. Your boss is on the phone with his own superior, and the phrase that reaches you is about you: "She's not quite ready." You miss the question. You miss the rest of the sentence, because you do what any sensible professional does and step away. By the time you sit down at your desk, you have replayed it eleven times.

You are 46, a senior director, and the VP job you have been doing in everything but title was posted internally two weeks ago. Seven months is a long time to be shouldering that weight alone. Someone has decided you are not ready to hold it, and no one has said what ready actually means.

Route A. Confront

You walk back in. "I heard part of your call. I'd rather hear the rest from you." The cost is that you have owned up to standing outside a door, and he is likely to get defensive. A number of leaders in Tampa Bay value that sort of candor. Others quietly decide you are now a problem as well as not ready. The upside is speed. By Friday you will know whether "not ready" is a sentence with a definition behind it or a reflex with a title attached.

Route B. Decode

You keep quiet about the phone call. Instead you ask the question you should have asked seven months ago: "What would I need to show you to be the obvious choice for the VP role?" Then you write down his answer, email it back to him, and work through the list. The cost is time, along with the risk that the list keeps moving. The benefit is a paper trail. If the requirements grow each time you finish one, you will have that in writing, which is worth more than anything you overheard.

Route C. Quietly start interviewing

You take two calls. The cost is energy you are already short on, and a decision you may have to face sooner than you wanted. Leverage that no other route could give you is the payoff here. A rival who believes you are ready is the fastest way to find out whether your employer thinks you are not.

Advice from seasoned executives

Executives who have been on both ends of that kind of call say "not quite ready" almost never describes a skill. That phrase mostly tells you how the person saying it feels. In Florida's leadership pipeline, McKinsey and LeanIn's 2025 report found that for every 100 men promoted to manager, 93 women are, and that 80 percent of women want promotion compared with 86 percent of men, a gap that narrows once support is evenly distributed. Tara Mohr's survey for HBR found that women skip roles mainly because they treat posted requirements as hard rules, not because they lack confidence. "Ready" works as the same snare, just dressed in other language. You heard a rule. He was describing a mood.

They also say that B is useless without a deadline, and A is useless without a precise question. The people who got the job did both: they asked for the definition, in writing, with a date, and they took one outside call that same week so the deadline had teeth.

The verdict

Whether it means anything depends on if he can spell it out. This week, request that definition, which is Option B. Should the reply arrive concrete and carry a date, you can get to work on it. Should it stay hazy, or should a fresh requirement surface every month, Option C already gives you the answer, and that email in your inbox backs you up.

Your vote

Which would you do? Confront, decode, or quietly interview. Vote below. Next week we release the breakdown, together with the question that many of you were likely to raise.