There’s a conversation happening in staff meetings all across the country right now. It sounds like vision. It feels like discernment. But if you listen closely, it’s actually something else.
It goes like this: “We’ve been doing this the same way for a while. Maybe it’s time to try something different.”
And the room nods. Because everyone’s tired of it.
That’s the problem.
You Have Lived Inside This. They Haven’t.
You’ve been thinking about Sunday since Monday. You worked through the series concept on Tuesday. You reviewed the environment design on Wednesday. By the time the weekend arrived, you had processed this content across five meetings, two revision cycles, and a handful of conversations that most of your attenders will never know happened.
They showed up Sunday morning. They experienced the hour. They went home.
That’s it.
They are not saturated. They haven’t lived inside this thing the way you have. They heard it once, maybe twice if you’re fortunate enough to have people showing up with any regularity. The programming familiarity you’re exhausted by is still new to them. The series concept you’ve outgrown is still landing for someone in row four.
What you’re bored with is still working.
The Law of Diminishing Astonishment
There’s a specific kind of leadership drift that doesn’t announce itself. It doesn’t show up in a budget crisis or a staff conflict. It shows up in your gut. And it’s deceptively easy to dress it up as leadership initiative.
Call it the Law of Diminishing Astonishment.
The longer you run a system, the less impressive it feels to the people running it. Not because the system stopped working. Because familiarity erodes the ability to feel the impact you’re actually having. The astonishment you felt the first time something clicked has been replaced by routine, and routine feels like stagnation even when it isn’t.
What It Looks Like in Practice
You’ve seen this pattern. A series format hits. Attendance responds. Engagement is up. And then, somewhere around month three or four, the team starts feeling restless. The creative energy that launched the system has nowhere to go, so it starts pointing at the system itself.
The conversation shifts from “how do we refine this?” to “should we replace this?”
And if nobody names what’s actually happening, a working system gets dismantled by the people responsible for running it. Not because something failed. Because the leaders got bored.
Why This Is a Leadership Problem, Not a Strategy Problem
Boredom is not data.
This is not a minor distinction. If you want to know whether to change the system, you need a different question than “does this still feel interesting?” You need to ask whether it’s still producing movement. And that answer lives in your metrics, not in the mood of your staff meeting.
A system that’s working but feels stale is a personnel development challenge. A system that’s producing evidence of stagnation is a strategy problem. Those require entirely different responses, and confusing them is one of the most expensive mistakes a growth-minded pastor can make.
What Actual System Problems Look Like
This is worth slowing down on, because the distinction between a familiarity problem and a system problem is where most churches lose traction.
System problems show up in the data:
- First-time guests not returning after their initial experience
- Engagement that’s flat or declining across ministry environments
- Next steps being offered but consistently ignored
- People staying in the same stage of faith for years without movement
These are structural indicators. They point to a real problem worth solving. When your data is telling you this, change is not just appropriate. It’s overdue.
The Difference Between Evidence and Exhaustion
Familiarity problems show up in the staff meeting. Your creative team is over it. Your key leaders are restless. You’ve lost the felt sense of momentum even though the numbers haven’t moved in either direction.
That is not a system problem. That is a leadership maturity challenge, and the solution is not a redesign. The solution is a recalibration of how your team understands their role in the system.
They are not the audience. The system was never built for them.
The Person You Keep Forgetting
Every time you sit in a planning meeting feeling under-stimulated by the programming you’ve been running, there is someone who almost didn’t come back this week. They showed up anyway. They sat in your room and experienced something that felt, to them, new. And there is a real chance that the repetition, the familiar environment, the consistent language and structure, is actually what’s making them feel safe enough to take a next step.
The System Is for Them
That first-time guest in row four doesn’t know what week three of the series looks like. They just know what Sunday felt like. The person who finally dragged their skeptical neighbor along is hoping Sunday is as good as you said it would be. The attender who almost stopped coming doesn’t need innovation. They need enough consistency to trust that something is here worth returning to.
When you dismantle a working system because you’re tired of it, they pay the cost. They’re asked to adapt to new sequencing, new language, a new experience right when they were starting to settle in. You reset their clock. You restart yours. And the work of creating enough familiarity for them to trust the environment starts over.
Solve the Right Problem
Before your next programming or planning meeting, pull 90 days of data. Attendance trend. First-time guest retention. Next step response rates. Engagement across environments.
Then ask one diagnostic question: Am I looking at a system problem or a familiarity problem?
If the data shows movement in the right direction, and the restlessness is coming from your team rather than your attenders, you don’t have a strategy problem. Name it clearly in the room.
Say it out loud: “We are not the audience. Our boredom is not a reason to stop.”
If You Don’t Have That Data
Here’s the honest reality for a lot of churches: the data isn’t being tracked with enough clarity to make this call with confidence. If you don’t know your first-time guest retention rate or whether next steps are producing movement, that’s the real problem to solve. Not the programming.
I recently built something called Church Pulse, a metric tracking and analysis tool built specifically for churches navigating this kind of decision. If you’re operating without clear data and making programming calls from instinct alone, email me at gavin@gavinadams.com. I want to help you get the right information in front of your leadership.
What Happens If You Don’t Name This
Leaders who change things because they’re bored train their teams to expect novelty over effectiveness. Over time, new becomes the standard. Whatever worked last quarter gets replaced before it’s finished working. Your attenders never get the repetition they need to move. Your team never builds the competency that comes from running a system long enough to actually refine it.
Churches that drift this way don’t fail dramatically. They plateau. Programs churn. Systems never mature. The pastor is always relaunching something.
The mission doesn’t stall because something stopped working. It stalls because nobody let anything work long enough to matter.
Boredom is the worst reason to change a working system. And naming that clearly, in the room, before the decision gets made, might be the most important leadership move you make this quarter.
Quotes to Share
- “Boredom is not data. Your creative team being over it is not a reason to stop a system that’s still reaching people.”
- “The Law of Diminishing Astonishment: the longer you run a system, the less impressive it feels to the people running it. That doesn’t mean it stopped working.”
- “The mission doesn’t stall because something stopped working. It stalls because nobody let anything work long enough to matter.”
Helping You Add More Intention To Your Mission,
Dr. Gavin Adams
