Persuasion in Writing: Email, Proposal, Application
The reader is busy, skimming, and one click from gone
Written persuasion is harder than spoken in one specific way: you're not in the room. You can't read the reader's face, adjust when they frown, or use your voice to carry the point. They skim on a phone, half-distracted, and they will stop reading the instant it stops being worth their time — no politeness keeps them there. Whatever the message — an email asking for something, a proposal, a job or university application, a request to a busy person — you get a few seconds to earn the next few seconds.
But writing has a compensating strength: you get to plan every word, and revise until it's right. Nobody persuasive writes a great email in one pass; they write a mediocre one and cut and sharpen it. This lesson is the structure and the edit that turn a rambling message into one that gets a yes. It assumes PS-09 (the mechanics of persuasion — ethos, logos, pathos, and Cialdini's levers); here we put those to work on the page.
What you'll have at the end
- The "bottom line up front" structure that respects a skimming reader
- The specific moves for email vs proposal vs application
- One real message of yours, rebuilt and measurably tighter
Lead with the point (bottom line up front)
The biggest difference between spoken and written persuasion: in writing, put the point first. A talk can build to a reveal; a busy reader who has to dig for your point through three paragraphs of throat-clearing just... doesn't. They need to know, in the first two lines, what this is and what you want.
- State the ask early and clearly. "I'm writing to ask if you'd be open to a 20-minute call about X" up top beats burying it in paragraph four. The reader decides whether to engage based on the opening, so put the deciding information there.
- This feels rude; it isn't. Front-loading the point respects the reader's time — it lets them grasp and act fast. Slow build-ups serve the writer's comfort, not the reader's.
Think of it as the inverted pyramid: most important thing first, supporting detail after, nice-to-haves last (where they can be skipped or cut).
The rest of this walkthrough is for members
Behind this: the full step-by-step, the exercise with a verifiable output, and the downloadable cheatsheet. Everything you've read above stays free, always.