What Creators and Innovators Can Learn from The Elements of Style
Aisha had built a genuinely useful feature and now had four hours to write the launch post before her team's Friday deadline. Her draft opened: "We're incredibly excited to be introducing an innovative new solution that has the potential to fundamentally transform the way that users are able to engage with their workflows on an ongoing basis." She read it three times, and each time it sounded less like her actual product and more like every launch post she'd ever scrolled past without reading. The feature itself was simple: it saved a draft automatically every ten seconds so people stopped losing work. That sentence, the true one, was sitting three paragraphs down, buried under adjectives she'd added because "saves your draft automatically" felt too plain to announce. She deleted the opening paragraph entirely and started again with the sentence that actually said something, and it felt smaller and better at the same time.
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
Aisha's launch post spent thirty words on "incredibly excited to be introducing an innovative new solution that has the potential to" before reaching a single concrete fact. Creators pad announcements with intensity words — "incredibly," "revolutionary," "game-changing" — because the idea feels big and they want the language to match, but the padding does the opposite of what they intend.
Write the plain, factual sentence about what the thing does first — "It saves your draft automatically every ten seconds" — before deciding whether it needs any framing at all. If the plain sentence is genuinely exciting, it usually doesn't need adjectives stacked in front of it.
Prefer the active voice and concrete language
"Users are able to engage with their workflows more efficiently" describes nothing a reader can picture, while "innovative solutions are being delivered" hides who built what and how it works. Vague, abstract phrasing often signals the writer hasn't pinned down the mechanism themselves.
Replace the vague benefit with the specific mechanism — not "improves productivity" but "cuts a five-click export process down to one." If you can't state the concrete mechanism in one sentence, that's often a sign to go understand your own feature better before you try to describe it.
Keep related words together and use consistent structure
Release notes describe the same feature with three different names across the changelog, the in-app tooltip, and the help doc, so a user can't tell if they're looking at one feature or three. A pitch deck explains the problem, jumps to the team bio, then circles back to the solution, scattering related ideas across the document.
Pick one name for each feature and use it everywhere, and group information by topic rather than by the order ideas occurred to you. Before publishing, check that a reader encountering only one section could still follow what that section is about.
Habits, not laws
None of this means creative and marketing writing has to be flat or joyless; enthusiasm, voice, and even a well-placed superlative have their place in launch writing. These habits are meant to become the default so your first draft already gets closer to the actual thing you built, leaving revision time for voice rather than for excavating the real feature from the hype around it. A writer who has practiced plain description can still choose a bold, showy sentence deliberately, knowing what it trades against clarity.
Excitement and precision pull against each other in product writing, since the words that convey enthusiasm are often the least specific ones available. When you notice that tension, keep the concrete mechanism in the sentence and let enthusiasm show through structure and emphasis rather than stacked adjectives — a reader believes excitement more when it's attached to a specific fact.
Name one thing, honestly
Take the last paragraph you wrote describing something you built — could a stranger explain back to you, in one sentence, what it actually does?
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
Pick one name for each feature and use it everywhere, and group information by topic rather than by the order ideas occurred to you. Before publishing, check that a reader encountering only one section could still follow what that section is about.