Writing Sermons That Carry Weight

A lot of preachers sound weak because they're telling people what to think instead of leading them somewhere they actually want to go. Authority in preaching doesn't come from volume or biblical quotes dropped like bricks. It comes from structure, conviction, and knowing exactly where your text is taking you before you open your mouth. I've spent years trying to figure out why some sermons land and others just fade out. The ones that stick have something about them that's hard to pin down. People describe it as hearing a certain sound. Not the preacher's voice, but the argument itself feeling resolved, like a trumpet call that leaves no room for escape.

The Certain Sound Of The Trumpet Crafting A Sermon Of Authority

Here's what that actually looks like in practice. You pick a single text. Not three texts propped up together because you couldn't decide which point to make. One passage. You read it until you can see what's happening in the grammar, the historical context, and the theological movement of the thing. Then you find the single argument it's making. Everything in your sermon serves that argument. Nothing else gets a seat at the table. I used to make the mistake of building sermons around themes. Justice. Forgiveness. Faith. Those are fine topics for a conversation, not for a sermon. A sermon is not a panel discussion. It's a delivery. When I switched to letting the text dictate the structure instead of my interest dictating the text, the whole tone changed. People started listening differently. The trumpeting sound comes from conviction of direction. When a preacher knows exactly where they're going and can't be diverted, the congregation senses it. It's the difference between someone who's reading notes and someone who's leading. You can tell immediately which one you're dealing with.

Here's the technical part most people skip. Your thesis statement should be one sentence. If you can't state your sermon's main point in a single breath, you don't actually know what you're preaching yet. I write mine on a slip of paper and tape it to my manuscript. If I drift from it, I stop. I've lost sermons mid-delivery by realizing I'd wandered into territory my text didn't support, and there's no coming back from that. You just have to pivot hard and recommit or fumble through to the end looking unsure. Structure matters more than inspiration. I use a three-part movement: exposition, illustration, application. Not always in that order, but those three elements have to be there. Exposition is where you prove you actually understand the text. Illustration is where you make it matter. Application is where you tell people what to do with it. Skip any one of those and the sermon collapses into either academic exercise or motivational speech. One thing beginners consistently miss: the application section shouldn't appear at the end like an afterthought. The entire sermon should be building toward it. Every illustration, every exegetical point, every pause should be oriented toward the question "so what?" If you're saving that for the last five minutes, you've already lost people who needed to hear the "so what" earlier to stay engaged.

Get the Full Details

Certain Sound of the Trumpet : Crafting a Sermon of Authority by Samuel ...
Certain Sound of the Trumpet : Crafting a Sermon of Authority by Samuel ...

I had a sermon last year on Habakkuk where I spent twenty minutes on the historical context of Babylonian invasion and completely forgot to connect it to anything my congregation was actually facing. I could see it. Shoulders checking phones. Eyes glazing. I stopped mid-sentence, closed the Bible, and said "here's what this actually means for you." It took three minutes. The room came back. But I'd wasted twenty minutes because I'd forgotten the destination. Another common failure is over-quoting. When every sentence is anchored to a Bible verse, nothing stands out. The text becomes background noise instead of the signal. Pick your key verses. State them clearly. Then explain them in your own words without hiding behind more citations. Authority comes from your ability to handle the text, not from proving you've read it. For delivery, speak slower than you think you need to. Pause after your major points. Give people a second to actually process what you just said instead of hammering through at full speed. Most preachers rush because they're afraid of silence. Silence is where the sermon lands. Without it, you're just making noise.

There's a limit to how much of this approach works. If your text is short or ambiguous, forcing a single argument can feel strained. Sometimes you genuinely have multiple points to make. In those cases, don't pretend it's one argument when it isn't. Just be honest about the structure. "There are two things this text requires of us..." works fine. The problem only appears when you're being sloppy about it. Also, this method requires genuine study time. If you're preparing sermons in two hours on Sunday morning, no amount of structural technique will save you. The authority people sense comes from you actually wrestling with the text beforehand. You can't fake that depth. Congregations know the difference between prepared conviction and rehearsed performance. Read widely outside your comfort zone. I used to only preach from passages I already felt comfortable with. Once I started pulling from obscure texts and working harder to make them speak, my preaching improved across the board. The struggle with difficult texts made the easy ones feel fresh again.

The goal isn't to sound authoritative. The goal is to actually be carrying something worth hearing. The trumpet sound isn't decoration. It's the result of a sermon that knows where it's going and doesn't apologize for the direction.

CERTAIN SOUND OF THE TRUMPET
CERTAIN SOUND OF THE TRUMPET