Communicating and leading, one lesson a day

Imagine you manage a greenhouse that supplies young plants to farms across the county. A fungus has appeared in one propagation room, and you are about to spend the morning inside another room where phones are not allowed. While you are sealed behind the sanitation doors, the shipping crew still has to decide which trays can leave, which orders need new dates, and whether the delivery van should wait. Everything you write before you go in has to work without you.

That is the right moment for bottom line up front. The military shortens it to BLUF, a format required in Army correspondence, where the standard is that a reader should understand a message in a single rapid reading. The same idea appears in Barbara Minto's Pyramid Principle, developed through her work teaching consultants to write. Start with the answer. Put the reasons below it. Put the evidence under the reasons. The point sits at the top of the pyramid and the details descend from it.

This order feels unnatural because it is not the order in which you discovered the answer. You noticed yellow leaves, checked the irrigation, inspected the roots, compared two benches, and only then concluded that one room should be isolated. When you write in that order, you make the shipping crew repeat your investigation before they learn what to do. They do not need to solve the mystery with you. They need the destination first, followed by enough of the route to trust it.

The philosopher Paul Grice helps explain why this works. Conversation depends on cooperation. Readers assume that every detail you include matters, so until they know your point, they must keep each detail suspended in memory and guess what it is for. That takes effort. Under pressure, people skim, and the very facts you carefully included get lost. Put the conclusion first and every later sentence has a place. The mental load drops because the reader knows what question the details are answering.

Make it concrete. The weak note begins, "We saw some discoloration during the morning check, and after looking at moisture levels..." The useful note begins, "Hold all trays from propagation room three until noon; the other shipments leave as planned." Now the driver can act even if that is the only line they see. Under it, give the supports: the problem is limited to one room, the plant pathologist will confirm the cause by eleven, and affected customers will get revised dates after that call.

Use the same test on every message. If the reader sees only the first sentence, do they know the most important thing? If the message asks for action, put the action first. If it reports a state, put the state first. If it requests a decision, name the decision and its deadline first. History, reasoning, and caveats belong below for the people who need them.

People often hide the main point for emotional reasons while telling themselves they are only supplying context. Bad news feels easier to deliver after a runway of careful explanation. You may want to describe every inspection before saying that several orders will be late. The runway does not soften the landing. The reader senses that something is coming, hunts for it, and becomes frustrated with both the delay and the news. Assertive writing says the uncomfortable thing plainly. Respect comes from clarity, not from making someone excavate your meaning.

The subject line or opening sentence should be the message in miniature. "Decision by ten: destroy or quarantine the north bench" can be understood while someone is unloading compost. "A few thoughts after this morning's walkthrough" cannot. A reader should be able to triage your note from the notification alone, then open it for the reasons.

Point-first does not mean context-free. A bare order can create a second round of questions and force everyone to reconstruct your reasoning. The useful shape is answer, because, unless. Answer: hold one room's trays. Because: the symptoms are contained but still unidentified. Unless: the pathologist clears them before noon. Most everyday messages need no more than five sentences, but they do need all three parts when a caveat could change the action.

Try this before your next busy stretch. Take one update you were about to send and do not rewrite it. Move the sentence containing the answer, request, or decision to the top. Read only that line and ask whether someone could take the correct first step while you were unreachable. Later, write your next message with the ask or answer first and notice how much of the explanation becomes unnecessary.

Point first. Details descending. Write it so the work can continue without you.