There's a particular kind of overwhelm that has nothing to do with workload.
It's the feeling of being pulled in multiple directions by something you can't quite name.
You know something is off, something is building, but when you try to explain it, even to yourself, the words don't come.
This is more dangerous than it looks. What you can't articulate, you can't address.
It stays in the background, shaping your decisions, draining your energy, creating a low hum of anxiety that never fully resolves.
The unnamed thing runs the show precisely because it hasn't been brought into the light.
There's a line I come back to often: if you can't name the next wave in one sentence, you're already under it.
What Staying Vague Costs
When a challenge remains undefined, everything around it gets harder. Your team senses that something is coming but doesn't know what. They fill the silence with their own stories, usually worse than reality. Alignment becomes impossible because there's nothing specific to align around.
You feel it too.
The mental load of carrying something unnamed is heavier than carrying something clear.
Clarity, even about something difficult, creates relief. Ambiguity creates drag.
This is why some leaders seem calm in crisis while others spiral in uncertainty.
It's not that the calm ones face easier problems.
It's that they've named what they're facing. The naming itself changes their relationship to it.
Keeping the challenge private makes it worse.
You tell yourself you're protecting the team, or that you need to figure it out first before you share.
But what actually happens is that the weight stays entirely on you, and the organization loses the chance to help carry it.
What Naming It Opens
Something shifts when you say it out loud.
The vague dread becomes a specific challenge.
The thing that felt overwhelming becomes a problem with edges, something you can actually work with.
Anticipated pains are roughly half as painful on arrival.
Not because you solved them early, but because your nervous system isn't in shock when they show up. Part of you already said: this is coming, and I can meet it.
Naming the wave publicly does something else too. It creates energy.
Your team now knows what they're working toward and what they're working against. The shared clarity becomes fuel.
What was private drag becomes collective momentum.
This requires a kind of courage that doesn't look dramatic from the outside.
It's the willingness to say "I don't have this figured out, but here's what I see coming."
It's trusting that articulation is leadership, not a sign of weakness.
The Practice
Try this:
What is the biggest challenge facing you or your company in the next six to twelve months?
Can you name it in one sentence?
→ If you can, notice how that feels.
→ If you can't, that's information too.
Sometimes the reason you can't name it is that you haven't let yourself fully acknowledge it.
The vagueness is a form of protection.
But protection from what? Usually from the grief or fear or identity shift that the challenge implies.
The leaders I work with often discover that naming the thing is most of the work. Once it's said, the path forward becomes strangely obvious. Not easy, but clear. The energy that was spent managing ambiguity gets freed up for actual movement.
Every wave demands a different version of you.
You can't become that version until you name what's asking you to change.
What's the wave you haven't named yet?
Curious where your blind spots are? Take the free CEO Mirror Quiz.
And if something landed today, hit reply. I read every one.
