Lecture 11-2: Managing Resistance Without Dismissing It
목차 53
- Lecture 1-1: Order Is God's Own Concern
- Lecture 1-2: The Household Manager — Administration as Stewardship
- Lecture 1-3: Administration as a Spiritual Gift
- Lecture 1-4: What to Take from Secular Management Theory, and What to Leave
- Lecture 2-1: Jethro's Advice to Moses — Delegation, Capacity, and Choosing Leaders
- Lecture 2-2: The Wilderness Camp — Order Around a Theological Center
- Lecture 2-3: Temple Staffing and Levitical Organization — Building for the Long Term
- Lecture 2-4: Acts 6 — A Complaint, a Diagnosis, and a Change in Role
- Lecture 2-5: The Jerusalem Council — Deliberation, Evidence, and a Communicated Decision
- Lecture 3-1: The Office of Elder
- Lecture 3-2: The Office of Deacon
- Lecture 3-3: The Three Polity Families
- Lecture 3-4: Convergence and Divergence in Practice
- Lecture 4-1: The Governing Board — Purpose, Composition, and Limits
- Lecture 4-2: Bylaws and the Function of Writing Things Down in Advance
- Lecture 4-3: Legal Incorporation and Denominational Structure — The Basics
- Lecture 4-4: Committees and Delegated Authority
- Lecture 5-1: What Makes a Meeting Effective
- Lecture 5-2: Parliamentary Procedure
- Lecture 5-3: Consensus-Based Decision-Making
- Lecture 5-4: Discernment-Based Decision-Making
- Lecture 6-1: A Theology of Giving: Cheerful, Proportionate, and Voluntary
- Lecture 6-2: Budgeting as a Theological and Practical Discipline
- Lecture 6-3: Internal Financial Controls: Protecting Money and Integrity Together
- Lecture 6-4: Financial Transparency and Its Limits
- Lecture 6-5: Compensation and Conflicts of Interest
- Lecture 7-1: Hiring and Job Descriptions
- Lecture 7-2: Supervision and Staff Development
- Lecture 7-3: Volunteer Recruitment, Training, and Retention
- Lecture 7-4: Burnout in Staff and Volunteers
- Lecture 8-1: Facilities as Stewardship
- Lecture 8-2: Child Protection Policy
- Lecture 8-3: Risk Management and Insurance Basics
- Lecture 8-4: Emergency Preparedness
- Lecture 9-1: Matthew 18 and the Shape of a Fair Process
- Lecture 9-2: 1 Corinthians 6 and the Question of Litigation
- Lecture 9-3: Mediating a Dispute as an Administrative Leader
- Lecture 9-4: Formal Church Discipline
- Lecture 9-5: When and How to Involve Outside Help
- Lecture 10-1: Mission and Vision Are Not the Same Document
- Lecture 10-2: A Planning Cycle, and What Secular Frameworks Can and Cannot Do
- Lecture 10-3: What Gets Measured Is What Gets Pursued
- Lecture 10-4: Building a Plan a Congregation Will Actually Own
- Lecture 11-1: Leading Change: Two Models and What Each Misses
- Lecture 11-2: Managing Resistance Without Dismissing It
- Lecture 11-3: Organizational Culture: What Actually Forms It
- Lecture 11-4: Succession: Planning the Handoff Before It Is Forced
The previous lecture named two frameworks for understanding why change is hard. This lecture is more concrete: what does a leader actually do when resistance shows up in a specific meeting, from a specific person or faction, about a specific proposal? The single most important move, and the one most often skipped under time pressure, is diagnosis before response — asking what kind of resistance this actually is before deciding how to answer it.
Not all resistance is the same, and treating it as though it were invites two opposite failures. Treating every objection as a principled conviction that must be honored risks giving a veto to whoever is most persistent, regardless of the objection's merit. Treating every objection as mere discomfort with novelty risks steamrolling a genuine theological or confessional concern that deserved to be engaged on its own terms. This lecture works through both the diagnostic distinction and a set of concrete practices — communicating the reason for change in advance, using a pilot period, and naming real losses honestly — that reduce the unnecessary portion of resistance without pretending all resistance is illegitimate.
이 17분으로 얻는 것
- Distinguish a principled theological or confessional objection to a proposed change from resistance driven by discomfort with novelty, and explain why responding to the wrong one is itself a failure of pastoral judgment.
- Explain, using Exodus 16:2-3, why a narrative can take a group's grumbling seriously as reflecting a real, material loss without thereby concluding that the change that provoked the grumbling was wrong.
- Name at least three concrete practices — advance communication of the reason for change, a pilot or trial period, and honest acknowledgment of loss — that reduce resistance that is not principled, and explain what each practice actually does.
- Explain why a leader who reverses every unpopular decision teaches a congregation something different, and worse, than a leader who holds a decision while genuinely listening to it.
The whole congregation of the children of Israel murmured against Moses and against Aaron in the wilderness; and the children of Israel said to them, "We wish that we had died by the hand of Yahweh in the land of Egypt, when we sat by the meat pots, when we ate our fill of bread, for you have brought us out into this wilderness, to kill this whole assembly with hunger.
Exodus 16:2-3 (World English Bible)
1. Two different reasons people resist, and why the difference matters
When a proposed change meets resistance, a leader's first task is not to respond but to diagnose. Broadly, resistance to an administrative change comes from one of two very different places, and they call for entirely different responses.
The first is principled conviction: an objection grounded in a theological, confessional, or ethical claim that the proposed change is actually wrong, not merely unfamiliar. A member who objects to a proposed change in worship practice by citing the congregation's confessional standards, or an who objects to a proposed governance change on the grounds that it would violate the commitments examined in Chapter 3, is raising a claim that has to be engaged on its own merits — agreed with, argued against, or at minimum taken seriously as a live theological question — not managed as a morale problem to be smoothed over.
The second is discomfort with novelty: an objection whose real content is unfamiliarity, inconvenience, or the ordinary human cost of change, even when it is expressed in the vocabulary of principle ("this isn't how we do things here" is rarely a confessional claim, however it is phrased). This kind of resistance is real and deserves to be taken seriously as a genuine cost to real people — a later section of this lecture insists on that point — but it does not carry the same obligation to change the proposal's substance that a principled objection does.
The category error runs in both directions and both are administrative failures. Treating a principled objection as mere discomfort — waving away a genuine confessional concern as "people just don't like change" — is a failure to engage a legitimate argument on its merits, and it is also, on the logic worked out in Chapter 1's reading of 1 Corinthians 14, a use of administrative authority to suppress rather than to serve order. Treating mere discomfort as though it were a principled veto — reversing a sound decision every time someone frames their unfamiliarity in weighty language — teaches the wrong lesson for exactly the reason worked out below. A leader's actual diagnostic work, often under real time pressure in a meeting, is to ask plainly what kind of objection is on the table before deciding how much weight it should carry.
2. Exodus 16: taking a real loss seriously without concluding the change was wrong
Exodus 16 opens a chapter and a half after Israel's deliverance from four hundred years of slavery in Egypt — a change whose rightness this course assumes rather than argues. Yet the very people who had just been delivered "murmured against Moses and against Aaron" (v. 2) and said they wished they had died in Egypt "by the hand of Yahweh," specifically naming what they missed: sitting by the meat pots, eating bread to the full (v. 3). The comparison is not measured; slavery under Pharaoh did not in fact include sitting comfortably by full meat pots, and the text does not correct this exaggeration in the moment. What it does is take the underlying fear seriously — the people were hungry, in an unfamiliar wilderness, uncertain whether their basic material needs would be met — and God's actual response in the rest of the chapter is not primarily rebuke but provision: manna each morning, quail in the evening.
This narrative models something specific and useful for a leader managing resistance to a change whose direction is not actually in question. The exodus was not wrong because Israel later regretted parts of what it cost them. A change can be the right change and still involve a real, mourned loss for the people living through it — not a loss that should be denied, minimized, or treated as evidence the decision itself was mistaken, but a loss that deserves an honest and practical response. God does not tell Israel their fear was foolish and leave it there; God feeds them. A leader facing resistance rooted in a genuine, if imperfectly expressed, material or emotional loss has a comparable two-part task: hold the direction, and respond concretely to the actual need or fear driving the complaint, rather than treating the complaint only as a discipline problem to be corrected.
This is also a caution against a stock reading of this text that flattens it into "the people grumbled and were wrong to grumble." The text is more interesting than that, and a leader who uses it only to justify dismissing complaint entirely is bending the narrative to a use it does not fully support.
3. Practices that reduce unnecessary resistance
Three concrete practices, none of them exotic, address the discomfort-with-novelty category directly and reduce the volume of resistance that principled engagement alone will not touch.
Communicating the reason before the change, not after resistance appears. A change announced without its reasoning invites people to supply their own explanation, and the explanation supplied is rarely the most charitable one available. Explaining why a change is being made — what problem it solves, what alternatives were considered and rejected, and why — before the change is implemented gives people something to evaluate on its merits rather than something to simply react to.
A pilot or trial period. Committing to a change permanently and irreversibly raises the stakes of every objection, because agreeing to try it can feel indistinguishable from agreeing it is right forever. A defined trial period — try the new format for two months, then formally review it — lowers those stakes, converts an abstract argument into an experience the congregation can evaluate together, and gives a leader real data rather than only predictions to work from at the review point. This is also where Kotter's "short-term win," discussed in Lecture 11-1, does real work: a trial that visibly succeeds, even modestly, builds trust for what follows in a way argument alone cannot.
Honest acknowledgment of real losses. William Bridges, in Managing Transitions, distinguishes a change — the external, situational event, such as adopting a new service format — from a transition — the internal, psychological process a person goes through in response, which Bridges describes as moving through an ending (letting go of what was), a neutral zone (an uncomfortable in-between with the old gone and the new not yet fully trusted), and a new beginning. A leader who manages only the change and ignores the transition is solving half the actual problem. Naming specific losses aloud — "this means the eight o'clock service, which some of you have attended for twenty years, will end" — rather than speaking only in terms of what is gained, is not a concession that weakens the case for change; it is what allows people time and space to move through the ending Bridges describes, instead of getting stuck resisting a change whose real losses were never acknowledged.
4. Not capitulating to all resistance
None of the above amounts to reversing a decision whenever it meets resistance. A leader who does that — who treats sustained complaint as itself sufficient reason to abandon a sound decision — teaches the congregation a specific and corrosive lesson: that the way to win an administrative argument is to persist and escalate, not to have the better argument. This does not reward wisdom; it rewards whoever is willing to be the loudest or the longest holdout, and it makes every future decision hostage to whichever faction is prepared to resist longest.
The distinction this lecture has been building toward makes the difference precise. A principled objection that identifies a genuine flaw in the proposal, or a genuine confessional problem, should change the plan — that is what engaging it on its merits means. Resistance rooted in discomfort with novelty, once genuinely heard, communicated with, and given a fair pilot period, does not by itself carry the same claim on the outcome, even though the people experiencing that discomfort deserve to be heard with the same seriousness Exodus 16 models. Holding a decision after genuinely listening, and reversing a decision because listening surfaced a real defect, look similar from a distance. They are not the same act, and a leader has to be able to tell, in each specific case, which one is actually happening.
핵심 요약
- First diagnose the resistance. Principled theological or confessional conviction must be engaged on its merits. Discomfort with novelty is real, but does not carry the same claim to change the proposal.
- Both errors are failures: dismissing a real conviction, or giving a veto to any objection phrased in weighty language.
- In Exodus 16:2-3, Israel's complaint reflects real hunger and fear, and God responds with provision, not only rebuke. A right change can still involve real loss.
- Three practices reduce unnecessary resistance: explain the reason before the change, use a pilot period, and name real losses aloud. William Bridges separates the external change from the inner transition.
- A leader who reverses every unpopular decision teaches that persistence beats a better argument.
- Holding a decision after real listening differs from reversing it after listening finds a real defect.
Topic: This lecture explains how to tell principled objections from discomfort with novelty and how to respond to each without dismissing people.
Remember: Diagnose first. Engage conviction on its merits, and answer discomfort with reasons, a trial period and honest naming of loss.
Caution: Exodus 16 should not be read only as "the people grumbled and were wrong." The lecture also does not say a leader should give in to all resistance.
One line to carry into ministry: Before answering an objection, ask whether it is a claim that the change is wrong or the cost of change, and name the losses aloud.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Describe a real or plausible case where an objection phrased as "this isn't how we do things here" turned out, on closer examination, to be a genuine theological concern rather than mere discomfort. What would have been lost if a leader had dismissed it too quickly?
- Exodus 16 does not correct Israel's exaggerated comparison between slavery and freedom, and God's response is provision rather than only correction. What does this suggest about how a leader should respond to a complaint that is emotionally real but factually overstated?
- Think of a change you have witnessed, or could imagine, where a trial period would have made a real difference to how it was received. What specifically would the trial period have needed to include to function as Lecture 11-2 describes — a genuine test, not a foregone conclusion dressed up as one?
- What is the practical difference, in a specific decision you can imagine facing, between "holding a decision after genuinely listening" and "refusing to listen"? How would someone outside the decision be able to tell which one had actually happened?