FREE

Course certificates are free until March 31, 2027.

PT702E Church Administration and Leadership

Lecture 5-3: Consensus-Based Decision-Making

View as cards (3 min)
Contents 53
PT702E Church Administration and Leadership
Chapter 0 · Introduction: Administration Is the Body of Ministry, Not Its Shadow
  1. Introduction: Administration Is the Body of Ministry, Not Its Shadow
Chapter 1 · Chapter 1: Why Administration — A Theology of Order and Stewardship
  1. Lecture 1-1: Order Is God's Own Concern
  2. Lecture 1-2: The Household Manager — Administration as Stewardship
  3. Lecture 1-3: Administration as a Spiritual Gift
  4. Lecture 1-4: What to Take from Secular Management Theory, and What to Leave
Chapter 2 · Chapter 2: Biblical Models of Organization
  1. Lecture 2-1: Jethro's Advice to Moses — Delegation, Capacity, and Choosing Leaders
  2. Lecture 2-2: The Wilderness Camp — Order Around a Theological Center
  3. Lecture 2-3: Temple Staffing and Levitical Organization — Building for the Long Term
  4. Lecture 2-4: Acts 6 — A Complaint, a Diagnosis, and a Change in Role
  5. Lecture 2-5: The Jerusalem Council — Deliberation, Evidence, and a Communicated Decision
Chapter 3 · Chapter 3: Church Polity and the Theology of Office
  1. Lecture 3-1: The Office of Elder
  2. Lecture 3-2: The Office of Deacon
  3. Lecture 3-3: The Three Polity Families
  4. Lecture 3-4: Convergence and Divergence in Practice
Chapter 4 · Chapter 4: Governance Structures in Practice
  1. Lecture 4-1: The Governing Board — Purpose, Composition, and Limits
  2. Lecture 4-2: Bylaws and the Function of Writing Things Down in Advance
  3. Lecture 4-3: Legal Incorporation and Denominational Structure — The Basics
  4. Lecture 4-4: Committees and Delegated Authority
Chapter 5 · Chapter 5: Meetings and Decision-Making
  1. Lecture 5-1: What Makes a Meeting Effective
  2. Lecture 5-2: Parliamentary Procedure
  3. Lecture 5-3: Consensus-Based Decision-Making
  4. Lecture 5-4: Discernment-Based Decision-Making
Chapter 6 · Chapter 6: Financial Stewardship
  1. Lecture 6-1: A Theology of Giving: Cheerful, Proportionate, and Voluntary
  2. Lecture 6-2: Budgeting as a Theological and Practical Discipline
  3. Lecture 6-3: Internal Financial Controls: Protecting Money and Integrity Together
  4. Lecture 6-4: Financial Transparency and Its Limits
  5. Lecture 6-5: Compensation and Conflicts of Interest
Chapter 7 · Chapter 7: Staffing and Volunteer Leadership
  1. Lecture 7-1: Hiring and Job Descriptions
  2. Lecture 7-2: Supervision and Staff Development
  3. Lecture 7-3: Volunteer Recruitment, Training, and Retention
  4. Lecture 7-4: Burnout in Staff and Volunteers
Chapter 8 · Chapter 8: Facilities, Risk, and Safety
  1. Lecture 8-1: Facilities as Stewardship
  2. Lecture 8-2: Child Protection Policy
  3. Lecture 8-3: Risk Management and Insurance Basics
  4. Lecture 8-4: Emergency Preparedness
Chapter 9 · Chapter 9: Conflict Management and Church Discipline
  1. Lecture 9-1: Matthew 18 and the Shape of a Fair Process
  2. Lecture 9-2: 1 Corinthians 6 and the Question of Litigation
  3. Lecture 9-3: Mediating a Dispute as an Administrative Leader
  4. Lecture 9-4: Formal Church Discipline
  5. Lecture 9-5: When and How to Involve Outside Help
Chapter 10 · Chapter 10: Strategic Planning and Vision
  1. Lecture 10-1: Mission and Vision Are Not the Same Document
  2. Lecture 10-2: A Planning Cycle, and What Secular Frameworks Can and Cannot Do
  3. Lecture 10-3: What Gets Measured Is What Gets Pursued
  4. Lecture 10-4: Building a Plan a Congregation Will Actually Own
