What Creators and Innovators Can Learn from On Writing Well
Sam had written and rewritten the "About" page for a new app four times, and it still opened with "revolutionizing the way people connect through innovative, next-generation solutions." A beta tester, asked to explain the app back after reading the page, described something entirely different from what Sam had built. Sam sat with that for a while, defensive at first, then curious. The page didn't say what the app actually did — helped small book clubs schedule meetings without twelve back-and-forth texts — because that sounded too small and ordinary next to "revolutionizing." Sam deleted the paragraph and wrote the plain version: this app finds a meeting time for your book club in one tap. It felt almost embarrassingly simple to publish. But the next tester who read it described the app correctly on the first try, and Sam realized the fancy language had been protecting an idea that wasn't as sharp as it should have been.
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
Clutter is the enemy in how you describe your work
A creator writes an artist statement or product description full of phrases like "reimagining the paradigm of user experience" because that register feels appropriately ambitious for something new. A reader finishes the paragraph without being able to say, in their own words, what the thing actually is or does. Practice: Write a one-sentence version of your description using only words a twelve-year-old would understand, with no adjectives borrowed from other pitches you've read. Use that sentence as the true first line, and let any fancier language, if you still want it, come after.
Write a one-sentence version of your description using only words a twelve-year-old would understand, with no adjectives borrowed from other pitches you've read. Use that sentence as the true first line, and let any fancier language, if you still want it, come after.
Clarity of writing requires clarity of thought about what you actually built
An innovator writes that their product "leverages a novel synergistic framework" without being able to explain, in one sentence, what specific problem it solves for one specific person. The vague description is a sign that the idea itself hasn't been pressure-tested against a real use case yet. Practice: Before writing about your idea, name one real person and one real moment when they'd reach for what you built. Write the description from that scene outward, not from the feature list inward.
Before writing about your idea, name one real person and one real moment when they'd reach for what you built. Write the description from that scene outward, not from the feature list inward.
Revise ruthlessly on the descriptions everyone else will read first
A creator writes a launch post in one excited sitting and publishes it immediately, so the opening paragraph is about the creator's journey rather than what the reader gets from the thing itself. Readers bounce before reaching the actual explanation, buried three paragraphs down. Practice: After drafting, delete the first paragraph entirely and see if the piece still makes sense — often it does, and it's stronger for starting where the real information begins. Keep cutting from the top until every remaining sentence is doing real work.
After drafting, delete the first paragraph entirely and see if the piece still makes sense — often it does, and it's stronger for starting where the real information begins. Keep cutting from the top until every remaining sentence is doing real work.
Personality survives simplicity in how you present new ideas
A plainly described idea usually reveals more of its creator's actual judgment and taste than a grandly worded one does, because specificity is where a distinct point of view becomes visible. The plain version of Sam's app description was still recognizably Sam's — a particular, small, useful idea, described without apology. Simplicity doesn't make new work sound less ambitious; it usually makes the actual ambition easier for someone else to see.
Investors, juries, or early adopters sometimes respond to bold, abstract language before they've seen enough to respond to plain specifics, so cutting all the ambition-signaling can feel like underselling the work. A workable balance is to open with one plain, concrete sentence about what the thing does, then follow it with a shorter statement of scale or ambition, rather than starting with abstraction.
Name one thing, honestly
Describe your current project to yourself in one sentence a stranger could repeat back accurately — does your actual pitch match that sentence, or hide it?
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
After drafting, delete the first paragraph entirely and see if the piece still makes sense — often it does, and it's stronger for starting where the real information begins. Keep cutting from the top until every remaining sentence is doing real work.