Part IV — Professional and Workplace Writing

This is the writing you'll do most. For every paper or report you publish, you'll send hundreds of emails, file dozens of status updates, and write the occasional proposal that decides a budget. The volume alone makes workplace writing the highest-compounding skill in the book — small improvements, repeated daily, add up faster than mastery of any single prestige genre. And the reader here is the most time-poor you'll ever write for: a manager scanning between meetings, an executive who reads the first line and stops, a colleague who needs to do something with your words and has no patience for the route you took to them.

That reader forces the central shift of this part. Workplace documents aren't records of what you know or displays of effort; they're inputs to decisions and tools for getting action. The novice writes to discharge their knowledge — the info-dump. The professional asks "what do I need this person to do, and what's the least I can give them so they'll do it?" — then leads with the ask and prunes the rest. You report the exception, not the routine; the owner and the deadline, not the discussion; the outcome, not the activity. Every chapter here is that one move, worn in a different genre's clothing.

By the end of Part IV you will be able to write an email that wins triage and gets a yes; build a proposal or business case an executive can approve from the summary alone; file progress, status, and incident reports that sort information by what the reader must act on; write instructions a beginner can follow without you in the room; and coordinate a multi-author document so it reads as though one person wrote it.

What's in this part:

  • Chapter 19 — Emails That Get Read and Get Results: the four-part anatomy, choosing the channel, and the structural fixes for the three hard emails — the request, the bad news, and the "no."
  • Chapter 20 — Proposals and Business Cases: problem → solution → ROI, the three persuasive structures, and why the executive summary is the document, not a preview of it.
  • Chapter 21 — Workplace Reports: Progress, Status, Incident — six genres, BLUF, honest RAG status, and the blameless incident report that fixes the system, not the person.
  • Chapter 22 — Instructions and Procedures: numbered steps for a reader who's doing not reading, warnings placed before the step they govern, and the "someone who has never done this" test.
  • Chapter 23 — Collaborative Writing: Writing With a Team — naming one document owner, the integration pass that kills the Frankenstein document, and reconciling conflicting feedback by judgment.

These five chapters are mutually independent — read whichever your week demands. They build on Part I's audience and structure work and on Part II's revision discipline, but not on each other. The Business/Professional track lives here; the Software/CS track will recognize Chapter 22's testing discipline returning in the next part's developer docs, and Chapter 21's blameless framing seeding the postmortem in Part VII.

The dominant theme is structure serves the reader — exception-based reporting, BLUF, the ask-first email, all answering "how does the reader use this?" Close behind is audience is everything: the same status item changes shape for a manager, an executive, and a client, and the three hard emails are hard because of who's on the other end. Every sentence must earn its place drives the compression these readers demand — the 500-word update becomes a 100-word dashboard. Revision is where the writing happens surfaces in Chapter 22, where a procedure becomes good only by being tested on a real beginner and fixed, and in Chapter 23, where integration — not drafting — is the half teams skip.

The Communication Portfolio gains several pieces here: Chapter 19 builds the professional email chain (the difficult-scenario one), Chapter 20 shapes the proposal, and Chapter 22 produces the user documentation. By the end of this part, most of your seven pieces have a first draft.

Part V narrows to the documents of software and data — code comments, READMEs, API docs, data memos, and the writing you do with and about AI — where these same workplace instincts meet the developer at the front door.

Chapters in This Part