Chapter 11 · Chapter 11: Leading Change and Organizational Culture
  1. Lecture 11-1: Leading Change: Two Models and What Each Misses
  2. Lecture 11-2: Managing Resistance Without Dismissing It
  3. Lecture 11-3: Organizational Culture: What Actually Forms It
  4. Lecture 11-4: Succession: Planning the Handoff Before It Is Forced
Chapter 12 · Chapter 12: Legal, Ethical, and Cross-Cultural Administration
  1. Lecture 12-1: Legal Compliance, in General Terms Only
  2. Lecture 12-2: The Ethics of Institutional Power
  3. Lecture 12-3: Cross-Cultural Administration
  4. Lecture 12-4: Whistleblowing and Institutional Self-Correction
  5. Lecture 12-5: Sustainability, and a Personal Philosophy of Administration

Jump to the key points ↓

12 min

"We reached consensus" is sometimes used loosely to mean nothing more than "most people seemed fine with it" or "no one objected loudly." This lecture treats consensus as a more demanding and more specific practice than that: a defined process requiring real time, a culture that can tolerate extended disagreement without treating it as disloyalty, and — crucially — a clear, agreed answer to what happens if genuine consensus is not reached, because a process with no fallback can be stalled indefinitely by a single unresolved objection.

This lecture states what consensus actually requires beyond simply polling a room for objections, and states honestly where it is well suited to a church's decision-making and where it is not.

What these 12 minutes give you

  • Distinguish consensus, properly practiced, from a loose sense of "no one objected."
  • Name the specific structural elements — roles, a defined process for raising and resolving an objection, and an agreed fallback — that make consensus workable rather than merely aspirational.
  • Explain why a consensus process with no fallback is vulnerable to being blocked indefinitely by a single member.
  • Read Acts 15's account of the Jerusalem council as an example of a group reaching a decision "with one accord," and state honestly what that text does and does not prove about consensus as a modern method.
  • State at least two features of a situation that make it well suited, or poorly suited, to a consensus process.

Then it seemed good to the apostles and the elders, with the whole assembly, to choose men out of their company, and send them to Antioch with Paul and Barnabas: Judas called Barsabbas, and Silas, chief men among the brothers.

it seemed good to us, having come to one accord, to choose out men and send them to you with our beloved Barnabas and Paul,

Acts 15:22 (World English Bible)

Acts 15:25 (WEB)

The Jerusalem council in Acts 15 faced a genuinely divisive question — whether Gentile converts had to be circumcised and keep the law of Moses to be saved — and reached a resolution described, twice, in language of shared accord rather than a bare majority outcome: it "seemed good" to the whole assembly, and the delegates sent with the decision are described as having "come to one accord." This is real textual evidence that the early church valued, and in this instance achieved, a decision the whole body could own together, not merely one a numerical majority imposed on a resistant minority. It is not, on its own, evidence for a specific modern procedure with defined roles and a formal fallback vote — those are later, practical inventions for achieving something like what Acts 15 describes, not a method Scripture itself lays out. The distinction matters: this lecture claims Acts 15 as a genuine, encouraging precedent for seeking real, not merely counted, agreement — not as a proof text for the particular consensus process described below.

1. What consensus actually requires, beyond "no objections"

Stand-aside and block

A genuine consensus process is not simply asking a room, "does anyone object?" and moving on if no one speaks up. Silence in a room is not the same thing as considered agreement, and a process that treats it that way risks mistaking discomfort with speaking up, rather than actual agreement, for consensus. A workable consensus process, as described in practitioner literature on the method, typically defines several things in advance: a facilitator distinct from whoever is advocating for the proposal, responsible for managing the discussion rather than pushing it toward a particular outcome; a clear, low-stakes way for a member to register a stand-aside — genuine disagreement the member is nonetheless willing to let the group proceed with, distinct from a block, a stronger statement that the member believes the proposal is a serious enough error, or violation of the group's core values, that it should not go forward at all; and a structured way for an objection to be heard, understood, and, where possible, addressed by modifying the proposal, rather than simply overridden.

