How to write a sermon discussion guide small group leaders will actually use

The guide gets written with care and still doesn't get used

Someone on staff sits down Monday with the sermon notes and builds a discussion guide the way they'd build a sermon outline: an introduction, three points with sub-points, a few cross-references, eight or nine questions across two pages. It's thorough, and it took real time, and it was made by someone who wanted the groups to have something good.

Then most leaders open it, skim the first page, and run their group off memory anyway.

That's not a failure of effort. It's a mismatch between what got made and the situation it has to survive. Small group leaders aren't preparing a lesson. Most have a full-time job, a family, and maybe twenty minutes between getting home and people arriving at their door. A guide written for someone with an hour of prep time will lose to a guide written for someone with ten minutes, every single week.

A guide that gets used is built for that leader. Shorter, more specific, and structured so it can be read standing in a kitchen while the first car pulls up.

The one-page rule

If your guide doesn't fit on one page, it won't get read in full. That's just how busy people triage. A leader glancing at a two-page PDF fifteen minutes before group either skims page one and improvises the rest, or skips prep and asks whatever comes to mind once everyone's sitting down.

One page forces real editing decisions. You can't fit every cross-reference, every alternate application, and a warm-up icebreaker. You have to decide what the group actually needs. Five sharp questions beat twelve mediocre ones, because the leader only has time to ask five anyway.

Practically, one page means: the sermon's one big idea at the top, the scripture reference with it, and five questions. Nothing else. If you want to explain the theology behind each question, put it in a separate optional document leaders can ignore.

Put the sermon's big idea in writing, at the top

This is the line that does the most work on the page, and most guides don't have it.

Write the sermon's central idea as one sentence and put it at the top, above question one. Not a summary. One sentence, the thing you'd say if someone asked what Sunday was about.

The reason is the failure mode every group has. Without an anchor, a group drifts off the sermon inside ten minutes. Someone answers question one, it reminds someone else of something in the news or at work, and forty minutes later the group has had a nice conversation about something else entirely. Nobody did anything wrong. There was just nothing on the page holding the room to Sunday.

One sentence at the top fixes most of it. Everyone reads the same idea before anyone talks, including the three people who missed the service. When the conversation wanders, the leader has something to point at that isn't their own memory of the sermon.

Put the scripture reference right there with it, not buried in question three. A leader flipping between a Bible app and the guide loses the room fast, and that flipping happens more than you'd think in a living room with kids running through it.

The five-question arc

Five questions runs a 30 to 45 minute discussion, and it's few enough that a leader can read the whole guide in under two minutes. The order matters as much as the content. Move from easy to specific to personal.

1. A warm-up anyone can answer. Loosely tied to the theme, drawn from an ordinary part of the week rather than the sermon. This isn't filler. It gets quieter people talking before the harder questions arrive.
2. What stood out. An open question about what the group noticed or remembered from Sunday. This surfaces what actually landed, which isn't always what the outline emphasized.
3. A specific question tied to one moment. Pull the exact line, story, or verse that carried the big idea and ask directly about it. Vague questions get vague answers. A specific reference gets a real conversation.
4. An application question. How the idea connects to something concrete happening this week, not a hypothetical. "Where does this show up for you right now" beats "how should Christians respond to this."
5. A closing commitment. What someone will actually do differently this week. Small and specific enough to be checkable next week, not a resolution nobody remembers making.

Why long packets don't get opened

Long guides don't fail on effort. They fail on time and confidence.

Most volunteer leaders are not trained facilitators. They agreed to host because someone asked and the church needed hosts, not because they're comfortable running a discussion from a dense document. A packet with theological explanations and sub-questions under every point reads like something they're not qualified to handle. Faced with that, plenty of leaders set it aside, and the group talks about whatever comes up naturally, which is fine some weeks and thin most weeks.

A short, plainly worded guide does the opposite. It says: here's what to ask, in order, and you don't need to know more than what's on this page. That's not talking down to leaders. It's respecting that they signed up to host a conversation, not to become theologians, and a guide that makes hosting easy gets used far more often than one that makes it feel like a test.

Somebody has to own sending it

At most churches, nobody actually owns getting the guide to leaders. That sinks more guides than any writing problem on this page.

Comms makes the guide because it comes out of the sermon. Small groups owns the leaders. And the guide sits in a folder, or in a staff email thread, and reaches leaders late or not at all. When it doesn't go out, no meeting catches it, because it was never anyone's job.

Fix that before you fix anything about the questions. Name one person, put the send on their weekly list, and make it a task with a day attached rather than a thing that happens when someone remembers.

Then give it lead time. If groups meet midweek, send by the Tuesday or Wednesday before, not Sunday afternoon when everyone's still recovering from service. If groups meet on the weekend, aim a few days ahead. The specific day matters less than the gap between a leader receiving the guide and needing it.

Format matters too. A guide buried in a long weekly staff email gets lost. Sent as its own short message, with the questions visible in the body rather than only in an attachment, it gets read on a phone in a parking lot far more often than a PDF someone has to download.

What to cut

If you're trimming a longer draft, cut in roughly this order:

• Sermon summary longer than two sentences. The one big idea at the top is doing this job already.
• Extra cross-references. One scripture reference is enough. More turns a discussion guide into a study guide, and studying isn't what most groups gathered to do.
• Sub-questions. "And how does that make you feel, and why do you think that is" turns one question into three. Pick the sharpest version.
• Formal or academic leader instructions. If a sentence reads like a seminary syllabus, a leader reading on their phone between errands will skip it.
• Anything labeled "if time allows." Optional items go first when time is short. Leave them off the page and put them in a separate resource for leaders who want more.

The goal isn't a thinner sermon. It's a guide sized to the time a volunteer actually has, so the parts that make the page get used.

Where Extend the Sermon fits

Building this by hand takes real time. Pulling the one big idea, finding the moment to anchor question three, drafting and trimming five questions into something sharp. It's usually the first piece cut when a week gets busy, which is a shame, because it's often the one with the most impact per minute spent.

Extend the Sermon takes one sermon upload and returns a one-page discussion guide, along with 14 to 18 finished pieces total, in 20 to 50 minutes. It's built on the structure above: the big idea and the scripture at the top, five questions moving from easy to specific to personal, sized for one page. If you want to read a real one before deciding anything, run your first sermon through free and the guide comes back with everything else. You can also read how Extend the Sermon works for the full process.

It's $97 a month for one sermon a week, and $40 a month for each additional sermon. Cancel anytime. Your first sermon is free, no card required. Everything we make is yours to post, send, and keep.

Get your free sermon

Related

• Free sermon clip maker: run one sermon free and read the discussion guide it hands back.
• What to post after Sunday: where the discussion guide fits into a full week of content.
• Turn one sermon into a week of social media content: the full workflow, discussion guide included.