Speech Writing Rules

A speech is heard once, in real time, with no way to reread a confusing sentence — every rule here exists because the ear forgives and processes language completely differently than the eye does. Text that reads perfectly well on the page can fail completely out loud, and text that looks repetitive or fragmented on the page can land perfectly when spoken.

Write for the ear, not the page

• Keep sentences short enough to say in one breath. A written sentence with three embedded clauses is unfollowable at speaking pace — a listener can't "reread" a sentence that lost them.
• Prefer simple sentence structures (subject-verb-object) over the complex subordinate clauses fine for print — the listener has no way to hold a long dependent clause in memory while waiting for the main verb.
• Use contractions and spoken cadence deliberately, even in formal speeches — "we won't" said aloud sounds natural; "we will not," repeated, starts sounding stilted unless the formality is the point.
• Avoid words that are hard to say cleanly or easily misheard (tongue-twisting consonant clusters, words that sound like other words in context) — read every line aloud during drafting specifically listening for this.

Rule of three

• Group examples, arguments, and lists in threes wherever natural — three is the smallest number that reads as a pattern rather than a coincidence, and the largest a listener can hold without a list feeling like an enumeration.
• Use triads for emphasis at key moments ("not next year, not next month, but today") — the repeated structure itself creates rhythm that signals importance to the ear, independent of the words' literal content.
• Don't force a third item that weakens the first two just to hit the pattern — two strong points beat three where the third is filler.

Callbacks

• Plant a specific phrase, image, or line early in the speech that you deliberately return to later — a callback rewards attentive listeners and gives the speech a sense of structure that's felt rather than explained.
• Use the callback at a structurally significant moment (the close, a turning point) rather than incidentally — it should feel like a payoff, not a repetition.
• Keep the planted phrase short and distinctive enough to be memorable on first hearing — a callback to a forgettable line lands as confusing rather than satisfying.

Open strong, close stronger

• Never open with "Thank you for having me" or a throat-clearing pleasantry as the first substantive line — open with the strongest single line in the speech: a fact, a question, a scene, a stake. The first ten seconds decide whether the room is listening.
• Save housekeeping (thanking the host, acknowledging the audience) for after the hook, briefly, not before it.
• Make the closing line the second-strongest moment in the speech, after the opening — it's the line the audience actually remembers and repeats afterward, so it deserves as much drafting effort as the opening, not a rushed "so, in conclusion..."
• End on the speech's own terms — a callback, a direct charge to the audience, a return to the opening image — not on a generic thank-you that dissipates the momentum just built.

Rhythm and pauses

• Vary sentence length deliberately: a run of short sentences builds urgency; one longer sentence after a run of short ones creates release. Monotone sentence length, long or short, reads as flat when spoken.
• Mark intentional pauses in the script itself (a line break, an ellipsis, or an explicit [pause] note) at moments meant to let a line land — a joke, a hard fact, a turn in the argument. Don't leave pacing entirely to memory in the moment.
• Use repetition of a key phrase across a paragraph or section deliberately for rhythm ("we built this. we built this together. we built this because we had to.") — spoken repetition that would read as clumsy on the page can build real momentum out loud.

The read-aloud test

• Read every draft aloud, standing up, at the pace you'd actually deliver it — silent reading and reading aloud reveal completely different problems, and only reading aloud catches breath-length issues, awkward phrase mouthfeel, and unclear stress.
• Time the read-aloud pass against the actual speaking slot — written pace and spoken pace diverge more than writers expect, and a script that reads fine silently often runs long out loud.
• Note anywhere you stumble, reread, or lose your place while reading aloud — that's the exact spot to rewrite, regardless of how the sentence looks on paper; the ear is the only reliable test for a speech.