Writing for Work: Emails, Reports, and Messages
Write for busy readers: lead with the bottom line, structure for skimming, and use plain language in emails, reports, and messages.
Communication & Argumentation · Lesson 2
Write for busy readers: lead with the bottom line, structure for skimming, and use plain language in emails, reports, and messages.
Most writing you do is practical: emails, reports, updates, requests. The reader is busy, distracted, and skimming. Work writing that buries its point, rambles, or hides behind jargon wastes everyone's time and often fails to get what it asks for. A few principles make your professional writing dramatically more effective.
The single most useful habit in work writing is BLUF — bottom line up front. State your main point, request, or conclusion first, then supply the detail. Busy readers should grasp what you need and why in the first sentence, not the last paragraph. This is the opposite of building suspense — and exactly right for practical writing.
Readers scan before they read. Make your writing skimmable: short paragraphs, clear headings, bullet points for lists, and one idea per paragraph. A wall of text hides its own content. Structure is a courtesy that also gets you better results.
Professional does not mean pompous. Plain language — everyday words, direct sentences — communicates better than inflated 'business-speak.' And every work message should have a clear purpose: know exactly what you want the reader to understand or do, and make it obvious.
Weak email: three paragraphs of context, with the actual request ('can you approve the budget by Friday?') buried at the end. Strong email: 'I need your approval on the attached budget by Friday. Context below.' The reader knows the ask immediately and can act. Same information, reordered to respect the reader's time — and far more likely to get a yes.
BLUF is not universal. Sensitive messages — bad news, delicate feedback, persuasion of a resistant reader — sometimes need context or empathy before the point, or the blunt lead lands as harsh. And some genres (narrative, marketing) build deliberately. Match the structure to the situation: lead with the point for most practical writing, but read the human context.
Governments and militaries — famous sources of impenetrable prose — have led formal efforts to write more plainly. The 'bottom line up front' principle is widely used in the United States military precisely because officers need to convey the essential point immediately. More broadly, the plain-language movement culminated in the United States in the Plain Writing Act of 2010, a federal law requiring agencies to write public documents in 'clear, concise, well-organized' language that citizens can understand. Guidance published for it (on plainlanguage.gov) urges familiar words, active voice, short sentences, and logical structure — the same principles this lesson teaches. That an entire government legislated clarity underscores the point: plain, well-structured writing is not dumbing down; it is a practical necessity that saves time, reduces errors, and respects the reader. If it works for laws and military orders, it will work for your emails.
Take a work email you'd send. Move the main request or point to the very first sentence, and cut the throat-clearing before it. Does it read as clearer and more actionable?
Think Like a Maester: Respect a busy reader by leading with the point — say what you need first, then explain.
Work writing serves busy, skimming readers, so lead with the bottom line up front (BLUF), structure for skimming with short paragraphs and headings, and use plain language over jargon. Know each message's purpose and make it obvious. The military's use of BLUF and the US Plain Writing Act of 2010 show that even governments and armies legislate clarity — because plain, well-structured writing saves time, reduces errors, and gets results. Match structure to context, leading with the point for most practical writing.
Mark this lesson complete to track your progress.