Somebody is fifteen words into telling you something and you already have your answer.

You're not being rude. You're being fast. You've heard a version of this before, you can see where it's going, and somewhere around their second sentence a response assembles itself in your head. So you hold it. You nod. You make the listening face while you wait for the gap.

Then the gap comes, you say your piece, and it's a good piece. Accurate. Useful. Possibly generous. And it lands about four feet to the left of what they actually meant.

You can watch it happen on their face. Something closes. They say "yeah, no, you're right," which is the phrase people use when they've decided to stop trying.

What's actually happening

The answer wasn't wrong. You solved a real problem well. It just wasn't theirs.

That's the failure mode almost nobody catches, because from the inside it feels like competence. You were quick, you were engaged, you contributed. The only thing you skipped was confirming what you were responding to — and skipping that step never announces itself. There's no error message when you understand someone incorrectly. There's just a slow accumulation of people who stop bringing you things.

This is the friction the third commitment is built to name. Always Understand First isn't a rule about being nicer in conversation. It's a diagnosis of a default setting. Left alone, your factory default is reply. Understanding is the part you have to add on purpose.

Why the usual fix doesn't hold

The standard prescription is active listening, and most of us have sat through the training.

Maintain eye contact. Don't interrupt. Reflect back what you heard: "So what I'm hearing you say is..." It isn't bad advice. But run it as a technique and people feel the technique. They can tell the difference between being understood and being processed, and the reflecting-back move in particular has been used on all of us enough times that it now reads as a stall — the thing someone does right before they explain why you're wrong.

The deeper problem is that listening isn't a skills gap. You already know how. You skip it because understanding costs you something specific in that moment: either the satisfaction of being right, or the relief of being done. Both are real. Understanding first means paying one of them, on purpose, while the other option is sitting right there.

Proverbs says it without softening: "If one gives an answer before he hears, it is his folly and shame." (Proverbs 18:13)

Not his inefficiency. His folly. The text puts premature answering in the same category as bad judgment, which is a harder claim than it first sounds — it means the confident, well-constructed, immediate response is not a neutral event. It's a mistake wearing the costume of a contribution.

Where style enters

Now the part that gets left out of every listening seminar: understanding does not look the same coming from different people.

Some people understand by talking. They ask a question, then another, then a third, and the shape of what you meant emerges out loud between the two of you. Others understand by going quiet — reading tone, watching what you avoid, sitting with it long enough for the actual issue to surface. Both of those are real comprehension. And each one looks like failure to the other. The asker seems like an interrogator. The quiet one seems checked out.

So when you hand somebody a single prescribed method, you're asking most of them to fake a form of attention that doesn't match how their mind actually works. It holds for about two weeks. Then it collapses and they conclude they're bad at listening.

They're not bad at listening. They borrowed the wrong instrument. The commitment is fixed — understand before you answer. How you get there is yours.

The practice

Find the ask before you answer. Almost every conversation is one of three requests: fix this, decide this with me, or just know about this. Answering a know about this with a fix this is the single most common way to make someone feel unheard by someone trying hard to help. If you're wired to solve: ask it flat out — "do you want me to help with this or do you just want me to hear it?" Nobody has ever been offended by that question. If you're wired to hold back: the risk runs the other way. You may need to say "do you want my read on this?" out loud, because your silence is being filed as agreement.

Ask one more question than feels necessary. The moment you feel ready to respond is the moment you've formed a theory, not the moment you've confirmed one. Spend one question testing it. If you process out loud: ask about the part you assumed — "when you said it's been fine, what does fine mean here?" If you process internally: your one question can be as small as "what else?" and then genuinely wait. That's often the question that gets you the real thing.

Say it back badly and let them fix it. Not the polished reflection — a rough attempt, offered as a draft. "So this is less about the deadline and more about being left out of the decision?" Being slightly wrong in the open invites correction, which is exactly what you want. If precision is your thing: resist the urge to summarize elegantly. Elegant summaries end conversations. If warmth is your thing: make sure you're actually restating content and not just affirming feeling. "That sounds hard" is care. It isn't yet understanding.

Catch the moment you leave. You know the feeling — the small click when your attention shifts from them to your response. Learn what it feels like, and when it happens, come back. If you're comfortable being direct: just say it. "I got ahead of you, say that last part again." It costs four seconds and buys back the whole conversation. If that feels too exposed: ask them to keep going. Same result, less overhead.

The close

Being understood is the rarest thing you can give someone, and the only price is going second.

Always Show Up As You.