Why Speeches Are the Hardest Thing You'll Ever Write

A friend asked me to be best man last year. I said yes in two seconds. Then I sat on the speech for four months.

I write product copy, marketing pages, app store descriptions. None of it scared me. A six-minute toast at a wedding did. I think I finally understand why.

The stakes are wrong

Most writing has soft consequences. A bad email gets ignored. A bad blog post gets closed. A bad speech happens in front of 120 people who love the person you're talking about, with their parents in the second row, while everyone is sober enough to remember it.

You can't redraft live. You can't A/B test. There's no analytics dashboard. You either land it or you stand there watching a room try to be polite for you.

That asymmetry breaks people. The downside of a mediocre speech feels enormous. The upside of a great one feels nice but expected. So you start writing defensively, which is the worst mode to write in.

The expectation gap

Weddings, funerals, milestone toasts — the audience walks in with a template in their head. They've seen the movies. They've sat through a hundred of these. They expect a structure: a story, a turn, a line that lands, a raised glass.

But they also want it to feel personal. Specific. Not generic. Not something you could lift and drop into anyone else's wedding.

So you have to deliver on a familiar form using material no one else has. That's hard for professional writers. For someone who hasn't written anything longer than a Slack message in five years, it's brutal.

Blank-page paralysis is actually memory paralysis

When people say they're stuck, they usually aren't stuck on the writing. They're stuck on retrieval.

You know the person. You have twenty years of moments with them. But sit down with a blank doc and ask yourself "what's a story that captures who my brother is" and your brain returns nothing. It's the same reason you can't remember a single movie when someone asks for a recommendation.

The good speeches I've seen all share one thing: they pick small, specific moments. Not "he's the most generous person I know." Instead: the time he drove four hours at 2am because I locked myself out of an Airbnb in Tagaytay. Specifics carry weight that adjectives can't.

What actually lands

A few things I've noticed from sitting through maybe sixty of these:

• One clear thread. Not a list of memories. A single idea about the person, supported by two or three stories.
• Earned emotion. You don't tell people to feel something. You describe a moment and let them get there on their own.
• Brevity. Five minutes is plenty. Eight is the ceiling. Past that, you're hurting yourself.
• A line they can repeat. People remember one sentence. Make sure there's one worth remembering.
• Read it out loud before the day. Sentences that look fine on paper collapse when spoken.

What kills a speech: inside jokes that exclude the room, a chronological list of biographical facts, anything that sounds like it was generated, and trying to be funnier than you actually are.

On using tools

I built Atoast partly because of that best man speech. The thing I needed wasn't a writer. I needed something to pull stories out of me, then help shape them into a structure that breathes.

That's what it does. You answer questions about the person — how you met, a moment that surprised you, what you'd want them to know — and it drafts something from your actual material. You edit from there.

It won't write a speech for you if you have nothing to say. Nothing will. But if you've been staring at a blank doc for three weeks knowing the wedding is in nine days, it's a way to stop staring.

The speech is still yours. It has to be. The room can tell.