You can't coach what you won't name

The hardest part of executive coaching isn't the strategy. It's getting clear enough about what's actually happening to do something useful about it.

People arrive with a tidy version of the problem. Time management. Team alignment. Bandwidth. Those are real, but they're usually the presentable translation of something more specific and less comfortable to say out loud.

The stated problem and the real one

• "I need better systems" — I'm avoiding a conversation I don't want to have.
• "My team is underperforming" — I haven't told anyone what I actually expect.
• "I'm just tired" — I don't want this role anymore and can't admit it.
• "I need to be more strategic" — I'm afraid of being found out.
• "It's a busy season" — it's been a busy season for four years.

Nothing on that list is a character flaw. Naming things precisely is genuinely hard, especially for people whose competence is part of how they're valued. The vaguer version feels safer because it can't be held against you.

Why precision changes the work

A vague problem generates vague effort. A named one has edges: it suggests a first conversation, a boundary to set, a decision to make. Most of the momentum in coaching comes from that moment of accurate description — not from the plan that follows it.

That's most of what a good session is for. Not advice. A place where the accurate version can be said without cost, and then acted on.

What's the version you haven't said out loud yet?