This is considerably more demanding than an informal sense that "everyone seemed okay with it." It requires real time — a proposal that meets a serious objection may need to be revised and brought back, sometimes more than once, before the group can honestly say it has reached agreement rather than merely exhausted its patience for further discussion. It requires a culture, cultivated deliberately, that treats a member's extended disagreement as a genuine contribution to be worked through rather than an obstacle to be waited out or quietly resented. And it requires members willing to distinguish their own strong preference from a genuine block — since a process where anyone can halt the whole group over any disagreement, however minor, quickly becomes unworkable, and the difference between a preference and a principled objection has to be something the group has actually talked about and agreed on in advance, not left for each member to define for themselves in the moment.

2. The fallback question

Settle the fallback first

The single most important, and most often skipped, design decision in a consensus process is what happens when genuine consensus is not reached after a real, good-faith attempt. Without an answer to this question settled in advance, a consensus process has a structural weakness: a single member, whether through a strongly held conviction or, less charitably, through simple stubbornness, can prevent the group from ever acting, indefinitely, on any matter that member chooses to block. Some communities that practice consensus address this by defining a fallback — for example, a supermajority vote (commonly two-thirds or higher) that the group turns to only after consensus has genuinely been attempted and not reached, so that the group is not simply abandoning consensus at the first sign of difficulty, but also is not permanently hostage to one unresolved objection. A group that adopts consensus as its normal method without ever agreeing on a fallback has not actually finished designing its decision-making process; it has designed a process that works only for as long as no one uses their standing within it to block something the rest of the group wants.

3. Where consensus is, and is not, well suited

Consensus tends to work well where the group is relatively small, where members already have enough relationship and trust to engage real disagreement without it becoming personal, and where the decision at hand is one that will genuinely need every member's ongoing cooperation to succeed — a shared ministry commitment, for instance, that will not actually work if a third of the group is quietly resentful about how it was decided. It tends to work poorly where a decision is urgent and cannot wait for an extended process, where the group is large enough that reaching genuine, examined agreement from every member becomes impractical, or where a legal or bylaws requirement calls for a specific, documented vote regardless of how much informal agreement already exists. A congregation is not required to choose one model for every kind of decision it faces; a body that generally values consensus for decisions that require broad ownership can still reserve a formal vote, addressed in 5-2, for matters where speed, a legal requirement, or the sheer size of the group makes a full consensus process impractical.

Consensus: proposal, objection, revision, fallback A process with no fallback can be blocked indefinitely Proposal Facilitator opens discussion Objection raised Stand-aside, or a genuine block Proposal revised Addresses the objection directly Consensus reached "One accord" (Acts 15:25) If revision still does not resolve a genuine block, after a real attempt: Agreed fallback e.g. a defined supermajority vote — decided in advance, not improvised in the moment A process with no fallback step gives one objector permanent power to halt the whole group

In short

  • Real consensus is more than "no one objected." Silence may hide discomfort, not agreement.
  • A workable process has a facilitator apart from the advocate, a way to stand aside (disagree but let the group proceed) or block (object strongly), and a way to address objections.
  • It needs time and a culture that treats lasting disagreement as a contribution, not disloyalty.
  • It also needs an agreed fallback, such as a supermajority vote, or one member can block action indefinitely.
  • Acts 15:22 and 15:25 show the early church valuing "one accord," but they do not prove a modern procedure.

Topic: This lecture explains what consensus decision-making requires and where it suits, or does not suit, a church.

Remember: Consensus needs defined roles, a way to resolve objections and a fallback agreed in advance. Without a fallback, one objector can stall the group.

Caution: Acts 15 is an encouraging precedent for seeking real agreement, not a proof text for a particular consensus method. Consensus works poorly when decisions are urgent, groups are large, or bylaws require a vote.

One line to carry into ministry: Before adopting consensus, agree in advance what counts as a block and what happens if agreement is not reached.

Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • Before this lecture, would you have described "we reached consensus" the way this lecture defines it, or more loosely? What difference does the more demanding definition make in practice?
  • What is the difference between a "stand-aside" and a "block"? Why does a healthy consensus process need both concepts, rather than treating any disagreement the same way?
  • This lecture argues that a consensus process without an agreed fallback is structurally vulnerable to a single objector. Have you seen a group get stuck this way? What eventually happened?
  • Acts 15 is offered as genuine evidence for valuing "one accord" over a bare majority, but not as a proof text for a specific modern consensus procedure. Do you find that distinction persuasive, or does it feel like it concedes too little, or too much, to the text?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.