What Career Professionals Can Learn from On Writing
Tomas had just finished a status report for his director, four dense paragraphs explaining a project delay in the passive voice: "Timelines were impacted due to unforeseen dependencies that emerged during the integration phase." He read it back and realized it said nothing about who was responsible or what would happen next. His director would have to ask three follow-up questions just to understand the situation. He rewrote it in two sentences: "We're two weeks behind because the vendor's API changed. I'm meeting them Thursday to get a new date." It felt exposed, naming the delay so directly. It also meant, for once, nobody would need to ask him what actually happened.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Strip your reports and emails down to honest, plain language
A professional writing a status update reaches for passive constructions and vague phrases — "issues were identified," "efforts are ongoing" — that avoid naming who did what and what happens next. The reader has to chase down the person who wrote it just to get the information the document was supposed to provide.
Rewrite your next status update using active voice and naming a specific owner and next step for every open item. If a sentence doesn't tell the reader who is doing what by when, cut it or fix it before sending.
Protect a consistent block of time for the writing that actually matters
A professional writes documentation and reports only in the last twenty minutes before a deadline, squeezed between meetings, which produces work that's technically complete but unclear, forcing colleagues to ask follow-up questions that a clearer first draft would have prevented.
Block a fixed 30 to 60 minute slot at the same time each week — first thing Monday, say — dedicated only to writing documentation, reports, or updates before they're urgent. Treat that block with the same protection you'd give a client meeting.
Read workplace writing deliberately, as ongoing education
A professional reads dozens of emails and documents a week purely for content, never noticing which messages get fast, clear responses and which generate confused follow-up threads, so the same unclear habits persist unexamined for years.
Once a week, notice one email or document that got an unusually fast, correct response and one that generated confusion. Identify the specific difference in how they were written, and apply what you find to your own next piece of writing.
Your work history is material, but craft decides if it lands
The project that failed, the year you were in over your head, the mistake that taught you something real — these are legitimate material for interviews, performance conversations, and your own professional story. But that material only helps you when it's told with specific, honest detail and disciplined editing, not buried in vague corporate language that protects you from sounding responsible for anything.
Protected writing time and plain, direct language both take more effort than dashing off a vague update between meetings, and reading workplace writing critically takes time you may feel you don't have. Don't let deadline pressure push you toward vagueness as a shortcut. A rushed message can still name the owner and the next step; save the deeper critical reading for your protected block, not the crisis moment, and treat the two habits as reinforcing each other rather than competing for the same ten minutes.
Name one thing, honestly
Which recent report or email of yours would have been clearer if you'd named who was responsible for each open item?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Once a week, notice one email or document that got an unusually fast, correct response and one that generated confusion. Identify the specific difference in how they were written, and apply what you find to your own next piece of writing.