Exodus 20:1-17

Exodus 20 Sermon: What Freedom Looks Like With Limits

Exodus 20 opens with a sentence pastors often preach past: before any command is given, God identifies himself as the one who already rescued this people. That order is the whole difficulty and the whole reward of preaching this text - law follows rescue, not the reverse, and a sermon that gets the order backward turns freedom into a new kind of bondage before it reaches verse 17. That is the sort of thing Preaching Lab is built to help a pastor check afterward: whether the sermon kept that order or lost it somewhere along the way.

The text at a glance

The chapter opens with self-identification, not instruction: verse 2 names God as the one who brought Israel out of Egypt before a single command is given, so the commandments arrive as the shape of an already-rescued life rather than the terms of rescue.
The first four commandments, verses 3 through 11, govern the vertical relationship - no other gods, no idols, right use of the name, and rest on the seventh day - and each one protects something about who God is, not only what Israel must avoid.
The remaining six, verses 12 through 17, turn horizontal, moving outward from the nearest relationship a person has, parents, to the most distant, a neighbor's house and everything in it.
The list ends, deliberately, not with an act but with a desire: verse 17's prohibition on coveting reaches behind behavior to the wanting that produces it, which is why this commandment is the hardest one to preach and the easiest one to skip.
Read this way, the ten are less a checklist than a single answer, in ten parts, to the question of what a delivered people owes the God who delivered them and each other.

Three ways a sermon can go

Grace before law

Preach verses 1-2 as the interpretive key for everything that follows: these are not entrance requirements but the shape of a life already given. This costs the preacher a clear, explicit move from rescue to response somewhere in the sermon, not just an opening nod to verse 2 that gets left behind by verse 5.

One command, two directions

Trace how the vertical commands toward God and the horizontal commands toward neighbor are one connected claim rather than two separate lists, so that idolatry and dishonoring parents turn out to be the same kind of failure aimed differently. This requires resisting the pull to treat the first four as background and the last six as the real sermon, since congregations often hear the second table as more relevant.

One commandment, closely read

Take a single commandment - the Sabbath command or the coveting command reward this the most - and let the other nine stay in the background for one Sunday. This costs breadth: the sermon needs to say plainly that it is not attempting all ten, so the choice does not read as an arbitrary omission.

Where sermons on this text commonly slip

The prologue disappears

Verse 2 gets read aloud and then never mentioned again, so by the time the sermon reaches verse 17 the commandments sound like conditions for God's favor rather than the shape of a life already rescued. The text does not support that reading, but the sermon's own structure can produce it by accident.

Ten commandments, no minutes

A survey sermon tries to touch all ten and gives each one a sentence, which means none of them gets the specific, checkable engagement a listener can actually carry into the week. Verse 17 usually loses this race first, since coveting is harder to illustrate than theft or murder.

One tradition's answer presented as the text's answer

The Sabbath commandment, verses 8-11, in particular gets preached as if every listener already agrees on what it requires now - a specific day, a specific kind of rest - when traditions differ on whether and how it carries into the New Testament. The sermon does not have to resolve that; it does have to know it is there.

Five questions to ask afterwards

Did the sermon state or clearly reference verse 2's identification of God as rescuer before moving into the commandments, or did the commandments arrive first with no stated basis?
Count how many of the ten commandments received more than a passing sentence - was it two or three treated with real specificity, or all ten skimmed at the same shallow depth?
Did the sermon name verse 17's coveting as a matter of internal desire distinct from outward theft, or did it either skip verse 17 or fold it into the eighth commandment?
If the sermon addressed the Sabbath commandment in verses 8-11, did it acknowledge that traditions differ on how it applies now, or did it present one view as the text's own settled conclusion?
Listen to the closing minutes: did the application name one action with a verb, a timeframe, and an object a listener could complete before next Sunday, or did it end on a direction like obey God's law more?

Keeping the application on the ground

A landed application for this text names one commandment and one specific move, not the whole list restated as a resolution. Keep God's commandments is a direction anyone can nod at without changing anything by Sunday; an application that survives the drive home names a particular commandment, a particular person or habit, and something small enough to actually attempt.

Before next Sunday, tell one specific person about one thing you currently want that is not yours, naming it out loud rather than keeping it private, as verse 17 presses toward.
Pick one block of time this week, an evening or a morning, and set it aside from work as a trial of the rest commanded in verses 8-11, then notice what made that hard.
Call or visit one parent, or if that is not possible, one older relative who stands in that place, and say one specific thing you have not said, as a concrete act under the fifth commandment in verse 12.

Get a report on your recording of this sermon What Preaching Lab is