When Staff and Volunteers Clash: Navigating Church Politics
Every outreach leader eventually finds themselves in the middle of a conflict they didn't start and don't fully understand.
A long-tenured volunteer is upset about a decision the new outreach director made. A staff pastor feels sidelined by a volunteer coordinator who's running her partnership as if the church exists to support it rather than the other way around. The children's ministry team quietly resents the outreach team for pulling their best volunteers into Saturday service projects. Someone from the deacon board thinks the outreach ministry has drifted "too political" or "not spiritual enough." The food pantry team and the missions team are competing for the same budget line and the same church calendar slots.
None of this is new. None of it is unique to any one church. And none of it is going to resolve itself.
Church politics — the quiet, often-unnamed friction between staff, volunteers, teams, and leadership — is a reason some outreach ministries lose momentum. Not partnerships. Not funding. Not vision. Internal friction.
The good news: most of this friction is preventable. And where it already exists, almost all of it is navigable — if the outreach leader has the right framework.
A Scenario to Consider
Note: The following story is fictional — a composite drawn from patterns that recur across churches. It doesn't depict any real church or person.
Imagine a mid-sized church with a thriving tutoring partnership at a nearby elementary school. The ministry was built over four years by a volunteer coordinator named Mark — a retired teacher, deeply loved by the volunteers, trusted by the school principal, and quietly the operational engine behind everything.
Then the church hired a staff outreach pastor named Jen. Smart, energetic, strategic, and new. In her first six weeks, Jen made several reasonable decisions. She wanted to tighten the background check process. She wanted to standardize the volunteer onboarding so it matched other church ministries. She wanted to move the tutoring budget line from a general fund to a tracked ministry line. She did all of this through formal channels. All of it was defensible. None of it was done in consultation with Mark.
Within three months, Mark had quietly stepped back. Several longtime volunteers followed him out. The school principal called the church office to ask why things felt different. And Jen — who had done nothing technically wrong — found herself leading a ministry that had lost most of its soul and half its people.
Nobody fought publicly. Nobody filed a grievance. The tension never surfaced in a meeting. It just quietly dismantled four years of work.
This is how some church conflicts play out. Not in dramatic confrontations but in silent withdrawal.
Why This Happens
The dynamic in the Mark-and-Jen scenario repeats everywhere because it's rooted in a structural reality most churches never name directly: staff and volunteers operate under different rules, different time horizons, and different sources of authority — and nobody has taught them how to work across those differences.
Staff carry role authority. Their decisions sit inside a formal structure. They're accountable to supervisors and often required to make systemic changes quickly.
Volunteers carry relational authority. Their influence comes from years of trust, personal relationships, and institutional memory — none of which show up on an org chart but all of which carry real weight in the congregation.
When these two kinds of authority collide — especially when the staff person is new and the volunteer has history — the staff person usually wins the formal battle and might lose the ministry. Not because the staff was wrong, but because they moved faster than the relationships could absorb.
This is the pattern Chapter 2 of Beyond the Walls warns about when it names "Unclear Expectations" as one of the most common mistakes in building a leadership team: written descriptions prevent confusion and frustration. And it's exactly what Chapter 7 is pointing to when it emphasizes giving every leader — paid or unpaid — a clear role description and clear expectations before conflict has a chance to form.
Friction isn't the problem. The absence of structure around the friction is the problem.
Six Patterns That Fuel Clashes
Most staff-volunteer conflicts fall into one of six recurring patterns. Naming them helps.
Role ambiguity. Nobody has written down who decides what. When a decision needs to be made, two people both think it's their call. One acts. The other feels bypassed.
Mismatched time horizons. Staff think in weeks and quarters. Veteran volunteers think in years and relationships. A quick staff decision can trample years of patient volunteer work without anyone meaning harm.
Resource competition. Two ministries compete for the same volunteers, the same budget, the same calendar slots. Without a shared leadership framework, they end up in zero-sum positioning.
Status erosion. A long-tenured volunteer who used to be the de facto leader now reports to a new staff person. The role shift is real. If it isn't honored directly and verbally, it leaks out sideways as resistance.
Alignment drift. The outreach ministry has slowly developed values, priorities, or language that differ from the broader church. Chapter 2 names this directly as a red flag: outreach operating with different values than broader church. Over time it creates factions.
Communication breakdown. The simplest and most common. Decisions are made without consulting the people who will carry them out. Information flows one direction instead of both.
Any one of these patterns, left unaddressed, will eventually produce the kind of silent conflict that cost Mark and Jen their partnership.
Prevention Strategies That Actually Work
Chapter 2 and Chapter 7 together name the specific disciplines that prevent most of this friction before it starts. The pattern is consistent — and the strategies are simple.
Written role descriptions for everyone. Every staff member, every volunteer coordinator, every team lead gets a one-page document describing their scope, their decisions, and the specific places where they need to collaborate with another role before acting. Not legalistic. Clarifying. The book is direct about this: unclear expectations are the single biggest preventable cause of team friction.
A new-staff onboarding protocol that honors existing volunteers. When a new staff person joins the team, their first 90 days should include intentional listening sessions with every long-tenured volunteer in their ministry area. Not to approve of their new authority — to understand what they're inheriting, learn the history, and signal respect for the people who built what they're now leading.
Shared decision rights language. Define clearly which decisions are staff calls, which are volunteer calls, and which require joint input. The book's "Role Clarity Questions" framework is useful here: What unique contribution does this role make? What's our distinctive role that other roles don't fill?
Quarterly team charter reviews. Every team — staff and volunteer combined — should sit down four times a year and ask three questions: What's working? Where is friction building? What needs to change? The book is clear: regular evaluation prevents small frictions from becoming entrenched conflicts.
A conflict escalation path. When friction surfaces, everyone should know what the next step is. Who do you talk to? Who facilitates the conversation? What happens if the two parties can't resolve it? Without this path, conflict goes underground and comes out as attrition.
Alignment conversations with senior leadership. The outreach ministry should regularly check its values, priorities, and language against the broader church. If drift is forming, name it early.
When Conflict Is Already Here
If the Mark-and-Jen scenario is already playing out in your church, the first move isn't a strategy document. It's a conversation.
Sit down with the people on both sides. Separately first. Then together, if they're willing. Not to adjudicate who was right. To understand what each person was trying to protect — because almost always, both parties were protecting something real.
Mark was protecting four years of relationships. Jen was protecting the ministry's long-term sustainability. Both were right. Both were valuable. The conflict wasn't about values. It was about process. Many church conflicts, surfaced carefully, turn out to be smaller than they look. The silence around them is what makes them feel enormous.
Pick one friction point in your outreach ministry this week — even a small one. Name it directly. Write down what each party is protecting. Then sit down with the people involved and have the conversation nobody has had yet. Unity in diversity isn't the absence of difference. It's what happens when difference is handled with structure, honesty, and respect. The alternative — silent withdrawal — is what quietly destroys more outreach ministries than any external force ever will.
Next week: "The Ministry That Died When I Went on Sabbatical" — a cautionary story about leadership dependency, and the specific practices that keep a ministry healthy enough to survive without you.
Comments