To explain a complex idea clearly, give people the question or decision first. Group the supporting details into a few meaningful points, explain unfamiliar terms, and show what your insight changes. Keep the nuance that affects their understanding or decision. Use these 4 passes to check what your audience needs next.

the 4-pass check

You can use these passes on a project update, presentation, article, or AI prompt. They are a check on your explanation, not a script you have to recite.

what a clearer update sounds like

In consulting, we regularly conducted expert interviews to gather information for a project. An update could easily turn into a recap of the questions we asked, the answers we received, and where we ran out of time.

The listener then had to extract the progress, finding, risk, and next step while we were still talking.

For example, imagine reporting on 10 completed interviews to decide whether they support a recommendation. These are illustrative versions of the same update, with brackets for the findings you would supply.

Before: “We completed all 10 interviews. We went through most of the questions. A few experts couldn't answer some of them. There was a lot of agreement, although a few people said something different that we're following up on...”

After: “We're checking whether the interviews support [recommendation]. All 10 interviews are complete. Most experts agreed on [main finding]. A smaller group raised [emerging signal], an observation we still need to verify. We're following up this week to see whether it changes the recommendation.”

The first sentence orients the listener around a decision. Grouping the details into progress, finding, and follow-up calibrates the update. Explaining why the follow-up could change the recommendation connects the information to its consequence. Calling the signal an observation still to verify defines its status and preserves uncertainty.

The useful detail stays. The listener can now see what it means.

why expertise needs translation

We assume that because we know something deeply, other people should get it when we explain it. But your expertise contains years of accumulated context. The audience receives only the words you choose in that moment.

You see patterns faster. You know which exception matters. You remember the 5 decisions that brought the project here, so the 6th decision feels obvious. The person listening does not have that compressed history.

Researchers have documented one version of this problem as the curse of knowledge. Better-informed participants struggled to fully set aside what they knew when estimating the judgments of less-informed people. That supports a narrower point: knowing more can make it harder to predict the perspective of someone who knows less.

I call the result we want Visible Expertise: the ability to translate deep knowledge so people without your context can understand the point, see its value, and use it. You can apply these ideas in 4 passes.

1. orient: give people the map

Before you explain the work, ask what the audience needs to know about where you are.

Experts often jump into the current problem because they remember every phase that led to it. To everyone else, the information arrives without an arc. Every detail sounds equally urgent.

I use Phase Framing to locate people in a larger sequence: where we are, what brought us here, and what comes next. An illustrative project update might begin:

“We're in validation. Discovery confirmed that the problem exists, so now we're testing whether our proposed solution solves it. 3 tests are running this week. Depending on the results, we'll either move into build or reframe the solution.”

That gives people context, logic, scope, and the next decision without a history lesson. On the spot, you can compress it further:

“We're in validation. Discovery confirmed the problem, and now we're testing the solution.”

If your explanation is about an idea rather than a project, name the question it answers. The audience still needs to know what they are trying to understand before the details arrive.

The CDC's Clear Communication Index recommends making 1 main message clear in 1–3 short sentences. That is a useful check here: can someone tell what this explanation is for before they start sorting through the detail?

2. calibrate: adjust the level of detail

Once people know where they are, check whether they can work with the information you are giving them.

Complex explanations often fail at 2 extremes. An under-chunked explanation gives people separate details without grouping them into a meaningful concept. An over-chunked explanation gives them a compressed concept or abbreviation they cannot unpack.

I think of this as a Chunk Dial. Details without a concept lose people. A concept without details loses meaning.

Research on verbal working memory examines how limited memory capacity and grouping words into chunks affect recognition. It supports the underlying constraint that we cannot hold unlimited verbal information in mind. The Chunk Dial is my practical way of thinking about an explanation, not a method tested in that study.

The interview update was under-chunked. Grouping its details into progress, finding, and follow-up gave the listener somewhere to put each piece of information. If you tend to ramble, ask: What single concept could hold these details together?

The opposite problem was especially clear during my first week at Google. It felt like everything had an abbreviation. Meetings were filled with names for internal tools, processes, teams, and metrics. Everyone else could think efficiently in shorthand. I was trying to decode the language while keeping up with the discussion.

Often, a short phrase would have been enough:

“We use OKRs. Think of them as goals for now.”

“For now” gives someone a foothold while signaling that more nuance exists. It does not make OKRs and goals identical. If the discussion turns to how to write or evaluate an OKR, that fuller distinction becomes necessary.

The right level of detail depends on what the listener needs to do next.

3. connect: show why the detail matters

An explanation can be understandable and still leave people wondering what your point changes.

I understood this more clearly while walking through a Monet exhibition in Tokyo. Stand too close to an oil painting, and individual strokes can look disconnected. A white mark is just a white mark. Step back, and those same white marks make the whole painting shimmer. Their meaning comes from their relationship to the whole.

Details work the same way. Your analysis may be rigorous. Your observation may be the thing everyone else missed. But if you do not articulate where it fits, the room experiences it as another detail.

“Get to the point” often means: Zoom out and show me why this detail changes the picture.

That does not mean making the point you think executives want to hear. In one of Monet's Parliament paintings, the building was prominent, but what drew my attention was the effect of light and fog. That observation became the focus.

Your value may also be noticing an effect, risk, or relationship that others missed. Keep the insight. Translate its consequence by asking what you are seeing, why it is happening, and what changes because of it.

In the interview example, the follow-up matters because it may change the conclusion. That is the connection the audience needs to understand why the work continues.

4. define: make shared language precise

Once people can see the point and its consequence, make sure the words you use will support the next conversation.

Calibrating gets people into the explanation. Defining helps them use it accurately. A quick approximation may be enough to follow a meeting. A decision may require a more precise distinction.

For example, “emerging signal” in the interview update means something worth investigating. It does not mean a finding strong enough to support a recommendation. If people use those terms interchangeably, a concise update can create false confidence.

Name the distinction that matters. Explain it once. Then shared language can make the next conversation sharper.

This also matters when you work with AI. If your prompt asks for “insights” but never explains what separates an observation from a useful conclusion, the output may blur a distinction you care about. Give the model the context and standards your explanation depends on.

common mistakes

Removing the nuance that changes the decision. Keep uncertainty, exceptions, and limitations when leaving them out would change what someone should conclude or do. Clarity can include “we do not know yet.”

Giving the entire backstory. Often, the previous phase and the current question are enough. Add history when the listener needs it to understand the reasoning.

Eliminating all jargon. Shared shorthand is useful among peers. Explain it for people who are not yet inside it, then use it when it helps.

Treating the 4 passes as a rigid speaking order. Use them to find what is missing. A brief update may need a sentence of orientation and a clearer next step. A technical decision may need substantial supporting detail.

if you enjoyed this...

For more ways to make your thinking easier to express, watch How I Became Articulate With My Speaking (5 Secrets).

resources

Drowning in complexity? Use the Complexity to Clarity frameworks to build mental models to make sense of ambiguity and communicate it clearly to others.

try this on your next update

Take an update you are already preparing. Check it for orientation, the right level of detail, a clear consequence, and shared definitions. Repair the part that makes your audience work hardest.

Before adding another fact, ask: What does the room need before this detail will make sense?