Monday, in the team channel: “no clue yet if the fix holds, we’re testing three things.” Wednesday, in the weekly update: “fix in progress, early signals promising.” Friday, in the exec deck: “on track.”

Nobody lied. Something quieter happened.

James March and Herbert Simon named it in 1958: uncertainty absorption. As information travels, people pass along their conclusions, not the evidence behind them. Every handoff is a summary, and summarizing means deciding what the next reader doesn’t need. Doubt is expensive to explain, so doubt goes first.

The engineer who wrote Monday’s message knows exactly how provisional it is. The executive reading “on track” can’t; the qualifiers are gone. Clean sentences invite commitments: a date gets promised, a dependency planned, and every commitment raises the price of reopening the doubt. “We’re no longer sure” becomes harder to say just as it grows more important. People learn, too: updates with caveats come back with questions, smooth ones sail through. So the trimming starts earlier, until teams absorb their own uncertainty before it leaves the room.

I hear the same piece of work described at every altitude of an organization, and the doubt usually dies in transit: an hour of argument on the team, a cautious clause in the update, gone by the deck.

This week, keep one doubt alive on purpose. One sentence in your update: “What we’re least sure of is X, and here’s when we’ll know.” And when you’re the reader, pick the smoothest line and ask what it compressed.

Which line in your last update was cleaner than what you knew?