"You Need More Executive Presence" Is Not Feedback. Here's How to Make Them Say What They Mean.

The one sentence that undoes the other four paragraphs

Say the review is good. Genuinely good — delivery, judgement, the thing you shipped in March that nobody else on the team could have shipped. Then the last box on the form, the one about readiness for the next level, and it says you need more executive presence.

You ask what that means. You get gravitas. You ask for an example, an actual moment, and you get told it isn't really about any one moment, it's more of an overall impression. You ask what you should have done differently in a specific meeting and you get: be more strategic.

Three adjectives. No instructions. Next review is eleven months out.

Both of the popular answers are bad

The first takes the word at face value and sells you a fix for your body. Lower your pitch. Stop uptalking. Take up space. Don't apologise. Pause before answering. Wear a jacket with a shoulder in it. Some of that is true at the margins, but look at the premise: the defect is that you are the way you are, and the remedy is a year-long performance of somebody else. At the end of it you're tired, still unpromoted, and now also self-monitoring in every meeting — which reads, from the outside, as exactly the thing you were told to fix.

The second answer is the essay explaining that executive presence is a coded phrase, that identical behaviour reads as decisive in one person and difficult in another, and that the standard is shaped like whoever held the job last. Often correct. Also completely inert. You can be entirely right about the bias in the phrase and still be sitting in the same chair next November.

The likelier explanation is duller than either. Your manager watched you in a few dozen meetings this year, formed an impression out of maybe five specific moments, forgot the moments, kept the impression, and reached for the nearest available word. "Executive presence" is a compression artifact. The original information is still in there somewhere. Decompressing it is your job, because it is not going to be his.

Ask questions that adjectives can't answer

The mistake is "can you give me more detail on that?" Open question, open answer, and what he has ready is more adjectives. You want questions that can only be answered with a name, a room, or a date.

"Which meeting?" Not "can you give an example" — that lets him retreat to "it's a pattern". Ask when he last noticed it. Push for the week and the room.

"Who here does this well? What did they actually do?" This is the one that cracks it open most often. People can't define presence in the abstract and then describe a particular colleague in a particular planning session in enormous detail. Whatever comes out of that description is the real rubric, and it is usually nothing like the adjective.

"What would you have wanted me to say instead?" Anchored to a moment, present tense. If he can answer it, you have a script. If he can't, write that down too.

"A year from now, if this were completely fixed, what would you see me doing that you don't see now?" Future observable behaviour is much easier for people to produce than a diagnosis. Managers who can't tell you what's wrong can often tell you what good looks like.

And one more, asked carefully: whose view is this? Not "who complained" — that starts a fight. Something closer to "is this coming from the leadership team, from peers, from your skip?" A single director who finds you irritating is a different problem, requiring a different response, from a consistent read across five people.

Turn whatever comes back into behaviour

When the phrase does decompress, it usually decompresses into one of a small number of things. Not because women all make the same mistake. Because managers only have a few things in mind when they reach for the word:

• You present the analysis and stop, leaving the room to draw the conclusion. They wanted the recommendation in the first thirty seconds and the analysis behind it.
• You answer the question you were asked instead of the question underneath it.
• You narrate your process out loud — "I wasn't sure whether to look at it that way, so I also ran…" — which sounds like thinking in public rather than having concluded.
• You only speak about your own area, and they're waiting to see whether you have a view on the thing two teams over.
• You've never disagreed with someone senior in front of an audience, so nobody in that room knows what you're like under pressure.

Take the ones that match and rewrite them as behaviours with a start date. Not "be more strategic" but "from Monday, slide one of every deck is the recommendation and the ask, and I don't walk through the workings unless someone asks for them." Two or three of those. Not eight. Eight is just a slower way of changing nothing.

Then write it down, because goalposts move

Send the email. Short, unemotional, to the person who signs off on the promotion.

Something like: following up on our conversation, my read is that executive presence here means these three things, and I'm going to work on them by doing these specific things, starting now. If that isn't what you meant, tell me now so I'm not solving the wrong problem.

That email does two jobs. It converts an adjective into a document, and it moves the burden of correction onto him — silence becomes agreement. If the same blocker appears next year, you can produce the email and ask which of the agreed behaviours didn't land. It's a lot harder to move a goalpost somebody wrote down and didn't object to.

Send it as an eager report, not as a challenge. The tone matters more than it should.

When nothing translates

Sometimes you run all of this and get nothing back. Two conversations, five questions, and every answer is another adjective. No meeting. No name. No sentence you could have said instead.

Treat that as information rather than as failure. It usually means one of three things: your manager is repeating something he heard and never observed; the feedback is a placeholder for a decision already made about headcount, budget or someone else's turn; or the discomfort is about who you are rather than what you do, in which case no behaviour change resolves it, because behaviour was never the input.

None of those gets fixed by trying harder. What they change is the question. It stops being "how do I fix this" and becomes "how many more cycles am I willing to run against criteria nobody will state, and what does leaving look like?" That's a heavier question. It's also the honest one, and answering it in month two is far cheaper than answering it in month eleven.

One caution against the opposite error: don't reach that conclusion after a single vague conversation. Vagueness on the first pass is ordinary. Most managers are bad at this, and quite a few are slightly afraid of the conversation. Give it two real attempts before you decide the feedback has no content in it.

If you want to rehearse it first

TrueTalk has an advisor pointed at this exact corner — Boss Babe Brittany, whose specialisms are women's leadership, executive coaching and the director-level ceiling. She's an AI persona, not a human coach and not your HR team, which is the reason you can paste in the literal sentence from your review at eleven at night and ask what it probably means and which question to open with. The first conversation is free; after that it's a subscription. What she can't do is tell you what your manager actually meant — nobody can do that from outside the room. What she can do is help you build the questions, and take a pass at the wording of that email before it goes to someone who outranks you.

The point isn't to be told you have it

The goal was never to hear, eventually, that you've developed presence. It's to make the word unnecessary — to drag the conversation onto things that can be observed, dated and disputed, where you actually have some purchase.

An adjective can be reapplied to you forever. A list of behaviours with dates on it either happened or it didn't.

Make him say what he means. Then make him write it down.