Writing Without Bullshit Summary: Make Work Writing Clear

Key Ideas

1. Treat the reader’s effort as a design constraint

The Iron Imperative is Bernoff’s central principle. Its practical force comes from asking who pays for an unfinished thought. When a writer leaves the purpose unstated, the reader must infer it. When a message mixes facts, proposals and speculation, the reader must sort them. Saving a few minutes before sending can create avoidable work for several other people afterward.

In our original case, the procurement manager drafts a memo beginning with a history of conversations with the supplier. The assembly lead reading it needs to know first whether next week’s work is affected. The finance lead needs to know whether additional spending is requested. Respecting those readers does not require hiding the history; it requires putting it in a place that supports their task instead of making it an entrance examination.

Write a private description of the reader’s job before editing. Here the immediate job is to evaluate whether to authorize a limited alternative purchase while the delayed shipment remains uncertain. That description tells the writer which information needs a prominent place: the component, timing, production effect, spending request and remaining unknowns. It also identifies material that can move to a linked record.

For a practical check, hand the draft to a colleague who is unfamiliar with the incident and ask what work they think the memo is asking them to do. Do not supply the answer first. A mismatch is a reason to revise the document’s purpose or presentation. The principle is not that readers deserve no effort at all; it is that the writer should remove effort that serves no useful understanding or decision.

2. Put the point early without flattening the facts

Front-loading is a named part of Bernoff’s book. In his later explanation, he argues that an early point does not prevent a writer from providing the story and support afterward. The value is orientation. A reader can understand why the details matter instead of waiting until the last paragraph to discover the document’s purpose.

Our procurement memo begins with the subject Supplier update. It then describes three calls before asking for approval to buy a small quantity elsewhere. A revised subject could identify the decision and timing: approval requested by Wednesday for an alternative component order. The opening can explain that the current supplier has missed the confirmed dispatch date and that assembly coverage is at risk. These are invented example facts, not a template to use without checking your own situation.

Follow the opening with evidence, options and limitations. A direct first sentence must not promise more certainty than the body supports. If the revised arrival date is an estimate, label it as one. If the alternative component requires a compatibility check, make that condition clear before the reader approves the order. Early placement of the recommendation creates an obligation to explain it honestly, rather than an excuse to hide awkward detail.

Test the opening independently: can the intended reader state the main point and the requested action after reading it? Then test the full document: can they see enough support to judge that request? These tests address different failures. A forceful subject line cannot compensate for missing evidence, and a complete appendix cannot compensate for a first page that never reveals what the reader is being asked to decide.

3. Reveal people, actions and uncertainty in the language

Bernoff’s contents give attention to passive voice, jargon, vague modifiers and directness. His discussion of exceptions is useful: examine a construction rather than banning it without thought. The practical question is whether wording helps the intended reader understand the work or gives the writer somewhere to hide.

In our memo, arrangements are being progressed leaves both the action and the responsible person unclear. A concrete version says that procurement is checking the alternative component with engineering and expects an answer on Tuesday. That statement allows another person to understand the dependency. It also makes a commitment visible, so it must be checked before publication. Editing cannot responsibly invent an owner or deadline merely to make the sentence active.

Apply the same care to an expression such as a significant impact is likely. What impact, on which work, under what condition? Our fictional manager can explain that assembly may pause after the remaining stock is used, while the exact duration depends on the revised delivery. The clearer version still contains uncertainty. It places uncertainty where it belongs instead of distributing it through vague words that leave every claim equally cloudy.

On a language pass, underline sentences where you cannot identify an actor, action or necessary condition. Resolve the missing facts with their owners, then rewrite. Keep a technical term if the actual readers need its precise meaning, and explain it when they do not share that vocabulary. Candor is compatible with tact: describe the missed commitment and consequence without turning the memo into an unsupported judgment about the supplier’s motives.

4. Make structure and numbers answer the reader’s question

Bernoff includes using numbers wisely and revealing structure among the book’s writing topics. In this guide’s application, treat those concerns together: readers need to know what a figure measures and where it fits in the argument. A precise-looking number can remain useless if its period, scope or role is unclear. Headings can help expose those relationships.

Our procurement manager has a quoted unit price for the alternative component. Reporting only that price would conceal the decision’s full shape. The memo should state the proposed quantity, relevant delivery charge and whether testing or assembly work adds another cost. If a figure is provisional, mark it. If two options use different quantities or dates, explain that difference before comparing their totals. These are original application checks, not a calculation method attributed to Bernoff.

Use headings that distinguish the decision, verified situation, options, costs and conditions. A reader can then scan for the material relevant to their responsibility. Under the decision heading, state the authorization sought. Under conditions, identify what must be confirmed before ordering. Avoid scattering a consequential limitation across several unrelated paragraphs where it can be missed during approval.

Finally ask a colleague to explain one important number back to you: what does it include, what does it exclude and what would change it? If the answers differ from your assumptions, revise the labels or explanation. Readability here is more than shorter sentences. It includes helping another person interpret evidence well enough to make a decision, and leaving a record that can still be understood after the immediate conversation has passed.

5. Collaborate on the argument before polishing the wording

The book addresses planning, collaboration and editing as part of clear business writing. Bernoff’s separate article on a fat outline describes a planning document containing enough substance for collaborators to evaluate the intended content. This author-written article clarifies a useful practice; our sequence below is an editorial application rather than a claim that the book prescribes exactly these review stages.

For the supplier memo, a bare outline saying Background, Options and Recommendation gives engineering and finance little to examine. A fuller outline includes the actual claim under each heading, the facts needed to support it and the unresolved question. Engineering can then correct a compatibility assumption before the writer spends time making a paragraph elegant. Finance can identify a missing cost before approving language that implies a complete total.

Ask reviewers to distinguish factual corrections, argument changes and wording suggestions. Resolve the first two before debating a synonym. If one reviewer believes the memo is a request and another thinks it is an announcement, settle that difference directly. Combining both reviewers’ preferred sentences will not produce an honest document until the purpose is clear.

Keep one accountable owner for the final version and check it after revisions. A late edit can silently turn an estimate into a commitment or remove the condition that made approval reasonable. The practical aim is a document whose contributors agree on what it means, not a document containing a trace of every comment. Thoughtful collaboration can prevent evasive prose from forming, instead of leaving the writer to repair it after the political decisions have already been embedded in the sentences.