Key Takeaways — Chapter 21: Workplace Reports
The summary card. Use it to re-ground before the quiz, or to review weeks later.
The one idea
A workplace report is an input to a decision, not a display of effort. The reader is busy and must do something with what you wrote—approve, escalate, reassign, decide, or stop worrying about something on track. So you sort the information by what the reader has to act on: lead with the headline, surface the exceptions, compress the routine to nothing, and attach an owner and a date to every action.
🚪 Threshold concept: Before you cross it, a report feels like an account of what you did—naturally told in the order it happened, with the most words on the things you spent the most time on. After, you write for a reader who's deciding: you report the exception, not the routine; the owner and the deadline, not the discussion; the outcome, not the activity. The chronology of your week is the writer's order; the structure of the reader's decisions is the right one.
The six genres at a glance
| Report | Answers | Built on | The one rule |
|---|---|---|---|
| Progress report | "How's your work going?" | Planned / Done / Next / Blocking | Outcomes, not activities |
| Status update | "Across everything, what needs attention?" | RAG + exception-based detail | Report the exception |
| Incident report | "What went wrong, and how do we prevent it?" | Summary / Timeline / Root cause / Impact / Corrective actions | Blameless; owners + dates |
| Meeting minutes | "What did we decide and who owns what?" | Decisions / Actions / Owners / Deadlines | Outcomes, not a transcript |
| Trip report | "Was the trip worth it; what did we learn?" | Takeaways / Recommendations | Value, not travelogue |
| Feasibility study | "Should we do this, and can we?" | Options × criteria → recommendation | Compare alternatives incl. "do nothing" |
The disciplines that cut across all of them
- BLUF the headline. On track or off? Incident occurred? Decision needed? The reader who reads only the first line should still get the one fact that matters. (Chapter 4.)
- Exception-based reporting. Spend words where there's a deviation; reduce on-track items to a single line. You allocate the reader's attention by their need to act—usually toward what went wrong, not what you spent the most time on.
- RAG honestly. Green = on track, no help; amber = at risk, recoverable; red = needs a decision/resources now. Decide the thresholds in advance. Never the watermelon (all-green until it explodes)—that destroys the report's early-warning value.
- Outcomes, not activities. "Shipped the redesign," not "worked on the redesign." A reader can't act on motion.
- Owners + dates make actions real. An action without one named owner and a real date is a wish. Put corrective actions and action items in a table; the table format is the accountability.
- Blameless = system, not person. "The pipeline allowed an unreviewed config to ship," not "X was careless." It's not politeness—it's the only framing that produces fixes that prevent recurrence (the seed of Chapter 34's postmortem).
- Facts apart from interpretation. In an incident report, the neutral timeline (what happened) stays separate from the root cause (why)—the Results-vs-Discussion discipline of Chapter 13, so your facts stay trustworthy even when your analysis is debated.
The test to apply before you send anything
Hand it to someone who knows nothing about your project. Ask: "What's the one thing that needs attention, and what would you do about it?" If they can't answer in under a minute, your exception is buried or your routine is too loud.
If they can't, you wrote it bottom-up—in the order your week happened, not the order your reader needs. Re-sort it: headline up top, exceptions next with owners and dates, routine compressed to a line.
Themes this chapter surfaced: #5 structure-serves-the-reader (central—exception-based reporting and BLUF both answer "how does the reader use this?") · #6 every-sentence-earns-its-place (compress the routine; the 500-word update becomes a 100-word dashboard) · #2 audience-is-everything (the same status item changes shape for a manager, an executive, and a client).
Threshold concept: Report the exception, not the routine; the owner and the deadline, not the discussion.
Back to: Chapter 21 · Exercises · Quiz · Further Reading