In the original article, the author proposes three rules of “correct” communication: BLUF, “just in time” context, and “top-down bridge.” On paper, it sounds nice, but as soon as you step beyond simple tasks and small teams, these tips start to stall.
​
☝️ BLUF: “Bottom line up front” — not always a blessing

The idea of BLUF is simple: start with the main conclusion, then give details later. In military settings and short status updates, it really works — when everyone’s context is roughly the same and the cost of delaying a decision is high.

But in real-life communication, there’s a nuance: the interlocutor already has their own internal context, hypotheses, and expectations. If you throw out a conclusion in the first sentence that conflicts with their worldview, you get not “efficiency” but instant cognitive dissonance and a defensive reaction. The person doesn’t listen to arguments; they internally argue with your first sentence.

Let’s figure out how an explanation should be structured. First, context is built through questions and clarifying assumptions, then a conclusion is formed. This is exactly what the Socratic method does: through questions, it draws out initial assumptions, helping the person arrive at a new thought themselves, rather than just “swallowing” someone else’s thesis. As a result, understanding is deeper and more stable than from a “blunt conclusion.” Good school teachers use the same approach; we’ve just forgotten about it.

BLUF is good as one mode, but as the “only correct way,” it becomes a source of misunderstanding, especially where you need not just to convey a decision but to change the interlocutor’s mental model.

☝️ “Just in time context”: depth is not ballast

The second thesis of the article is “give as much context as needed to solve the current problem, and don’t burden people with your depth of knowledge.” The logic is clear: cognitive load is limited, and it’s hard for people to digest extra information. But from this, too radical a conclusion is drawn — that depth gets in the way.

In large organizations, conflicts more often arise not from “excess context” but precisely from different depths of understanding among participants. One thinks at the architecture level, another at the ticket level, a third at the business metrics level. Everyone seems to speak the same language, but behind the words are different models, and hence constant “we misunderstood you.”

If in such a situation you cut context “for the task right now,” you save 10 minutes today and lose hours/days tomorrow — on sorting out the consequences of decisions made from different worldviews.

Normal time management in communication is not “cutting depth” but allocating time to convey the chain of reasoning: from initial assumptions to the decision. Yes, it’s more time-consuming upfront, but it’s an investment: then the person is already in context, understands your logic, and can make aligned decisions on their own without constant “jump on a call.”

☝️ Top-down bridge: steps are correct, but half the bridge is unfinished

The third thesis is “build a bridge from top to bottom”: start from what the person already knows and gradually go deeper. It’s hard to argue with this: if the gap in depth is huge, trying to drag the person through your entire mental model in one conversation is doomed. It’s better to break it down: first high-level, then detail as needed.
​
But there’s a catch here. If you limit yourself only to the top level and don’t lay out a plan to eliminate gaps in understanding, you’ll get stuck in an eternal mode of “I give you a thesis, you give me superficial agreement.” At some point, you’ll inevitably run into conflicts from point 2.

That is, the “top-down bridge” only works in combination:

we start at the top level — so the interlocutor doesn’t drown in details;

but we consciously plan: where and when we’ll go through the chain of logic deeper to align the mental model.

And here the circle closes: without eliminating gaps in depth, it’s hard to make an honest BLUF (point 1) that doesn’t cause rejection.