In Part 1 of this series, we looked at three patterns that keep church stories from landing. The process summary that documents what happened without showing why it mattered. The statistics update that mistakes numbers for meaning. The testimony with no tension that skips past the honest parts and goes straight to the resolution.

There is a real difference between a story that connects and one that doesn't, and it is worth understanding specifically enough to replicate.

A few years ago, I watched a church air a VBS volunteer video during a Sunday service. It featured one woman, probably in her mid-sixties, sitting in a chair in what looked like a classroom. No fancy backdrop. No motion graphics. Just her, talking.

She started by saying she almost didn't sign up. Her husband had passed away several months before, and she looked right into the camera and said plainly that she did not feel like she had anything left to give anyone. She felt old, tired, and irrelevant. The idea of spending five days in a room full of third graders sounded more like a punishment. She signed up anyway because a friend asked her to, and she didn't know how to say no.

Then she described what happened. Not in broad strokes. In specifics. A boy named Daniel, who reminded her of her son at that age so many decades ago. The way the kids argued about who got to sit next to her at snack time. A moment on Wednesday afternoon when a little girl grabbed her hand during prayer and held it for the whole prayer without letting go. She said that by Thursday, she had stopped thinking about what she had lost and started noticing what was still here. A gift of youth that needed her experience, patience, and love to share Jesus with them.

By the time she finished, there was not a dry eye in the room. And signups for the next year's VBS were higher than they had ever been.

What made that story move an entire congregation?

This video had a real person in a real situation that people could recognize. Grief. Loneliness. The feeling of not having enough left to be useful or needed in meaningful ways. Half the people in that sanctuary had felt some version of what she was describing, and when she named it, they were able to resonate.

It had honest tension. She did not walk into VBS confident and capable. She walked in defeated and reluctant. That reluctance is what made everything that followed meaningful. Without it, the story is just a nice lady who volunteered and had a good time.

It had specific details. Not "the kids were great" but Daniel, who reminded her of her son. Not "it was meaningful" but a little girl holding her hand during prayer on Wednesday afternoon and not letting go. Specific details separate a story from a summary. They create pictures. Pictures create a feeling. Feelings move people to act.

And it had an honest resolution that didn't oversell itself. She didn't say God completely healed her grief or that everything was better now. She said she stopped thinking about what she had lost and started noticing what was still here. That is an honest description of what hope actually feels like when you seek God in the middle of loss. It's believable precisely because it doesn't claim more than it can deliver.

What question should you ask before every story interview?

In your pre-interview conversations, there is one question that tends to unlock the real story faster than anything else: What were you afraid of?

Most people, when asked to share a story, start with what happened. When you ask them what they were afraid of, you steer them toward honesty. They access the part of the experience they didn't think to talk about — the doubt, the resistance, the reason they almost didn't do the thing they're now grateful they did. That is the part of the story that connects with people who are sitting in the same place they were in before it happened.

Follow that with: What surprised you? And then: What do you know now that you didn't know then? Those three questions get underneath the version someone has rehearsed and into the experience they actually had.

A story is doing its job when someone watching it thinks about their own life — not about the church's program or the ministry's success. Their own life. Their own fears and hopes.

Free. Every Thursday.

Get articles like this in your inbox each week. Church communications strategy, practical frameworks, and honest thinking.

Subscribe Free

How do you know when your church story is working?

A story is doing its job when someone watching it thinks about their own life and choices. Not about the church's program or the ministry's success or how impressive the production is. Their own life. Their own fears, questions, and hopes.

When someone finishes watching and thinks, "That sounds like something I'm going through," or "I wonder if that could happen for me," or "I didn't know the church had something for people like me," the story has done what no announcement, graphic, or email can do on its own. It has made a connection that is personal, real, and inspirational.

That is what you are aiming for every time you point a camera at someone and ask them to tell you what happened. Not a polished promotion. Not a ministry highlight reel. A true account of one person's experience that gives someone else permission to hope for their own.

Hold that standard. It is worth the extra conversation before the interview and the extra time in the edit. The people sitting in your congregation every week are carrying more than most of us know. A story told with that kind of truth can reach places that nothing else will.

Know Who You're Telling Stories To

The Audience Personas resource helps your team get clear on who's in the room and what they're carrying, so you can choose the stories that will actually connect with the people you're trying to reach.

Get the Resource