How to recognize and repair an explanation while speaking.
You can hold several parts of an idea in mind at once. Someone listening must encounter them one at a time.
They may begin with different knowledge, assumptions, or questions. They cannot see the connections you see, and you cannot know exactly what they understand.
Your task is to find a path from what they know to what they need to know.
That path may require a definition, an example, a missing step, or a corrected assumption. Sometimes you'll discover that you've been answering the wrong question. Sometimes you'll find a gap in your own reasoning.
The skill is recognizing what isn't working and knowing what to do next.
1. Find the explanation they need
Before speaking, ask:
What is this person trying to understand, and what is preventing them from understanding it?
Don't assume you know their starting point. Find out when it matters.
Give them a point to follow: an answer, a problem, a question, or an observation that organizes what comes next.
An explanation may need to perform four jobs:
- Orient. Establish what we're talking about.
- Explain. Show how the relevant parts relate or why something happens.
- Ground. Make the relationships visible through an example or evidence.
- Resolve. Answer the question and establish what follows.
These are functions, not a fixed sequence. Sometimes the answer comes first. Sometimes an example is the best opening. Sometimes only one connection is missing.
What matters is the order of understanding: establish each necessary idea before asking the listener to use it.
Don't confuse explaining something with recounting how you discovered it. Your path to understanding may not be the best path for someone else.
2. Learn to catch yourself
Your own speech often reveals where an explanation is failing.
| Catch yourself when… | What may be wrong | Repair |
|---|---|---|
| You keep saying it, this, or that. | The subject is unclear. | Name it again. |
| You introduce several abstractions. | The listener lacks a concrete referent. | Describe what happens in practice. |
| You explain what something isn't. | You're defining by exclusion. | Say what it is. |
| You introduce another metaphor. | The first hasn't done its work. | Finish one comparison. |
| You keep saying and also. | You're opening new branches. | Complete the current thought. |
| You repeatedly say what I mean is. | You're restating without diagnosing. | Find the missing distinction. |
| You bury the claim in qualifications. | The point is hard to find. | State it with the qualifications it needs. |
| You explain a consequence before its cause. | A necessary step is missing. | Show the connection. |
| You continue after answering. | You're adding without purpose. | Stop. |
These are clues, not prohibitions. Abstraction, metaphor, repetition, and qualification can all help.
The question isn't whether you've used a device. It's what work the device is doing.
Notice what the listener does
Their responses offer another kind of evidence.
- They ask about something already explained. A term or prerequisite may still be unclear. Find the first point of confusion.
- They object to a claim you weren't making. Your wording may imply something unintended. Clarify the distinction.
- They repeat your claim but cannot apply it. They may remember the words without understanding the relationship. Try a changed example.
- They ask a narrower question. You may be explaining more than they need. Answer it directly.
These signals are imperfect. A quiet listener might be confused, satisfied, distracted, or thinking carefully.
Not every pause needs repairing.
3. Repair the gap, not the length
When an explanation falters, the temptation is to say more. But more information may only make the difficulty harder to locate.
Use a simple cycle:
Notice → Diagnose → Repair → Check
Find what is wrong before choosing what to say next.
Missing connection: The listener doesn't know how one thing leads to another.
“I skipped a step. Here's what connects them.”
Mistaken connection: The listener assumes a relationship that may not hold.
“Are we assuming that one necessarily leads to the other?”
Lost subject: The listener no longer knows what you're referring to.
“More plainly, we're talking about…”
Too many ideas: You've started another thought before completing the first.
“Let me finish the first point.”
Wrong question: You've answered something adjacent to what was asked.
“I explained how it works. You asked why we need it.”
Unsupported claim: You've stated more than the evidence warrants.
“I stated that too strongly. Here's what we know.”
Make the smallest useful correction, then check whether it helped.
Don't assume the listener is mistaken. Their objection may expose a weakness in your own explanation.
4. Make the relationships visible
Consider:
“We need a system for maintaining coherence across agentic development surfaces.”
The sentence names a concern but leaves the relationships unexplained.
Try:
“A team records a product decision in a plan, translates it into a design, and implements it in code. Those three things can change independently. Someone updates the code without updating the plan or design. Now they may disagree about what the product should do.”
We can now discuss coherence because we've established what the word refers to.
But suppose the listener believes that the design and code must agree because they began with the same plan.
The missing explanation is different:
“They started from the same plan, but they can change independently afterward. A shared starting point doesn't guarantee continued agreement.”
This corrects an assumption rather than merely supplying more information.
Naming a relationship is not the same as explaining it.
A good example can reveal how something works, expose an assumption, or show why a plausible explanation fails.
And when significance matters, ask: What difference does knowing this make?
Here, the team might ship behavior that no longer reflects the intended decision.
That's why the disagreement matters.
5. Make the reasoning accountable
An explanation can be clear and still be wrong.
Before making a claim easier to understand, distinguish:
- Observation: What have I established?
- Inference: What am I concluding?
- Mechanism: What connects cause and effect?
- Assumption: What must be true?
- Uncertainty: What remains unknown?
Don't turn a possibility into a certainty, a correlation into a cause, or a proposed explanation into an established fact.
Consider someone asking, “Why does this product need AI?”
Explaining how a language model performs the task doesn't answer why AI is needed.
A better answer might begin:
“It may not need AI. We should first establish whether simpler rules can handle the task reliably.”
The right answer sometimes begins by questioning the premise.
Clarity should reveal the reasoning, not conceal its weaknesses.
6. Check understanding, not agreement
A listener may nod without understanding. They may disagree while understanding perfectly.
When understanding matters, find out whether they can use the idea.
Can they explain the relationship in their own words? Apply it to another situation? Reason about what changes when a condition changes?
Ask when appropriate:
“What part needs more explanation?”
“Is that the distinction you were asking about?”
“What would happen if we changed this?”
Don't turn every conversation into an examination. Choose the check that fits.
If their interpretation differs from yours, find where the two understandings diverged before repeating yourself.
7. Practice finding the first failure
Choose one idea. Explain it aloud for sixty seconds and record yourself.
Listen as though you don't already know what you meant.
Find the first place someone might reasonably lose the thread. Did you skip a relationship? Introduce an unfamiliar term? Start another thought? Answer a different question?
Repair that passage and record it again.
Then listen for where you could have stopped. Another sentence doesn't always make an explanation better.
Finally, explain the same idea to someone with different prior knowledge. Notice what you can omit, what you must establish, and which assumptions need examination.
The tables are for learning to recognize problems. In conversation, you need only remember the cycle: Notice, Diagnose, Repair, Check.
The goal is to recognize these problems while speaking, not just afterward.
A checklist for speaking
Before: What are they actually asking? What do they already understand?
Begin: Have I given them a point to follow?
Explain: Have I established each relationship before relying on it?
Notice: What do my words and their responses suggest?
Repair: What's missing, mistaken, irrelevant, or unsupported?
Check: Can they use the explanation?
Stop: Have I answered the question?
The measure of an explanation is not how complete it feels to the speaker.
It is what the listener can understand, reconstruct, question, and use without the speaker.