The Explanation

You start explaining something, and somewhere around the third sentence, you hear yourself say something you didn't know you thought.

This happens more than we admit. You're walking a friend through your reasoning, or teaching a junior dev some concept you've "understood" for years, and you say: "The reason we do it this way is..." and then you pause, because what just came out of your mouth isn't what you thought you believed. It's not wrong, exactly. It's just not the explanation you were holding before you started speaking.

The philosopher Daniel Dennett called this "thinking about thinking" — but that's not quite it. That's too deliberate. This is more like: thinking out loud and being surprised by your own voice.

I remember teaching a friend to drive stick shift. I'd driven manual for fifteen years. I'd explained it dozens of times: "You feel for the bite point, where the engine engages..." But this time, mid-sentence, I said: "You're not really releasing the clutch. You're looking for the moment the car wants to move."

That wasn't my usual explanation. My usual explanation was mechanical. This was... something else. Something about intention and momentum and reading the machine's desire. And I thought: huh, is that what I've been doing?

It was. I just hadn't needed to know it until I tried to say it out loud.

The gap between knowing and teaching is well-documented. We've all had that moment where someone asks "wait, why?" and we realize we have no idea. We memorized the steps but never the reason.

But there's another gap, less discussed: the gap between teaching and discovering.

You can rehearse an explanation until it's smooth. That's not this. That's performance, and performance hides the revealing moments. No, this is when you're explaining something genuinely — not repeating what you've said before, but actually trying to reach someone — and your brain, forced to produce words at the pace of speech, outputs something your conscious mind hadn't approved.

Sometimes it's embarrassingly simple. You're explaining why you made a decision, and you hear yourself say: "I didn't want to deal with the conversation." You'd been telling yourself it was about efficiency. Out loud, it was about avoidance. Your mouth was more honest than your narrative.

Sometimes it's the opposite — your unconscious understanding is more sophisticated than you'd given yourself credit for. You explain a tricky concept, and what comes out is an analogy you've never thought of before, one that actually illuminates it better than your prepared explanation. You think: where did that come from? From years of operating on an understanding you'd never needed to articulate.

This is why some of the best insights come when explaining to someone who isn't an expert. Expert-to-expert explanations are efficient — compressed, jargoned, optimized. They move fast because both parties know the landscape. But the novice asks the obvious question, forces you to slow down, forces you to strip away the shorthand. And in that slower pace, in the space where you can't hand-wave, you sometimes find your own understanding arranged differently than how you'd stored it.

The explanation is the autopsy of your knowledge. It doesn't show what you thought you knew. It shows what you actually use when you need to make sense.

There's a particular kind of conversation — you might call it the explanation loop — where two people take turns explaining things to each other, not for status or performance, but because they're genuinely curious what will emerge. These conversations often feel strange at first. Most of us have learned to hoard our explanations, to offer them only when demanded, as if they're finite. But in the loop, you offer explanations freely, half-formed ones, ones you're not sure about, and the other person does the same, and sometimes the only reason you're explaining something is to find out what you think about explaining it.

These conversations generate new positions. Not like arguments, where positions harden. The explanation loop softens. You say something, realize it's incomplete, revise it in real-time. The other person doesn't contradict — they extend. "And also..." they say, and your half-formed thing grows a new branch, one you couldn't have grown alone.

This is different from brainstorming, which tends toward quantity. This is toward coherence. You're building something together, and the material is your own understanding, which you've never had to articulate this way before.

We talk about "finding your voice" in creative work, but there's also finding your voice in explanation — learning to trust what comes out when you're genuinely trying to be understood. Some of us have trained ourselves, through years of corporate communication, to lead with the approved explanation. The safe one. The rehearsed one. That version never surprises. It's not supposed to. It's the opposite of the explanation loop. It's the explanation bullet.

The explanation bullet is the one-way delivery of a prepared message. Teachers sometimes do this. So do leaders, politicians, experts of all stripes. They've said it so many times they don't hear it anymore. They don't discover anything in the saying. The bullet is a fixed object. It lodges.

The explanation conversation is different. It's an exploration. It has to be two-way. Not in the sense that the other person contributes content — they may know nothing about the topic — but in the sense that their presence forces you into a different relationship with your own knowledge. You're not reciting. You're building.

A friend of mine, a brilliant technologist, once said: "I don't know what I think until I see what I write." Writing as a form of thinking. But the timeline of writing allows for revision. You can see what you wrote, cringe, rewrite. The explanation, spoken, has to be real-time. The discovery is public. You can't hide your surprise at yourself.

This is vulnerable, and not everyone wants to do it. The bullet is safer. The bullet shows competence. The explanation conversation shows process.

But process is where the interesting things happen.

I've learned to notice when I'm surprised by my own explanation. That moment of "wait, did I just say that?" is a signal. Something was stored differently than I'd presented it to myself. The explanation reached for it and found a more honest node.

The art, then, isn't to eliminate surprise but to notice it. To not let your prepared explanation become so rehearsed that it never reveals anything new. To stay in the explanation loop, where the goal isn't to convey information but to discover the shape of your understanding.

The best way to explain something, sometimes, is to find someone who doesn't know it and genuinely try to help them. Not for them — though they'll benefit — but for you. For the moment when you hear yourself say something true that you hadn't planned on knowing.

The explanation isn't a transfer mechanism. It's a mirror. Not a smooth mirror that shows what you're performing, but a mirror with depth — one that shows not just what you're saying but what you're drawing from.

We learn our own minds by watching what comes out of our mouths when we're trying to help someone else understand theirs.