Clear writing is not elegant writing. It is writing that lets a busy person understand the point, decide, and act without calling you. Stop trying to sound professional. Corporate fog is not authority; it is work pushed onto the reader. This guide shows the edits I use on emails, proposals, and technical documents when the first draft is not doing its job.
🎙️ Published & recorded: ·
Before writing, finish two sentences: “The reader is…” and “After reading, they should…” If the second answer is “be informed,” you have not made a choice. Do they need to approve, fix, compare, prepare, or remember? One document can serve several readers, but one paragraph cannot serve five purposes at once.
Weak brief
Audience: stakeholders
Goal: provide an update
Usable brief
Reader: Maya, who owns the launch decision
Action: approve the two-day delay by 3 p.m. Thursday
Evidence she needs: failed load test, repair estimate, customer impactA project lead sent, “Just sharing the latest deck for visibility.” Nobody replied. On Friday he asked why legal had not approved it. The request had never appeared. Fix it in three passes. Name legal as the reader. Put “Approve slide 12” in the first line. Add the deadline and what happens after approval. Do not blame readers for failing to discover a hidden task.
At work, suspense is usually rude. State the answer, then give the reason, then the detail. A manager should not read six paragraphs to learn whether the launch is on time. Background-first writing feels safe because it delays commitment. Delete that runway.
Before
Over the past several weeks, the team has been evaluating a number
of vendors while also considering our changing operational needs.
Following those discussions, we wanted to share an update.
After
Choose Northstar. It is the only vendor that meets our June deadline
and audit requirement. It costs $8,000 more per year.
Decision needed: approve Northstar by Tuesday at noon.
Evidence: comparison table below.Use the first sentence as a test. If the reader sees only that sentence on a phone notification, will they know the point? “Quick update” is not a point. “The migration is delayed two days” is.
Replace vague praise, concern, and scale with observable facts. “Significant,” “soon,” “optimize,” and “several” force the reader to guess. Numbers are useful only when they answer the reader's question. “Conversion improved 4.2 percent” is still incomplete if the reader needs to know the dates and baseline.
Vague Concrete
We had several incidents. Checkout failed 17 times on Monday.
Please respond soon. Reply by 2 p.m. Friday.
The page is much faster. Median load time fell from 3.1s to 1.4s.
We should optimize onboarding. Remove the card step from trial signup.
A large group dislikes it. 8 of 12 interviewees could not find Save.If you do not know the number, say what you observed and how limited the evidence is. Write, “Three support calls this week mentioned duplicate invoices.” Do not upgrade that into, “Customers are broadly dissatisfied.” Clear writing exposes weak evidence instead of decorating it.
Short is not automatically clear. A row of tiny sentences can sound childish. The useful rule is one main claim per sentence, with enough detail to understand it. When a sentence contains three “and” clauses, a parenthesis, and a late exception, split it. Put the exception beside the claim it changes.
Before: 54 words
We reviewed the rollout plan and, given the staffing constraints that
were discussed last week and the fact that the mobile build remains
in review, which may be resolved by Wednesday, we believe it would be
appropriate to move the launch, although the web release could still
proceed if leadership prefers.
After
Move the full launch from Tuesday to Thursday. The mobile build is
still in review, and support has two people out. We can release the
web version on Tuesday, but I recommend one coordinated launch.Read the draft aloud. If you need to restart a sentence, the reader probably will too. Keep the wording if it is long but easy to follow. Cut it if grammar is hiding the decision.
A useful paragraph has a point, proof, and consequence. Put the claim first. Keep evidence with that claim. End with why it matters or what happens next. Start a new paragraph when the job changes. A wall of text is often not a formatting problem; it is four thoughts that were never separated.
Claim The new search is not ready for public traffic.
Evidence It times out on 6% of queries above 20,000 records.
Consequence Keep the beta flag on while we add the missing index.
Next claim The fix is small and testable.
Evidence It passed on a production-sized copy this morning.
Consequence Re-run the load test at 4 p.m.; release if errors stay below 0.1%.Headings should reveal the argument. “Recommendation: delay by two days” beats “Next steps.” A reader scanning headings should recover the shape of the document without reading every line.
Business writing turns verbs into heavy nouns: make an assessment, conduct a review, provide an explanation. Put the action back in the verb. Use passive voice when the actor is unknown or irrelevant. Reject it when it hides responsibility. “Mistakes were made” is not neutral; it removes the person who can fix them.
Corporate fog Direct version
We conducted an evaluation of X. We evaluated X.
Implementation will be undertaken. Priya will implement it Monday.
A decision was made to postpone. I postponed the release.
There was a failure in delivery. The courier lost the package.
We are in alignment on the need to… We agree to…An incident note said, “The production database was inadvertently modified.” Leaders spent an hour asking who did what. Rewrite it in order. Name the actor: “Our migration job modified production.” Name the exact action: “It dropped the customer-status index.” Name the effect and repair: “Queries slowed for 11 minutes; Ana restored the index at 10:42.” Accountability makes the note useful.
The subject line is a routing label. Put the action and date there. In the body, state the request in the first two lines, give only the context needed to answer, and define the response format. “Thoughts?” is lazy when you need approval.
Subject: Follow-up
Hi all, circling back on the below. Any thoughts would be appreciated.
It would be great if we could get this finalized ASAP.
Subject: Approve homepage copy by Thu 2 p.m.
Mina, please reply “approved” or mark changes in the doc by Thursday
at 2 p.m. We send the page to translation at 3 p.m.
Review only the headline and first paragraph:
https://example.com/doc
If I do not hear back, I will keep the current copy and move translation.A London editor wrote, “Please send final copy by end of day.” The San Francisco writer delivered eight hours after the editor logged off, and the print slot was lost. Repair the request with a date, time, and timezone: “Send final copy by 5 p.m. BST on 14 May.” Then state the consequence: “After that, the issue ships without this article.”
Technical writing should let a tired reader recover. Start with the outcome and prerequisites. Use exact commands. Show the expected result. Include the real error text because that is what people search. Put explanation after the fix, not before it.
Goal
Run the app locally on port 3000. Requires Node 22 and npm 10.
Steps
1. npm ci
2. copy .env.example .env
3. npm run dev
4. Open http://localhost:3000/health
Expected result
HTTP 200
{"status":"ok"}
Real failure
Error: listen EADDRINUSE: address already in use :::3000
Fix
1. Windows: netstat -ano | findstr :3000
2. macOS/Linux: lsof -i :3000
3. Stop the stale process, or run PORT=3001 npm run dev.
4. Open the health URL again on the chosen port.Never write “simply configure the environment.” Name the file, setting, accepted value, and restart step. “It should work” is not an expected result. Give the status code, visible text, or output that proves success.
Draft for truth. Edit for the reader. Trying to perfect every sentence while discovering the argument makes both slower. Use five passes. First, verify the conclusion. Second, move it to the top. Third, cut anything the reader does not need. Fourth, replace vague nouns with actors, verbs, dates, and quantities. Fifth, read aloud and test every request.
PASS 1 Point: can I state the conclusion in one sentence?
PASS 2 Order: answer → reasons → evidence → action
PASS 3 Cut: throat-clearing, repetition, history nobody needs
PASS 4 Specify: who, does what, by when, measured how
PASS 5 Test: read aloud; open every link; follow every instruction
Search and challenge:
very · really · significant · leverage · facilitate · in order to
it was decided · going forward · at this point in time · thoughts?Cutting is not making prose cold. Keep courtesy, context, and human judgment. Remove ceremony that pretends to be courtesy. “Could you possibly take a look when you have a chance?” is less kind than a clear request with a realistic deadline.
Use this before sending anything that asks another person to spend time, make a decision, or take a risk.
BEFORE DRAFTING
□ Name one primary reader.
□ Name the action or decision.
□ List the minimum evidence they need.
WHILE EDITING
□ Put the answer in the first sentence.
□ Give each paragraph one claim.
□ Replace vague scale with observed facts.
□ Turn noun phrases back into verbs.
□ Name the actor when responsibility matters.
□ Split sentences with competing jobs.
FOR REQUESTS
□ Action + date in the subject line.
□ Owner, deadline, timezone, response format.
□ State what happens if nobody responds.
FOR INSTRUCTIONS
□ Prerequisites, exact steps, expected result.
□ Real error text and a tested recovery.
FINAL TEST
Could the reader act correctly without asking me what I meant?My rule is blunt: sounding professional is not a writing goal. A clear “No, because the load test failed” is more professional than three polished paragraphs that conceal the answer. Respect the reader enough to choose, specify, and stop.