What Everyday Life Can Learn from The Elements of Style
Deshawn was typing a text to the group chat trying to plan his sister's birthday dinner, already on his third draft: "Hey everyone, just wanted to see if maybe people might be free at some point this weekend for possibly getting together to celebrate, no pressure either way, whatever works!" Nobody had answered in two hours. He reread it and saw why — no actual question in it, no date, no time, no place, just a fog of politeness giving nobody anything to say yes or no to. He deleted it and typed instead: "Dinner for my sister's birthday, Saturday 7pm at Luna's. Can you make it?" Three replies came back within ten minutes. He sat there a little annoyed at himself, because he did this constantly — in texts, in emails to his landlord, in notes to neighbors — burying the actual point under cushioning that people couldn't find to respond to.
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
Deshawn's group text used a dozen words — "just wanted to see if maybe people might be free at some point" — to avoid asking one direct question. This padding often comes from a fear of sounding demanding, so the request gets wrapped in enough softness that it stops looking like a request at all.
Write the plain version first — the date, the time, the place, the question — and only afterward decide if it needs a friendly line added around it. A text that states the plan and asks one clear question usually gets more replies than one trying to sound relaxed about everything.
Prefer the active voice and concrete language
"It would be great if this could get sorted out at some point" to a landlord about a broken heater says nothing about who should fix what or by when, and the landlord has no clear action to take. Vague language in everyday requests often comes from not wanting to sound pushy, but it usually just produces a slower, less useful response.
State the specific problem and the specific ask — "the heater in unit 4B stopped working Tuesday; can someone come look at it this week?" — instead of describing the situation passively. Naming the problem and the timeframe gives the other person something concrete to respond to.
Keep related words together and use consistent structure
A group text mixes the party date, an unrelated complaint about parking, and a question about food allergies into one unbroken paragraph, so people respond to whichever part they noticed first and ignore the rest. A note left for a roommate buries the actual request in the middle of an update about something else entirely.
Put one topic per message, or clearly separate topics within one message, so each thing you need an answer to can get one. If you have multiple questions, list them separately rather than folding them into a single run-on sentence.
Habits, not laws
None of this means every text needs to read like a work memo; plenty of everyday writing is meant to be warm, rambling, or purely social, and that's not a problem to fix. These habits matter specifically for messages that need an actual response — plans, requests, logistics — where clarity determines whether the message does its job. Someone who has practiced direct requests can still write a long, meandering message to a close friend without losing anything.
Friendliness and directness can seem to compete in everyday messages, since a short, plain request can read as curt to someone expecting more warmth. The fix is to add warmth around a clear core — state the plan and the question plainly, then add a friendly line, rather than dissolving the ask into the friendliness itself.
Name one thing, honestly
Think of the last message you sent that never got a reply — did it actually contain a clear question or request, or did it just describe a general hope that something might happen?
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
Put one topic per message, or clearly separate topics within one message, so each thing you need an answer to can get one. If you have multiple questions, list them separately rather than folding them into a single run-on sentence.