Questions to ask after every sermon series

The Four Questions Every Growing Church Asks After a Series

After working with thousands of churches over the last nine years, there's one practice we've watched the thriving ones return to again and again. It shows up at the end of every sermon series and major event, and it's worth borrowing.

They run a 30 minute meeting within 48 hours of the event or series wrapping up, and they ask the same four questions every time. It's the simplest habit on their calendar, and most of them will tell you it's the one they've learned the most from.

Why most churches skip it

The reason most churches don't do this is because momentum gets in the way. You finish Easter and the next series is already on the calendar, your team is exhausted from the weekend, and reviewing what just happened feels like a luxury you can't afford on top of everything else.

We understand that. We've been in ministry too, and we know how much weight the team is already carrying coming into a Monday like that. The growing churches we've watched have come to the same realization, which is that you can't afford not to. Without a review process, every series becomes a stand-alone project, the lessons your team learned the hard way last time slowly evaporate by the time you're planning the next one, and the same problems show up again.

A thirty-minute conversation can save you from most of that. Here’s the questions we recommend to ask:

Question 1: What went right?

This is the question we always recommend starting with, because it's the one most teams skip and the one that ends up carrying the most weight. When you spend the first ten minutes naming what worked, you give your team something they rarely get to hear in church work: a clear, specific affirmation of what they did well.

Name the moments and choices that paid off so the team knows what to repeat. Surface the specific transition that worked, the graphic that drove the most signups, the way someone on your team framed the closing prayer. Specificity matters here as much as it does anywhere else in the meeting.

Your worship leader doesn't always know that the lobby felt warm and inviting that morning, and your designer doesn't always hear that the graphic she made was the reason someone clicked through and ended up walking through your doors. The affirmation lands differently when it comes from a teammate who watched it happen from a different angle.

Question 2: What went wrong?

This one is harder, and it requires a culture where people on your team can say hard things without consequence. We've watched plenty of churches try to run this kind of review without that culture in place, and it falls apart fast. People hedge, they protect each other, and the meeting becomes a polite recap instead of a useful one.

If you're not sure your team is there yet, that's worth naming out loud at the top of the meeting. Tell them you're asking for honesty and you'll receive it without defensiveness, and then prove that's true by how you respond.

When the door is open, get specific. "The transition between worship and the message lost the room" tells the team something they can use; "it felt off" doesn't. Specificity is what gives this question its weight, so look for the friction points, name them clearly, and avoid making it about blame. The point is having something the team can act on the next time around.

Question 3: What were we missing?

This one surfaces the things that should have been there and weren't: the follow-up email no one remembered to draft, the parking lot signage for first-time guests, the heads-up to volunteers about the new arrival time. Most of these only become obvious in hindsight, which is why asking this question while the event is still fresh matters as much as it does.

You won't be able to fix every gap you surface in one meeting, and you don't need to. What this question gives you is a running list your team can check against the next time something similar lands on the calendar.

Question 4: What can we do differently next time?

This is the question that turns the conversation into action, and it draws from everything you've named so far. Pull from the first three answers as you work through it together, and resist the urge to leave anything vague.

Push past "communicate better" to "send the volunteer email two weeks out instead of one." Push past "improve flow" to "drop the announcement video from the front of service and put it after the sermon." That's the kind of specificity that carries through into the next event and changes the outcome.

The next iteration only gets better when you give yourself something concrete to carry into it.

Run it within 48 hours

Timing matters more than you'd think. If you wait longer than two days to do the review, the details start disappearing, and most of what's worth remembering lives in those details: the specific moment something landed, the exact wording that didn't work, the look on a volunteer's face when they realized something was missing.

Block the time on your team's calendar before the event happens, and treat it as non-negotiable. The week after Easter or a major launch is the easiest week of the year to skip a meeting, which is exactly why this one needs to be on the books.

Write it down

The review only pays off if the answers end up somewhere the team can pull them up later, which means writing them down somewhere shared and findable. A doc in your project management tool, a page in your team's playbook, or a shared note in Notion can all work for this. The format matters less than the discipline of doing it consistently.

Six months from now, when you're starting to plan the next major event, the first move your team should make is pulling up the last debrief and reading it together. That's how the lessons compound. Without writing them down, you'll find yourself starting from scratch every time, relearning what your team already knew.

The takeaway

Compounding improvement at any church comes from a willingness to look back at what you just did, name what worked and what didn't with honesty, and bring those lessons into the next round. None of it is glamorous work, and it rarely shows up in a job description, but it's what separates the teams that keep getting better from the ones that keep starting over.

This won't be the most exciting thirty minutes on your calendar, but it'll be one of the most useful. Over the course of a year, it changes how your team plans, executes, and recovers from every major moment. Yep…we said it!

If you'd like a creative partner who can take production off your team's plate so the people in those seats have the room to think strategically about review, planning, and what's next, we'd love to talk.