The Congregation Is Not the Audience

I once sat through a service where everything looked right on paper.

The worship team was tight. Vocals were strong. The songs were familiar enough to follow — or at least most of them were. The pastor had clearly put hours into the sermon. By any objective measure, the service was well-executed.

And I spent almost the entire time watching it happen.

Afterward, the feedback from the congregation trickled in. The songs felt unfamiliar, hard to enter. The set felt like a performance — one thing after another with no clear thread. The lyrics weren't landing. The sermon ran long enough that whatever had registered earlier had faded before anyone could hold onto it. People were polite about it, because people usually are. But underneath the politeness was something I recognized: they'd been an audience. They had come to participate and found themselves observing instead.

Here's what unsettled me most about hearing that feedback. My first instinct was to diagnose the worship leader's song selection. My second was to critique the sermon's structure. And somewhere in those two instincts was a confession I wasn't quite ready to make: I had felt exactly what they described. I'd sat in that same room and watched the same thing happen and gone home without naming it.

I'd become a spectator too.

There's a word in Greek that the early church used for what they did on Sunday mornings. Leitourgia. It's the word we translate as "liturgy," and it means something specific: the work of the people. Not the work performed for the people. Not the work performed at the people. The work of them. The congregation was the subject of the sentence, not the object.

This is not a footnote. It's the architecture of everything.

When the early church gathered — before the cathedrals, before the concert sound systems, before anyone had invented a platform with a spotlight — they understood themselves to be the primary actors in the room. The leader's job was to order the gathering, to facilitate what the congregation was doing together. The word they used for that person, proestōs, meant simply "the one who stands in front." Someone who ordered the assembly so that the assembly could do its work. The role was facilitation, not performance.

That's a very different job description than what many of us are living with.

Here's where it gets uncomfortable, because the problem runs in two directions at once.

The first version is visible and easy to name: the worship team as concert act. Lights dimmed, band elevated, congregation standing in the dark watching professionals perform. The form communicates something regardless of the theology in the lyrics. It says: your role here is to receive. Ours is to deliver. That's not a covenant gathering. That's a concert with religious content.

But the second version is harder to see because it doesn't look like a performance at all. It looks like serious, text-centered, theologically rigorous ministry. The sermon-centered service where everything before the message is warmup and everything after is cool-down — where the congregation's job during the service is to sit attentively, take notes, and absorb what the preacher has prepared. That congregation is also an audience. They're watching a different kind of professional perform a different kind of expertise. The structure still says: your role is to receive. Mine is to deliver.

Both versions put the action in the hands of the specialist and reduce the congregation to observers. Both are the same structural error wearing different clothes.

1 Peter 2:9 calls the church a "royal priesthood." That phrase got retrieved in the Reformation as a direct argument against the idea that a specially trained class had to stand between ordinary Christians and God. Luther's point was that every baptized believer has the same direct access to God through Christ — not individualism, but equality. No one needs a human mediator to get through. The curtain tore. The way is open for all.

But what Luther was recovering wasn't just a doctrine about access. He was recovering a doctrine about function. A priesthood doesn't just have access — it acts. Priests do something. They intercede. They offer. They participate in the work of approaching God on behalf of the community.

If the congregation is a royal priesthood, then the congregation's presence in a worship service is not a passive presence. They are not there to receive a delivery. They are there to act — to confess, to receive, to pray, to declare, to be sent. The gathering of the church is a gathering of priests. When they become an audience, something has gone wrong at the level of theology, not just logistics.

I've thought about that service a lot since. Not with the detachment of a worship scholar diagnosing someone else's liturgical mistakes. More with the discomfort of someone who should have seen it sooner than he did.

Because what I'm describing isn't a problem that lives only in other people's churches. I've led services where I was more focused on the execution than on whether the room had anything to do. I've planned sets where the songs made sense to me and the transitions felt elegant and the congregation had a beautiful piece of music to watch unfold. I've heard sermons I admired — theologically dense, carefully argued — that left the room with nothing to respond to. The congregation had been informed. They had not been engaged as participants.

The question I keep coming back to is this: when the service ends, were the people in that room actors in something, or audience to something? Because leitourgia — the work of the people — implies they had actual work to do. Not just presence. Work.

What does that change in practice?

For those who plan and lead worship: the question isn't only "is this good content?" It's "does this give the congregation something to do?" Congregational singing is active. Responsive reading is active. Confession spoken together is active. Receiving the Lord's Supper together is active. Being sent with a benediction that the congregation claims, not just receives, is active. A service can be beautifully executed and still fail to be worship if the people in it have had nothing to do but observe.

For those who preach: the sermon's job is to address the congregation as participants, not an audience. When it lands, they should be arriving somewhere together — not watching the preacher arrive somewhere interesting. That requires knowing the difference between a congregation that has been engaged and a congregation that has been impressed.

For everyone who serves in any role: the people sitting in those chairs are a royal priesthood. That reframes the question entirely — the question isn't how well you executed your part, but whether the space you created gave them room to act. Whatever the role, that's the job. Order the space so that they can do their work.

The feedback from that service was painful to hear, for everyone involved. But I've come to think it was honest testimony to something real. The people in that room had been given something to watch. What they came for was something to be part of.

That's not a preference. It's the word the early church used for what they gathered to do.

The work of the people.

When you think back on a service where you felt genuinely engaged — not just moved, but actually participating — what was different about it? What gave you something to do?