What Career Professionals Can Learn from The Elements of Style
Ben had rewritten the same email to a client four times before lunch. The original draft said: "I wanted to reach out to touch base regarding the fact that there may potentially be some delays that could impact the timeline going forward." He read it back and felt his stomach tighten, because he knew exactly what it was doing: hiding a two-week delay behind eleven words of hedging so the bad news would feel smaller to write, even though it wouldn't feel smaller to receive. He'd learned to write this way in his first job, copying the cautious tone of every email he saw in his inbox, and it had become so automatic he barely noticed it anymore. He deleted the sentence and typed, "The project will be two weeks late because of a vendor delay," then sat with how much shorter, and how much more honest, it looked on the screen.
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
Omit needless words
Ben's original email used eleven words — "regarding the fact that there may potentially be" — to introduce four words of actual news. Professionals learn this pattern from example, absorbing office-speak because it's everywhere, until the padding becomes invisible to the person writing it.
Before sending, scan for stock phrases like "touch base regarding," "at this point in time," and "there may potentially be," and replace each with the direct statement it's standing in for. A useful test: if you'd say the sentence differently out loud to a colleague's face, rewrite it to match.
Prefer the active voice and concrete language
"The deadline was missed" and "budget decisions were made without consulting the team" both remove the person responsible from the sentence, which reads as evasive even when that's not the intent. Status updates full of passive constructions leave readers unsure what actually happened or who to ask.
Name who did what — "the vendor missed the delivery date" or "finance cut the marketing budget without a heads-up" — even when the actor is your own team or yourself. A concrete sentence about what happened is also easier for a reader to act on than a vague description of a situation.
Keep related words together and use consistent structure
A status update lists three unrelated updates in one run-on paragraph, so the reader has to untangle which sentence belongs to which project. A request buried at the end of a long email gets missed because it wasn't given its own line or its own weight.
One idea per paragraph, with the most important point — the ask, the deadline, the decision needed — in the first sentence, not the last. When listing updates across multiple projects, use the same structure for each so a reader can scan rather than read line by line.
Habits, not laws
None of this means every email needs to be terse to the point of sounding cold; warmth and context still matter, especially with people you work with regularly. These habits are meant to become quick enough to use in a five-minute reply, not just a carefully drafted proposal, so clarity survives the volume of daily correspondence. A professional who has built the habit can still write a longer, warmer message on purpose when the relationship calls for it.
Directness and diplomacy can seem to pull against each other at work, since naming exactly who missed a deadline can feel riskier than describing it vaguely. The habits here aren't an argument for bluntness at the cost of tact — they're an argument for making the facts clear first, then choosing your tone deliberately, rather than letting vagueness do the work that tact should be doing instead.
Name one thing, honestly
Pull up the last email you sent delivering unwelcome news — how many words came before the actual news, and what were those words actually protecting?
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
One idea per paragraph, with the most important point — the ask, the deadline, the decision needed — in the first sentence, not the last. When listing updates across multiple projects, use the same structure for each so a reader can scan rather than read line by line.