When the Board Says No: Navigating Internal Resistance

Not everyone will be enthusiastic. And that's actually okay.

In my experience, the congregations that navigate the coworking discernment process best are the ones that take their skeptics seriously — not the ones that steamroll opposition in the name of innovation.

Internal resistance to a coworking pilot is almost always legitimate. The concerns are real, even when they're expressed awkwardly or rooted in anxiety rather than analysis. Learning to hear those concerns clearly, and to respond to them honestly, is one of the most important skills a coworking champion can develop.

Here's what I've learned about navigating this well.

The Three Categories of Resistance

In my experience, board-level resistance to coworking falls into three broad categories. Each requires a different response.

1. Theological Resistance

"This isn't what a church building is for."

This is the most common form of resistance, and it's often the most deeply felt. The concern is that opening the building to commercial use will compromise its sacred character — that the presence of laptops and business meetings will change something essential about a space that has been set apart for worship.

This concern deserves a theological response, not a financial one. Trying to overcome theological resistance with revenue projections almost never works. What does work is engaging the underlying question seriously: What does it mean for this space to be sacred? What does faithful stewardship of this building look like? What is the tradition's understanding of hospitality to the stranger?

I've written more about this in The Theology of Shared Space. The short version: the idea of church buildings as resources for the whole community is not a modern innovation. It's a recovery of something ancient.

2. Financial Resistance

"We can't afford the risk."

This concern is often expressed as theological resistance but is actually about financial anxiety. The board member who says "this isn't what a church is for" may really be saying "I'm worried about what happens if this fails and we've spent money we don't have."

This concern deserves a financial response: a clear, conservative model of what the pilot will cost, what it will generate, and what the downside looks like if it doesn't work. The key word is conservative. Optimistic projections that don't materialize will destroy trust. Honest projections that are met or exceeded build it.

It also helps to structure the pilot in a way that limits downside risk — starting small, using existing infrastructure before investing in upgrades, and setting clear decision points at which the congregation will evaluate whether to continue.

3. Practical Resistance

"Who's going to manage this? What happens when something goes wrong?"

This is the most tractable form of resistance, because it's asking a question that has a concrete answer. The board member who raises operational concerns is often doing the congregation a favor — they're identifying real problems that need to be solved before the pilot launches.

Take these concerns seriously. Develop clear answers to the operational questions: Who manages access? What's the protocol when a member damages something? How are disputes handled? What happens if a member's business creates reputational risk for the congregation?

A well-developed operations plan doesn't just answer these questions — it demonstrates to skeptical board members that the champions of the project have thought it through.

How to Have the Conversation

A few principles that I've found useful in navigating board-level resistance.

Listen before you advocate. Before you make your case, make sure you understand theirs. Ask open questions. Reflect back what you're hearing. Demonstrate that you take their concerns seriously. People are much more open to persuasion when they feel genuinely heard.

Separate the person from the position. Board members who resist coworking are not enemies of the mission. They're often the congregation's most careful stewards — people who have seen enthusiastic initiatives fail before and are trying to protect the community from repeating those mistakes. Treat them as allies, not obstacles.

Find the legitimate concern behind the stated objection. "This isn't what a church is for" often means "I'm afraid of change." "We can't afford the risk" often means "I don't trust the people proposing this to manage it well." Getting to the underlying concern — and addressing it directly — is more productive than arguing about the surface objection.

Propose a limited pilot, not a permanent program. One of the most effective ways to overcome resistance is to reframe the decision. You're not asking the board to commit to coworking forever. You're asking them to approve a six-month pilot with clear success metrics and a defined decision point. That's a much smaller ask — and it gives skeptics a legitimate off-ramp if the pilot doesn't work.

Be willing to slow down. The congregations that launch coworking over significant board opposition almost always regret it. A pilot that launches with genuine consensus — even if it takes an extra six months to build — is far more likely to succeed than one that launches over objections.

When the Answer Is Still No

Sometimes, after all the conversations, the board says no. What then?

First, respect the decision. The governance structures of your congregation exist for a reason. If the board has the authority to make this call, their decision deserves to be honored — even if you disagree with it.

Second, ask what would need to be true for the answer to be yes. Sometimes a "no" is really a "not yet" — and understanding what would change the answer gives you a roadmap for the future.

Third, consider whether the timing is right. Sometimes the right idea comes at the wrong moment. A congregation in the middle of a capital campaign, a pastoral transition, or a significant internal conflict may not have the bandwidth for a coworking pilot right now. That's not a permanent no; it's a situational one.

The goal isn't to win the argument. It's to build the kind of trust and consensus that makes a successful pilot possible. Sometimes that takes longer than you'd like.

If you're navigating internal resistance and want a thought partner, reach out. I've helped a lot of congregations work through this — and I'm glad to help yours.