Eyes glaze over when your description gives somebody nothing to picture. Three things cause it: you're describing tactics when a client wants an end state, you're using words that sound like meaning without carrying any, or you're listing several outcomes at once. All three are fixable in a sentence, and none of them is about how interesting your work is.
Replace the abstract word in your description with the thing a client could picture happening.
People can rehearse a specific end state in their head, and they can't rehearse a concept.
Read your description aloud and circle every word that names no visible thing.
Clients can't fall in love with a concept. They can only fall in love with the future that they can rehearse.
Leah Neaderthal, Smart Gets Paid
A description becomes unpicturable when it names a category of improvement without naming what changes. "Helping teams have strategic conversations" describes real work and leaves the listener with no image, because a strategic conversation could be almost anything and lead almost anywhere. That's the level most consultants answer on when somebody asks what they do.
Compare two descriptions of similar work:
| Nothing to picture | Something to picture |
|---|---|
| Helping leaders build happier workplaces through mediation and manager training | I help leaders develop an unshakeable core to navigate change with more ease |
| Coaching leaders to achieve goals for greater impact | I help unfulfilled high achievers find work they love |
| A diagnostic process that gets you where you want to go | Never worry again if your US expat taxes are done right |
The right column works because a listener can feel it for a second. My favorite version of this isn't from consulting at all: a construction site near my house has a sign saying their number one priority is to send workers home safe to their families. They could have written that safety is their priority. They wrote the thing you can see.
That's the test. Can somebody rehearse it, even for a split second? If they have to do any assembling to get there, they won't do it.
Six words do the most damage, and they're the ones that feel most professional: thrive, accelerate, impact, success, growth, and transform. Each names a concept and no end state, which is why I keep them in word jail.
The problem isn't that they're vague. It's that they require your listener to supply the content. "I help companies accelerate growth" asks them to decide what growth means, how much, and by when, and a busy person declines that work without noticing.
The same trap has a corporate-speak version:
That last one costs you credibility. Go far enough past what you can plausibly deliver and a reader stops believing you at all.
The fix is the same in every case: say it the way your clients would say it. If you wouldn't use the phrase standing in a grocery store line, it doesn't belong in your description.
Here are the steps to find your own:
Listing several outcomes hurts, because a list asks a listener to work out which item matters and a single clear end state doesn't. This is the trap I see most in consultants who are good at a lot of things.
A real example of the shape: "I help business owners define what they do, focus their niche, find words with confidence and attract clients." Every item on that list is accurate. Together they read as a menu, and a menu is something you skim.
The alternative is what I call the side door: go straight to what clients say they want, in their own words. Ask what a win physically looks like for them, and use their answer. Building the sentence deliberately usually comes down to one question like that one.
Your jargon is a bigger factor than the complexity of your work, and there's research on it worth knowing about. Complicated work can be described plainly. Plain descriptions of complicated work are what expertise sounds like from outside.
Hillary Shulman and Olivia Bullock ran an experiment with 393 US participants across three topics and measured what jargon did to comprehension and persuasion. The pattern split by how urgent the topic felt:
| How urgent the topic felt | What jargon did |
|---|---|
| Low urgency (flood risk) | Significantly harder to process, and less persuasive |
| Control (emergency policy) | Significantly harder to process, and less persuasive |
| High urgency (a live pandemic) | No measurable effect |
Their explanation is that motivated readers push through language difficulty, because they're focused on the substance rather than on how the sentence feels.
Read that against your own situation. In a first conversation your listener is almost never at maximum urgency, which is exactly the condition where jargon cost both comprehension and persuasion. Their caveats are worth carrying: one message set per topic, an online participant pool, and the authors calling for replication.
There's a related reason you can't see your own jargon. You can't read the label from inside the bottle. The words that lost your listener are the words that stopped registering as words to you years ago, which is why describing the problem in your client's language is the reliable way out and self-editing is not.
I want to be careful here, because this is one of those problems where the cause looks like a personal failing and it isn't.
The language that makes eyes glaze over is, almost always, the language somebody was trained to use. In corporate, abstraction was safety. Saying "we drove impact across the portfolio" got you through a review; saying "we got 200 more people to renew" invited questions about the other numbers. You were rewarded for words that couldn't be checked, for years, and then you left and started a business where the same words cost you clients.
So the fix isn't to be more interesting. It's to be more specific, which feels riskier and is the opposite of risky. Concrete claims are the ones people believe.
One more thing about the glazed look itself. It's information, and it isn't a judgment. Somebody's face going neutral while you talk is the cheapest feedback you will ever get about your messaging, and it arrives free, in real time. Most consultants respond by talking more. Write down what you'd said in the ten seconds before the face changed, and you'll usually find the abstract noun sitting right there.
No, and that framing is the reason people resist this. Plain language is not simplified content; it's the same content with the abstraction removed. A specific sentence about a sophisticated problem sounds more expert than a vague one, because only somebody who understands the work deeply can describe it without hedging.
Shared vocabulary inside a specialty isn't jargon in that room, so keep it. It's shorthand that saves everybody time. The test is whether the person in front of you uses the word unprompted. Terms your clients say back to you are fine, and terms that come from your own training and never from their mouths are the ones to cut.
Read your description aloud and mark every word that names no visible thing. Abstract nouns ending in -tion, -ment and -ity are the usual suspects, along with the six in word jail. Then hand the sentence to somebody outside your field and ask what they picture. If they describe your process back to you, the sentence is still about you.
One description, delivered the same way, works better than several. Consultants often build a technical version and a simple version and end up delivering an uneasy blend of both. Pick the version your ideal client would say, and use it with everyone, including peers. They'll respect it, and the people who can hire you will understand it.