There’s a specific tension every expert faces when communicating their work. It’s not about whether you know enough. It’s about where you set the dial.
Go too technical: the work isn’t approachable. The prospect can’t see themselves using it. The client feels like they need a translator just to follow the conversation. They disengage — not because they’re not smart, but because the cost of staying engaged is too high.
Go too simple: the work doesn’t appear valuable. You’ve hidden the sophistication that earns the premium. The prospect sees a commodity. They wonder if they could just do this themselves.
The complexity dial is real. And finding the right setting isn’t instinct — it’s a learnable skill.
Why the Default Is Always Too Technical
Experts default toward complexity for a reason that feels rational: you want people to understand what you built. You’ve invested in the architecture, the system, the methodology. You want credit for it.
The problem is that credit for complexity doesn’t come from complexity itself. It comes from the outcome the complexity produces. And outcomes are most legible when they’re explained simply.
When someone asks you what you do, they are not asking for the architecture. They are asking for the result. “I build AI-powered content systems that rank on Google” is more credible to a non-technical buyer than a description of the pipeline that produces it — even though the pipeline is impressive, and even though you should absolutely understand and be able to speak to it when the moment calls for it.
How to Find the Right Setting
The right complexity setting is not a fixed point. It moves based on who you’re talking to, what stage of the relationship you’re in, and what decision you’re trying to help them make.
A useful calibration question: what is the one thing this person needs to understand to move forward?
Not the ten things. Not everything you know. The one thing. That’s your anchor. Build your explanation from that point outward, adding complexity only as far as is necessary to make that one thing credible and actionable.
Another useful signal: listen for when someone stops asking follow-up questions. In a live conversation, the questions stop either because they understand or because they’ve given up. Your job is to read which one it is. Silence after complexity is usually disengagement, not comprehension.
The Two-Version Rule
For anything you communicate regularly — your services, your process, your results — it’s worth building two versions deliberately:
The technical version is for peers, for audits, for documentation, for conversations where the other person has signaled they want to go deep. It doesn’t simplify. It’s accurate and complete.
The accessible version is for first conversations, for clients who are focused on outcomes, for anyone who hasn’t yet signaled they want the technical version. It doesn’t dumb things down. It leads with the result, earns the trust, and holds the technical detail in reserve.
The mistake is using only one. The expert who only has the technical version loses approachable audiences. The expert who only has the accessible version never earns sophisticated ones.
What This Looks Like in Real Work
A client asks: “What do you actually do for SEO?”
Technical version answer: “We run a full AEO/GEO content pipeline with schema injection, entity saturation, internal link graph optimization, and structured FAQ blocks targeting featured snippets and AI overview placement.”
Accessible version answer: “We make sure that when someone searches for what you do, Google shows your site — and shows it in a way that answers their question directly, so they click.”
Both are accurate. Only one is appropriate for the first conversation with a prospect who runs a restoration company and has never thought about AEO in their life. The technical version comes later — after the trust is built, after they’ve asked to understand more, after the relationship has earned it.
What is the complexity dial in communication?
The complexity dial refers to the register of technical depth you use when explaining your work. Too technical and you lose approachability. Too simple and you sacrifice perceived value. The right setting depends on who you’re talking to and what decision they need to make.
Why do experts default to overly technical communication?
Experts default toward complexity because they want credit for what they built. But credit comes from the outcome, not the architecture. Outcomes are most legible when explained simply.
How do you find the right complexity level?
Ask: what is the one thing this person needs to understand to move forward? Build your explanation from that anchor, adding complexity only as far as necessary to make it credible and actionable.
Should you always simplify your communication?
No. The goal is calibration, not permanent simplification. Build both a technical version and an accessible version of your key messages, and deploy each when the audience has signaled which one they need.
Leave a Reply