Don't Be Clever. Be Clear. How to Make Technical Information Easy to Understand

https://youtu.be/Zmz5uh7LhFg

There's a particular expression that appears on people's faces when they've lost the thread of what you're saying. A slight squint, a polite nod, a look that sits somewhere between concentration and mild discomfort. If you've ever seen it while you were mid-explanation, you know exactly what I mean. And if you've ever been the one producing it — talking through something you know thoroughly while watching the room quietly disconnect — it's one of the more frustrating experiences in professional communication.

The instinct is usually to add more detail, to explain more thoroughly, to go back and cover the bit they might have missed. But that's almost never the problem. The problem, in most cases, is that the language got in the way of the message.

Here are five techniques I use and teach for making complex or technical information genuinely easy to follow.

The first is the most fundamental: don't try to be clever. Be clear.

There's a pull, particularly in professional settings, toward language that sounds authoritative and sophisticated. Words that signal expertise. Phrases that position you as someone who knows the technical terrain. And while there's nothing wrong with knowing your subject deeply, using that knowledge to impress rather than to communicate is where things go wrong. Jargon, complexity, and abstraction might signal competence to some people in the room — but they lose everyone else, and they never actually move anyone.

Martin Luther King didn't deliver a speech full of policy language and sociological terminology. He said "I have a dream." Four words. One of the most remembered and repeated speeches ever given, because anyone who heard it could immediately grasp what it meant and feel what it was asking of them. Simplicity is not a compromise. In most cases it's the more sophisticated choice.

The second technique applies when you genuinely can't avoid technical language — which does happen. Some fields require specific terms, and using them correctly signals that you know what you're talking about. The move here is to follow every technical term immediately with a plain English translation. Not as an apology, not as a footnote — just as a natural part of how you speak. "The rudder — in plain English, the part that steers the boat — needs to be adjusted." That one phrase does the work. Nobody feels talked down to, and nobody gets left behind.

The third technique is a variation on this, and it's worth practising until it becomes a reflex: use the words "which means." Say something technical, then say "which means," then explain it simply. Then say "which means" again and explain it from a different angle if needed. It sounds almost too simple, but it's remarkably effective — partly because the phrase cues the audience that a clarification is coming, and partly because it forces the speaker to actually find the plain language version. Your brain will find a way to simplify it when you commit to the structure.

The fourth technique is to use analogies and metaphors. This is one of the most powerful tools in any communicator's kit, and it's chronically underused in technical and professional contexts. An analogy takes something unfamiliar and maps it onto something the audience already understands. "It's like a GPS system." "It's like building a house — you have to dig the foundation first." "It's about the size of a shoebox." "It's as thick as your thumb."

These comparisons do something that definitions can't: they give the audience a mental image to attach the new information to. That makes it easier to grasp in the moment and easier to retain afterwards. This is particularly valuable in phone or audio-only conversations, where the person on the other end can't see what you're referring to — a well-chosen analogy does the visual work for them.

The fifth technique is storytelling. When an explanation is long, layered, or genuinely difficult to reduce to a simple phrase, the most effective thing you can do is wrap it in a story. Not a fictional one necessarily — just a scenario that the audience can follow in real time. Start with "you know when you walk into a room and you see..." or "imagine you're in a situation where..." and then walk them through it. The narrative structure carries people through complexity in a way that a sequential explanation rarely does, because the brain is wired to follow stories in a way it simply isn't wired to follow technical breakdowns.

The thread running through all five of these techniques is the same: communication is not about demonstrating how much you know. It's about transferring understanding from one person to another as efficiently and clearly as possible. The speaker who can do that — regardless of how technical the subject matter — has a genuine competitive advantage, in sales, in leadership, in any professional context where you need people to follow you.

It's not the people with the best product or service who win. It's the people who can explain it best.