Small Groups
Small Group Discussion Questions From Your Sermon: A Pastor's Workflow
Every small group leader knows the moment. It's Wednesday night. Eight chairs in a living room. The group is finally settled. Someone says: "So… what stuck out to you from the sermon?"
Silence. Two people look at the floor. Someone reaches for the cheese board. The leader pivots to the prepared question — something like "What does this passage teach us about God's character?" — and gets one polite, generic answer that nobody can build on.
This isn't a small group problem. It's a question design problem.
A well-written discussion guide can take a tired Wednesday-night group and turn it into the most honest conversation in their week. A bad one — and most are bad — turns small group into a slow Bible quiz. Here's the difference.
Why do small group questions fall flat?
Most sermon discussion guides default to abstract questions:
- "What does this passage teach us about God?"
- "What is the main point Paul is making?"
- "How can we apply this to our lives?"
These look like good questions on paper. In a real group of 8 adults at 8pm on a Wednesday, they fail for three reasons:
1. They're too big. "How does this apply to our lives" is a question about all of life. People don't know where to start, so they say nothing. Or they say something so generic ("trust God more") that the group can't reply.
2. They're not personal. Abstract questions ask the group to perform analysis. People at 8pm don't want to perform — they want to be honest. Personal questions ("Tell us about a time when…") give people a way in.
3. They have no scaffolding. A good discussion has a shape: warm up, look at the text, react, apply. Most guides skip the warm up and the react, and jump straight to apply. The result feels like an interrogation.
How do you structure a sermon discussion guide?
Four blocks, in order. Each block has a job. Skip a block and the group stalls.
Block 1 — Icebreaker (1 question, 5 min)
The job: get every voice in the room before you talk about anything heavy.
Bad icebreaker: "How was your week?" (too open; leaders end up answering for everyone)
Good icebreaker: a single, specific, low-stakes question loosely tied to the sermon's image.
Example for a sermon on Mark 4 (calming the storm):
"What is the most over-packed suitcase you have ever had to carry on a trip?"
It sounds silly. It works. Everyone has a story, the answers are short, and you've subtly primed the room for the sermon's "we carry too much" theme without naming it.
Block 2 — Looking back (1 question, 5 min)
The job: get the sermon back into the room without quizzing anyone.
Bad: "Can you summarize the main point?" (only the diligent will answer)
Good: a question that pulls one moment, not the whole sermon.
Example:
"Thinking back to Sunday's message, what was one part of the sermon — a phrase, an image, a verse — that stuck with you or felt especially relevant to your week?"
This works because it doesn't require comprehension. It only requires memory of the moment that landed for that specific person.
Block 3 — Into the Word (2-4 questions, 20-25 min)
The job: open the actual text together. This is where most discussion guides over-write.
The pattern: ask about one verse at a time, with one concrete observation tucked into the question itself.
Bad: "What does verse 38 mean?"
Good: "Read Mark 4:38. The disciples find Jesus asleep on a cushion during a storm that experienced fishermen thought would kill them. What does that one detail tell you about how Jesus saw the situation?"
Notice the structure:
- Read the verse.
- Point to a specific detail in the verse ("asleep on a cushion").
- Ask one open question about that detail, not about the whole passage.
This is the formula that works. 2-4 of these, building on each other, will fill 20 minutes of real conversation.
Block 4 — Story and application (2 questions, 10 min)
The job: move the text into this week's life. Not "all of life" — this week.
Bad: "How can we apply this passage?"
Good: a personal story prompt + one specific action question.
Story prompt:
"Tell us about a time when you felt like the disciples in this story — when something hit hard enough that you genuinely thought, 'God, do you not care?'"
This invites confession. People will share. The group will hold it. The leader doesn't need to fix it.
Action question:
"If you took your biggest worry right now and brought it to God in the same posture as the disciples — honest, not cleaned up — how would that change the way you handle this week?"
This is the question that goes home with people. They'll think about it on the drive home. That's the work the small group is meant to do.
Bonus — One step + a prayer prompt
Two more elements that make a guide feel pastoral, not academic:
One step this week (1 sentence) A specific, concrete next-step the group commits to before they leave. Example: "This week, before you vent to anyone else about the situation that's eating you, present it to God in one specific sentence and finish with one specific gratitude."
Prayer prompts (3-4 lines) Not a long scripted prayer. 3-4 short topics the group can pray about together, each in one line.
How long should a sermon discussion guide take to write?
Twenty minutes a Tuesday morning. Here's the sequence:
- Re-read your sermon manuscript. 5 min — pull out the bottom line and 3-4 strongest illustrations.
- Pick the icebreaker. 2 min — what physical, low-stakes image from the sermon would work as a "what's a time when…" question?
- Pick the 2-4 "Into the Word" verses. 5 min — for each, identify the one concrete detail you want the group to notice.
- Write the 2 application questions. 5 min — one personal story prompt, one "this week" action question.
- Pick the one step + draft 3-4 prayer prompts. 3 min.
Total: 20 minutes. Print to PDF or paste into the small group leaders' Slack/text thread by Tuesday afternoon.
The first time this takes 40 minutes. By month two, you'll be at 15.
Where do pastors get stuck?
Two predictable failure modes:
1. Writing for the leader, not the group. A discussion guide isn't notes. It's questions. If the guide reads like an essay with bullet points, you've over-written. Cut everything that isn't a question or a 1-line setup.
2. Putting "stretch" questions before "warm-up" questions. The most common mistake. A guide that opens with "What does this teach us about God's sovereignty?" loses the room in 90 seconds. Always: icebreaker → looking back → into the word → application. In that order.
If you've seen the same pattern in your weekly devotional emails — generic questions that nobody answers — the fix is the same: pull from Sunday's sermon, not from a blank page. We cover that in How to Turn Sunday's Sermon Into a 5-Day Devotional.
Where Sermoneer fits
Sermoneer reads your sermon and produces a small group discussion guide in this exact 4-block structure (icebreaker, looking back, into the word with verse-anchored questions, story + application), plus the one-step and prayer prompts.
You spend 10 minutes lightly editing — usually swapping one icebreaker for something more local to your context, or sharpening one of the application questions. Then you send it to your leaders by Tuesday afternoon.
If you have a sermon already in your dashboard, the Small Group tab has the working draft. If not yet, start with one upload and look at the structure on a real sermon of yours.
The goal isn't to make small groups easier on the leaders. It's to make them deeper for the people in the room. Better questions do that more than longer guides ever will.