Information Is Not a Point

You have been on the receiving end of this. Someone sends a research summary, or presents a project update, or writes up their findings after two weeks of investigation. The document is thorough. It covers the history, the data, the tradeoffs, the context. And when you finish reading it, you still don’t know what they think you should do.

The work was careful. The communication failed.

Most people treat communication as information transfer. Get the facts across. Share the context. Let the other person draw their own conclusion. This feels respectful, even rigorous. But it confuses the act of sharing with the act of thinking. Information transfer is not communication. Communication is what happens when someone knows what you think and what you want from them.

The bottleneck is almost never information. People have more context than they know what to do with. What they lack is someone who has processed that context and arrived somewhere. The value is in the conclusion, not the inputs.

The gap between processing and arriving is where most communication fails. Not because the information is wrong, but because no one took the last step. They stopped at “here’s what I found” and handed the work back to the reader. The reader now has to do the part the writer was best positioned to do.

Weasel words are the visible record of this. “It might be worth considering whether we should potentially explore…” reads like caution. It is actually a record of someone who didn’t push through to a point. Hedges aren’t intellectual humility. They’re the residue of unfinished thinking. The test is simple: remove the hedge. If the sentence becomes false, it was load-bearing. If it just becomes clearer, it was avoidance.

The same dynamic appears at the level of the whole document. A recommendation that ends with three options and no preference hasn’t communicated. It has delegated thinking to the reader. “Here are three options, and I recommend the second one because…” is different in kind, not degree. One transfers information. The other transfers thought.

What “having arrived” looks like varies. A board memo looks different from a Slack message. A technical postmortem looks different from a 1:1 check-in. The form adjusts. The underlying question doesn’t: have you actually gotten somewhere, or are you describing the journey and leaving the destination to the reader?

A useful diagnostic: try to state your bottom line in one sentence before you write anything else. Not as a formatting rule — as a test of whether you’ve finished thinking. If you can’t write it, you don’t have one yet. The struggle to produce that sentence is often how you find out the thinking isn’t done. The sentence isn’t evidence of clarity. It’s how you discover whether you have any.

There are situations where information delivery is the right job. Status updates, audit trails, research archives: the reader needs the data, not a conclusion. The error is applying this standard to the wrong genre. Any time someone is waiting to decide — a recommendation email, a design review, an analytical brief — they’re not waiting for more context. They’re waiting for someone to have processed it.

The goal is never to have communicated. The goal is for the reader to know what to do.