He pointed at his stomach. I took the opening. “Good job, buddy. Now let’s put the carrot in our belly.”

He picked up the carrot and pressed it, firmly and with total commitment, into his belly button.

He did exactly what I asked. That’s the part I keep coming back to. He wasn’t ignoring me and he wasn’t resisting. He had full buy-in. He took my instruction, ran it through the only model of the world he had, and executed with confidence.

The breakdown wasn’t intent. It was translation. And I never saw it coming, because every signal on the surface looked like agreement. A nod, a reach, immediate action. The message had landed. Right up until it hadn’t.

The failure mode

Communication doesn’t transfer meaning. It transfers symbols: words, tone, a pointed finger. The receiver decodes those symbols against their own context. “Put the carrot in your belly” was never one message. It was two, the one I encoded and the one he decoded, and they overlapped just enough to feel like understanding.

That space between the message you send and the message that arrives is the Belly-Button Gap. The more confident and willing the receiver, the longer the gap stays invisible, because compliance looks identical to comprehension until the work comes back.

Anyone who has handed off work they cared about knows the scene. You brief someone sharp and motivated. They nod, they take notes, they go build. What comes back is a carrot pressed into a belly button: a competent, committed execution of a thing you never meant. The first instinct is to ask what they missed. The honest read is usually the reverse. I encoded for my context, they decoded in theirs, and I mistook the nod for a shared model.

The burden of being understood sits with the sender. Treating it any other way is resentment with a head start.

The practice

Stop treating “does that make sense?” as the check. Nobody fails that question.

The real check is: show me what you’re about to do. Have them play it back. Take the first step in front of you. Describe the end state in their own words. Make the decoded message visible before any real work rides on it.

Call it the Playback. At the dinner table it’s pointing at his mouth and saying “carrot goes here.” At work it’s “walk me through your first move before you build.” Same move. You’re closing the gap while it’s still cheap to close.

Operating implication: no brief is complete until the receiver has played it back. A definition of done that only exists in the sender’s head isn’t a definition. It’s a bet.

Some field notes come from the field. This one came from the dinner table.

When did someone do exactly what you asked and it still came back wrong? Reply and tell me. The best ones teach the rest of us.