무료

수료증 무료 발급 — 2027년 3월 31일까지.

LM201E Leading a Small Group Well › 요약으로 복습하기

요약으로 복습하기

LM201E 과목의 강의 29편을 요약만으로 훑어봅니다. 시험 전날에 쓰세요.

제 0 장 Introduction: The Room That Does the Work

  • A small group exists to do things a large gathering structurally cannot: sustained mutual knowledge, reciprocal "one another" commands, and real-time noticing of one missing person.
  • A small group is not a substitute for corporate worship, the sacraments, or ordained pastoral oversight — it is a different tool, not a smaller version of the same tool.
  • This course has seven chapters, each ending in a Practice Lab that applies the chapter to a real or realistic scenario.
  • This course does not teach systematic theology, public preaching, or church polity — it assumes those are covered elsewhere and stays focused on the room itself.

Q: What can a room of five to twelve people do that a room of five hundred structurally cannot? A: Sustain mutual knowledge between specific people over time — noticing when someone is missing, carrying an ongoing story, making reciprocal "one another" commands actually possible.

Q: Is a small group a substitute for corporate worship or the sacraments? A: No. It is a different tool for a different job, not a smaller version of the large gathering.

Q: How many chapters does this course have, and what does each one end with? A: Seven, each ending in a Practice Lab applying that chapter to a real or realistic scenario.

제 1 장 Chapter 1: What a Small Group Is For

  • A small group's core purpose is not delivering more content; it is doing what the New Testament's "one another" commands require — a reciprocal, name-level scale of relationship a crowd cannot supply.
  • Robert Wuthnow's research (Sharing the Journey, 1994) found people join small groups chiefly to be known, and also identified the risk of a group becoming a private "quasi-community" untethered from the wider church.
  • John 13:34-35 and Hebrews 10:24-25 both assume a scale where people can actually know and exhort one another by name.
  • A small group is not a substitute for corporate worship, the sacraments administered by ordained ministry, or the pastoral authority the wider church has ordained.
  • The leader's first job is protecting what the group is actually for — not teaching it well, and not letting it quietly become a rival to the church it belongs to.

One-sentence summary: A small group exists to do specific, reciprocal, name-level things a crowd structurally cannot do — not to deliver more content and not to replace the corporate worship, sacraments, or ordained pastoral authority of the wider church.

Terms to remember: one another commands, reciprocity, quasi-community.

Carry forward to 1-2: this lecture named what the group is for and what it must not become. The next lecture asks what that means concretely for the person running the room: what is a leader's actual job, if it isn't teaching?

  • Leading a discussion and teaching a lesson are different jobs: teaching transfers content; leading creates the conditions for a group to discover it together.
  • The most common failure mode is the meeting quietly becoming a mini-sermon, and it happens because facilitating a real discussion is genuinely less comfortable than delivering a prepared explanation.
  • 1 Peter 5:2-3 contrasts "lording it over" the group with "being an example" to it — modeling honesty and vulnerability rather than insisting on the last word.
  • Acts 20:28 frames whatever authority a leader holds as delegated stewardship of a flock that belongs to God, not ownership.
  • Traditions genuinely disagree on how much independent pastoral and doctrinal authority a lay small-group leader carries; this course states both positions without resolving the disagreement.

One-sentence summary: A small-group leader's job is to host and shepherd a conversation, not to teach a lesson, and resisting the pull toward the mini-sermon is a skill worth naming directly — while traditions genuinely disagree about how much independent authority that lay role carries.

Terms to remember: hosting versus teaching, mini-sermon, lording it over.

Carry forward to 1-3: this lecture described the leader's posture inside a single meeting. The next lecture zooms out to the group's shape over time — what a covenant is for, and why group size has a defensible ceiling.

  • A group covenant makes explicit, before anyone is hurt by its absence, what members can expect around confidentiality, attendance, and how the group will handle changing shape.
  • Confidentiality stated explicitly is what makes real vulnerability feel safe; most groups reasonably carve out an exception for risk of serious harm.
  • Exodus 18:17-23 records Jethro diagnosing that Moses' single-point structure was wearing out both Moses and the people, and proposing a tiered structure instead — the same principle behind a small group's size ceiling.
  • Group dynamics research (Steiner's concept of process loss) gives a concrete mechanism for why roughly five to twelve members is a durable range: airtime and trackability per person shrink as the group grows.
  • A group that outgrows its size has real options — capping and redirecting, apprenticing a co-leader toward a split, or naming a temporary limit — and letting growth happen silently is not a neutral choice.

One-sentence summary: A group covenant and a defensible size ceiling are not administrative overhead but the infrastructure that protects what a small group is actually for — a covenant makes vulnerability safe, and a size limit, grounded in both Exodus 18 and group dynamics research, keeps every member able to actually be known.

Terms to remember: group covenant, process loss, tiered structure.

Carry forward to 1-4: the Practice Lab asks you to turn Lectures 1-1 through 1-3 on your own group and produce a one-page written diagnosis.

  • A useful diagnosis names specific instances from your actual group, not general impressions about small groups.
  • The three questions map directly onto the chapter's three arguments: what the group is structurally for (1-1), whether its covenant is explicit (1-3), and whether its size is working for or against real participation (1-3).
  • A one-page diagnosis with one concrete next step is more useful than a longer document that surveys everything that could be improved.
  • Grounding at least one part of the diagnosis in a specific text from this chapter keeps the exercise anchored to what was actually argued, not to general good intentions.

One-sentence summary: Diagnosing your own group against the three questions this chapter raised — what it's actually for, whether its covenant is explicit, and whether its size is working — turns three abstract arguments into one concrete, one-page next step.

Terms to remember: none new — this lecture applies the terms introduced in 1-1 through 1-3.

Carry forward to Chapter 2: this chapter asked what a small group is for and protected that purpose with a covenant and a size ceiling. Chapter 2 assumes a group that knows what it's for and turns to a more concrete question: how do you actually design a single 90-minute gathering so that it serves that purpose well?

제 2 장 Chapter 2: Designing a Gathering

  • A gathering is not one undivided block of time; it has five distinct parts — arrival, opening, substantive middle, response, closing — each doing a different job.
  • Nehemiah 8:1-8 shows a gathering with real structure: assembly, a long deliberate reading, a structured response, and a separate explanation phase.
  • An undesigned meeting does not lose time evenly; it predictably borrows from response and closing to feed an already-prepared, momentum-carrying middle.
  • A written time budget for a 90-minute meeting (for example: 5 / 10 / 45 / 20 / 10) turns "we ran out of time" from a mystery into a decision the leader can see and adjust.

One-sentence summary: A small-group meeting has five distinct parts, and without a written time budget the substantive middle will predictably consume the minutes response and closing needed.

Terms to remember: arrival, opening, substantive middle, response, closing, time budget.

Carry forward to 2-2: this lecture named the opening as one of the five parts; the next lecture asks what an opening is actually for, and why an icebreaker chosen for the wrong reason can waste those minutes just as badly as having no plan at all.

  • An icebreaker's real function is lowering the cost of the first sentence someone speaks that night, not entertainment or filler.
  • Romans 15:7's "accept one another, even as Christ also accepted you" describes the theological weight underneath a good opening: acceptance comes first and makes a response possible.
  • A good opening question connects to that night's content; a disconnected question wastes the transition even when it is fun.
  • Reading the room means watching for observable signs — unusual quiet, a mismatch between face and words, a shared external event — and skipping the standard icebreaker when the room needs something else.

One-sentence summary: An icebreaker's job is lowering the cost of a person's first sentence that night, which means choosing a question connected to the content and being willing to skip it entirely when the room needs something else.

Terms to remember: cost of the first sentence, reading the room.

Carry forward to 2-3: this lecture covered how a gathering opens; the next lecture covers the other end of the meeting — how a gathering closes so that the care raised inside it does not evaporate the moment people walk out the door.

  • Ending on time is a form of care for the whole group's lives outside the room, not merely discipline for its own sake — running long by default quietly says the content matters more than the people who committed a set amount of time.
  • Prayer requests belong inside the planned response phase of the meeting, not squeezed into closing minutes or left to expand into a second, unplanned meeting.
  • Follow-through between meetings is small and repeatable — a text, a call, a shared note — not heroic, but it is what separates a request that was actually carried from one that was only prayed over once and forgotten.
  • Philippians 1:3-4 models ongoing, joyful remembrance of specific people, which is the theological shape follow-through is meant to imitate.

One-sentence summary: Closing a meeting well means ending on time and capturing requests inside the planned response time, and closing the care well means following through with something small — a text, a call, a shared note — before the group meets again.

Terms to remember: follow-through, response phase.

Carry forward to 2-4: this chapter has now covered the anatomy of a meeting, its opening, and its close. The Practice Lab asks you to put all three into a single, real session plan.

  • A session plan is only useful once it has real minutes attached to every part of the anatomy from 2-1, not a general sense of how the night should go.
  • The opening question should be written out in full and checked against 2-2's two tests before the session happens, not improvised in the room.
  • The follow-through mechanism from 2-3 should be decided in advance, even before you know the specific requests that will come up.
  • Naming the single point most likely to run over, and deciding in advance what you will actually do about it, is what lets a plan survive contact with a real group.

One-sentence summary: A real session plan assigns actual minutes to all five parts of the meeting, writes out the opening question and follow-through method in advance, and names in advance the one point most likely to run over.

Terms to remember: session plan, named risk.

Carry forward to Chapter 3: this chapter covered how a meeting is designed before it happens. The next chapter turns to what happens once people are actually talking — how a leader asks questions that open discussion instead of closing it down.

제 3 장 Chapter 3: Facilitating Discussion

  • A closed question asks for a fact or yes/no; a leading question hides its answer inside the wording; a falsely open question sounds open but the leader is fishing for one predetermined answer; a genuinely open question invites real variation and the leader means it.
  • Proverbs 20:5 pictures real thought as "deep water" that has to be drawn out, not supplied — the leader's question is the tool that does the drawing.
  • Sequencing observation before interpretation ("what do you notice" before "what does it mean") keeps a question open rather than letting it collapse into the leader's pre-written conclusion.
  • Malcolm Knowles' andragogy holds that adult learners bring real experience and resist being treated as passive recipients, which is why closed, lecture-style teaching underserves them in particular.
  • A meeting run mostly on closed and leading questions is, functionally, a lecture with extra steps, not a discussion.

One-sentence summary: The leader's tool is a genuinely open question that draws out a group member's own thinking rather than a closed or leading question that only asks them to recite or agree with the leader's.

Terms to remember: open question, closed question, leading question, falsely open question, andragogy.

Carry forward to 3-2: this lecture assumed the group will actually answer once asked well. The next lecture deals with what happens when, even after a good question, nobody speaks.

  • A leader who reflexively fills silence trains the group to wait rather than think, because the group learns speaking is optional as long as someone else eventually fills the gap.
  • James 1:19's order — "swift to hear, slow to speak" — describes the discipline a leader has to model first, not only ask of others.
  • Concrete techniques (counting to ten, a relaxed rather than fixed gaze, naming the pause as safe, repeating rather than rephrasing) make holding silence practicable rather than merely understood in theory.
  • Drawing out a quiet member works best through advance invitation or lower-stakes structures like turn-and-talk, not by calling on them cold in front of the group.
  • Pentecostal/charismatic and cessationist or liturgical traditions read the same silence differently — one listening for a spontaneous prompting, the other simply making room for members' own thoughts — and a leader should know honestly which is operating in their own group.

One-sentence summary: Silence after a real question is usually a sign of thinking, not failure, and a leader who learns to hold it — including for a member who has never spoken — trains a group to think for itself rather than to wait for rescue.

Terms to remember: filling silence, drawing out, turn-and-talk.

Carry forward to 3-3: this lecture dealt with too little talking. The next lecture deals with the opposite problem — one person, or one tangent, taking over the room.

  • A dominant talker is usually driven by enthusiasm, discomfort with silence, an old unchallenged habit, or occasionally a need to be right — not by a wish to dominate, and the leader's approach should assume the more common, more sympathetic reasons first.
  • Proverbs 18:13 names "giving answer before hearing" as folly, a correctable habit, which frames the leader's response as correction rather than condemnation.
  • Acknowledge-then-redirect ("That's a great point — let's hear from a couple of others") preserves the relationship while still opening the floor.
  • A tangent is worth a brief pause if it clarifies the actual topic; once it has replaced the topic, a short, warm redirect back to the evening's purpose is the better tool than an abrupt cutoff.
  • A pattern that persists after repeated in-room redirection, or that is visibly discouraging other members from speaking, needs a private conversation rather than another public correction.

One-sentence summary: A dominant talker or a runaway tangent is best handled by naming the pattern honestly to yourself, redirecting warmly in the moment, and moving to a private conversation only when the in-room techniques have genuinely been tried and have not worked.

Terms to remember: acknowledge-then-redirect, tangent, private conversation.

Carry forward to 3-4: the Practice Lab in this chapter asks you to put 3-1 through 3-3 to work directly — rewriting bad questions and planning your own silence-and-redirection moves for a group you actually know.

  • A bad discussion question can nearly always be rewritten by asking what is there before asking what it means, and by checking whether more than one honest answer is genuinely possible.
  • A written, specific plan — made in advance, for your real group — is more reliable under pressure than good intentions formed in the moment.
  • The threshold for moving a pattern from "handle it in the room" to "needs a private conversation" should be decided ahead of time, not improvised when frustration is already high.
  • This lab is a starting model to reuse, not a claim that every group dynamics problem has now been solved.

One-sentence summary: This lab turns the vocabulary and techniques of 3-1 through 3-3 into a rewritten set of questions and a written, personal plan for silence and redirection that you can actually carry into your next meeting.

Terms to remember: (review) open question, holding silence, acknowledge-then-redirect.

Carry forward to Chapter 4: this chapter dealt with how a leader asks and manages a conversation. Chapter 4 turns to what the group is actually reading together, and how to lead people to see a text rather than simply announcing what it means.

제 4 장 Chapter 4: Reading Scripture Together

  • The inductive method asks three questions in a fixed order: observation (what is there), interpretation (what did it mean), application (what does it call for now).
  • The order matters because each stage constrains the next — interpretation without observation is speculation, and application without interpretation is advice using the text as decoration.
  • Concrete observation questions ask about repeated words, speaker and audience, comparisons and context — not yet about meaning.
  • 2 Timothy 2:15 ties diligent, careful handling of Scripture to not being ashamed as a workman; careless handling is treated as a real failure, not a stylistic preference.
  • Acts 17:11 commends the Bereans for examining Scripture even against an apostle's own teaching — checking is not disrespect.
  • Skipping straight to application tends to produce moralizing: true-sounding conclusions that were not actually derived from the passage in front of the group.

One-sentence summary: The inductive method — observation, then interpretation, then application, in that order — keeps a small-group Bible discussion anchored in what the text actually says, rather than sliding straight to a conclusion the group already believed before they opened their Bibles.

Terms to remember: inductive method, observation, interpretation, application.

Carry forward to 4-2: this lecture established the sequence a leader needs to run before the meeting. The next lecture asks how a leader who has done that work delivers it in the room — as a question that leads people to see it, not an announcement of what was found.

  • Real preparation — context, cross-references, at least one commentary on anything genuinely obscure — has to happen before the meeting; this lecture does not treat that as optional.
  • The distinction that matters is not how much the leader knows, but whether the group is handed the conclusion (announcing) or invited to observe the details that support it (leading people to see it).
  • Announcing is sometimes the right call — for details a group could not reasonably infer — but becomes a failure mode when it is the default for everything, including what the group could find themselves.
  • Nehemiah 8:8 models the goal (real understanding, not just hearing) more than the method; its scene is public explanation to a community that had lost the language of its own Scripture, not small-group facilitation.
  • Under-preparing produces shallow discussion because the leader has nothing sharper to ask; over-preparing delivered as lecture teaches the group to wait for the leader's answer instead of looking themselves.

One-sentence summary: A leader still has to prepare seriously before the meeting, but the test of that preparation is whether it turns into questions that let the group find the passage's weight themselves, rather than a conclusion handed to them ready-made.

Terms to remember: announcing versus leading people to see it.

Carry forward to 4-3: this lecture assumed the leader's preparation succeeds in finding what a passage means. The next lecture asks what to do when it does not — when preparation runs out and a hard question is still standing in the room.

  • Hard questions tend to take one of three shapes: a disturbing Old Testament narrative, a disputed Pauline passage, or a translation difficulty — and each calls for a different kind of preparation.
  • Preparation reduces how often a leader is caught unprepared; it does not eliminate the possibility, and treating total coverage as achievable turns the first uncovered question into a crisis.
  • "I don't know, let's find out," said calmly and followed through on, models the inductive posture under real uncertainty and tends to build credibility rather than cost it.
  • Deuteronomy 29:29 distinguishes what is revealed (owed obedience) from what remains secret (not owed a resolved answer) — a leader is not obligated to have settled every genuinely disputed question.
  • What actually erodes a group's trust is refusing to engage a hard question at all, or manufacturing confidence that later turns out to be wrong — not admitting uncertainty itself.

One-sentence summary: A hard or disputed text is not a leader's failure to prevent; naming honestly what is uncertain, distinguishing it from what preparation could still resolve, and following through on "let's find out" builds more trust than a confident answer that turns out to be wrong.

Terms to remember: disputed Pauline passage, translation difficulty, "the secret things belong to Yahweh."

Carry forward to 4-4: this chapter has built the inductive sequence, the discipline of asking rather than announcing, and the honest handling of a hard text. The Practice Lab asks you to put all three to work on a passage you choose yourself.

  • A well-chosen passage for one session has real content and natural boundaries — not too short to say anything, not so long the group cannot sit with it.
  • Observation questions ask only what is in the text; interpretation questions are built on what observation surfaced, not on outside material introduced without explanation.
  • A specific application question names the passage's actual content; a generic one that could attach to any passage is a sign the application was not really derived from this text.
  • Deciding in advance what you will explain directly, versus what you will ask about, is itself part of preparation — not a failure to fully apply the inductive method.
  • This lab is a rehearsal: the actual test is whether you can run this same process, under time pressure, with a real group watching.

One-sentence summary: Building one full inductive study end to end — choosing a passage, writing observation questions before interpretation questions before one specific application question, and planning how to introduce it without announcing the conclusion first — turns this chapter's principles from something you agree with into something you know how to do.

Terms to remember: observation questions, interpretation questions, application question, delivery note.

Carry forward to Chapter 5: this chapter has been about the content of the meeting — the text itself. Chapter 5 turns to what happens around it: prayer, pastoral care, and the parts of leading a group that mostly happen between meetings rather than during them.

제 5 장 Chapter 5: Prayer and Pastoral Care

  • How a group prays is a design decision, not something that should be left to happen by accident; structured formats exist specifically to include members open prayer quietly excludes.
  • A member who will not pray aloud should be included through format changes (paired prayer, written prayer) and a clear standing invitation, never through repeated direct calling-on.
  • Confidentiality needs a concrete, specific statement — what stays in the room by default, and the one category (danger to someone) that leaves regardless — stated once before it is tested, not invented in the moment.
  • James 5:16 commands mutual confession, and traditions disagree about what else has to be true for that command to be rightly practiced: some treat ordinary mutual confession in a small group as the intended application, while Catholic and Orthodox teaching reserves sacramental confession and absolution to a priest, treating the verse as describing a real but distinct mutual practice.
  • A leader should be able to name honestly which reading their own tradition holds, rather than assuming the question is already settled.

One-sentence summary: A small group's prayer life and its confidentiality both need concrete design rather than assumption, and James 5:16's call to mutual confession is read differently across Christian traditions in ways a leader should be able to name fairly rather than resolve by fiat.

Terms to remember: structured prayer, open prayer, confidentiality (as practice, not slogan), sacramental confession, mutual confession.

Carry forward to 5-2: this lecture covered care that happens inside the meeting, in prayer. The next lecture moves outside the meeting entirely — to the much larger amount of care that happens, or fails to happen, between one Tuesday and the next.

  • Absence and a flat "I'm fine" are worth noticing as a change from a person's own baseline, not treated as either automatically alarming or automatically nothing.
  • A written, weekly-checked habit for tracking one-on-one contact catches the quiet member a leader's unaided memory tends to miss.
  • Care and surveillance are distinguished by whether the outreach is triggered by an actual change, how much pressure it carries, and how frequently it repeats regardless of what is observed.
  • Ruth's words to Naomi model committed presence, not a technique for fixing someone's situation — the text is used here as an illustration of that posture, not as an instruction manual for a small-group leader's role.
  • A leader who tries to diagnose every member's problem before staying present will burn out and will likely make disclosure less likely, not more.

One-sentence summary: Most pastoral care in a small group happens between meetings, in noticing a real change from someone's baseline and following up in a way that reads as committed presence rather than surveillance or diagnosis.

Terms to remember: baseline change, follow-up habit, care versus surveillance, committed presence.

Carry forward to 5-3: this lecture assumed the leader's job is to notice and stay present. The next lecture names the point past which staying present is not enough — where a disclosure needs someone with training or authority the leader does not have.

  • Abuse, suicidal ideation, active addiction, and a marriage in acute crisis are categorically different from ordinary struggle and sit past the edge of lay pastoral competence.
  • Howard Clinebell's distinction between supportive, sustaining care and care requiring clinical training gives a leader language for recognizing which kind a given moment calls for.
  • Romans 12:3 cuts two ways: against overestimating one's competence to handle everything, and against using "I'm not qualified" as an excuse to withdraw from care that remains squarely a leader's to give.
  • A referral done well names honestly why it is happening, offers concrete help finding the right resource, and commits to staying present afterward.
  • Deciding in advance who to call turns a crisis into a known next step instead of a logistics problem solved under pressure.

One-sentence summary: A small group leader's most important skill in a genuine crisis is recognizing, before it happens, where their competence ends and a trained referral begins — and having already decided who to call.

Terms to remember: mandated reporting, suicidal ideation, referral, supportive versus clinical care (Clinebell).

Carry forward to 5-4: this lecture named the categories and the posture. The Practice Lab now puts you inside one of these moments and asks you to draft, in advance, exactly what you would say and do.

  • A response plan only becomes real once it exists as actual words you are ready to say, not as a general intention to "handle it carefully."
  • Acknowledging a disclosure, asking a direct safety question, being honest about the real limits of confidentiality, and giving a concrete next step are the four things a good in-the-room response does.
  • What gets documented and what deliberately does not should be a conscious decision, not an afterthought.
  • Reviewing your own draft for self-protective instincts — avoiding discomfort rather than serving the person — is worth doing now, in a low-stakes moment, rather than for the first time during a real disclosure.

One-sentence summary: Drafting, in advance and in your own exact words, what you would say and do during a serious disclosure turns Chapter 5's principles into something you can actually use under pressure.

Terms to remember: safety question, honest confidentiality limit, concrete next step, documentation boundary.

Carry forward to Chapter 6: this chapter has been about care between meetings and the edge of a leader's competence with an individual. Chapter 6 turns to a different kind of difficulty — conflict between members, inside the group itself.

제 6 장 Chapter 6: Conflict and Difficult Group Dynamics

  • Small-group conflict falls into recognizable categories: theological disagreement gone personal, outside offense spilling in, and values clashes over how the group runs — and each needs a different scale of response.
  • Matthew 18:15-17 establishes an escalation logic — private first, then with a witness, then before the wider body — that applies more broadly than its original scope of personal sin.
  • Outside offense that predates the group is usually not the group's conflict to resolve; it needs private conversations with each person, not group mediation.
  • Values clashes about the group's own purpose are usually appropriate to name inside the group itself, calmly and as a shared question.
  • An unaddressed conflict, not an addressed one, is what actually erodes a small group over time — usually through quiet attrition rather than a dramatic ending.

One-sentence summary: Small-group conflict is not one problem but several — theological disagreement gone personal, outside history spilling in, and values clashes over the group's own purpose — and Matthew 18:15-17's private-first escalation logic helps a leader match the response to the kind.

Terms to remember: theological disagreement gone personal, outside offense spilling in, values clash, escalation logic.

Carry forward to 6-2: this lecture sorted conflicts by kind. The next lecture looks specifically at the personalities that generate recurring friction — the critic, the one who has to win, the over-discloser — and asks what need is actually driving each pattern before asking what to do about it.

  • A behavior pattern is not the same as a person's whole character; naming the likely underlying need changes how a leader responds to it.
  • The perpetual critic is often still invested in the group and looking for a constructive channel, not simply negative for its own sake.
  • The person who needs to win every theological point is often protecting against a fear that being wrong equals being rejected, not merely proud.
  • The chronic over-discloser may have no other regular room where this kind of sharing is welcome — the response should hold a boundary without humiliating them.
  • Romans 15:1-2 frames bearing with a difficult pattern as active — working toward what builds the person and the group up together — not passive absorption of the cost indefinitely.

One-sentence summary: Difficult personality patterns in a small group usually have a sympathetic underlying need, and naming that need — without excusing the behavior's effect on the group — points toward a response that addresses the person rather than merely suppressing the pattern.

Terms to remember: most sympathetic reading, bounded channel, bearing with.

Carry forward to 6-3: this lecture handled patterns a leader can usually manage inside the relationship. The next lecture asks the harder question: when does a pattern, or a conflict, cross the line into something that needs to go above the lay leader's own head?

  • Most small-group conflict is resolvable through ordinary relationship and time, and handling it does not require special training or authority.
  • Three markers suggest a conflict has outgrown a lay leader's scope: a credible allegation of serious wrongdoing, the leader's own loss of neutrality, and a private conversation tried in good faith more than once without improvement.
  • Galatians 6:1-2 commands gentle restoration but also warns the restorer to watch their own exposure — that warning is itself a signal a leader can use to recognize when a situation has grown beyond them.
  • A good handoff tells the person directly that outside help is being brought in and why, rather than letting them discover it after the fact.
  • Escalation changes who carries primary responsibility for the substantive issue; it does not mean the lay leader disappears from the person's life.

One-sentence summary: A lay leader can carry most ordinary conflict alone, but a credible serious allegation, the leader's own loss of neutrality, or a repeated failed private attempt are markers to bring in a co-leader or staff — done by telling the person directly, and without the leader disappearing from their life afterward.

Terms to remember: escalation markers, restorer's exposure (Galatians 6:1), handoff, escalation versus abandonment.

Carry forward to 6-4: this lecture named when and how to escalate in principle. The Practice Lab puts it to the test with a live, escalating scenario you have to reason through in real time.

  • Diagnosing a conflict in real time, without hindsight, is a different and harder skill than analyzing one afterward.
  • The same conflict can shift categories as new information arrives — what looks like a values or theological clash in the room can turn out to have an outside-history component underneath it.
  • Escalation markers from 6-3 should be applied concretely to a specific situation, not just recited in the abstract.
  • A handoff to a co-leader or staff still requires telling the people involved directly, in words the leader has actually thought through in advance.
  • Reasonable leaders can diagnose the same scenario differently; what matters is that the reasoning uses the chapter's framework rather than instinct alone.

One-sentence summary: This lab applies the whole chapter — conflict categories, sympathetic readings, and escalation markers — to a single unfolding scenario, practicing the harder skill of diagnosing a live conflict rather than one already resolved.

Terms to remember: live diagnosis, category shift, escalation in real time.

Carry forward to Chapter 7: this chapter dealt with conflict as something a leader manages. The next chapter asks what happens when a group succeeds well enough, long enough, to need to produce its own next leader.

제 7 장 Chapter 7: Multiplying Leadership

  • A small group's dependence on one irreplaceable leader is a structural weakness, not a sign of strong leadership — and apprenticing a co-leader is the direct fix, made early rather than in a scramble.
  • 2 Timothy 2:2 describes a chain of at least four links (Paul, Timothy, faithful men, others), which reframes the goal from "train my replacement" to "train someone who will also train someone."
  • Character (keeping confidences, following through, treating people well unwatched) and teachability (receiving correction without defensiveness) are better predictors of a good co-leader than charisma, though the two are not mutually exclusive.
  • Robert Coleman's account of Jesus's disproportionate investment in a small number of disciples illustrates, without being identical to, the multiplication logic behind apprenticing rather than doing everything yourself.
  • A real piece of the meeting handed over early, plus a stated timeline in months rather than "someday," turns an intention into an actual apprenticeship with checkpoints.

One-sentence summary: Apprenticing a co-leader — chosen for character and teachability, given a real piece of the meeting early, and developed on a stated timeline — is how a group stops depending on one irreplaceable leader, and 2 Timothy 2:2's four-link chain shows the goal is a leader who will also produce a leader, not just a successor.

Terms to remember: apprenticeship, chain of transmission, teachability.

Carry forward to 7-2: apprenticing a future leader raises the next question directly — what happens once there are, in effect, two leaders and a group that has outgrown its size? The next lecture distinguishes the healthy reasons to split a group from the unhealthy ones.

  • A healthy split requires two markers together: the group has genuinely outgrown a workable size, and a specific prepared person is being sent out with real multiplication intent — not just relief from overcrowding.
  • An unhealthy split can look identical on paper to a healthy one; the tell is usually in what is actually driving it and how it was sequenced relative to any unresolved conflict.
  • Conflict-avoidance splits relocate an unaddressed tension into two rooms instead of resolving it; numeric-pressure splits serve a report rather than the group's actual capacity or readiness.
  • Numbers 11:16-17 shows Moses's burden distributed to seventy prepared elders in advance of collapse, illustrating division driven by genuine, named capacity limits rather than external pressure.
  • 1 Corinthians 1:11-13 shows a division driven by loyalty to persons rather than mission — Paul's rebuke targets that substitution, not the existence of disagreement or difference as such.

One-sentence summary: A split is healthy only when real growth past a workable size and genuine multiplication intent are both present and prepared for in advance (Numbers 11:16-17), and unhealthy when it actually serves conflict avoidance or an outside numeric target while dressed in the language of multiplication, the way Corinth's factions substituted personal loyalty for shared mission (1 Corinthians 1:11-13).

Terms to remember: multiplication intent, conflict-avoidance split, numeric-growth pressure.

Carry forward to 7-3: whether a group splits by healthy design or a leader simply moves on, someone is leaving a room they have shared with others for months or years. The next lecture asks how to close that chapter well, so it reads as sending rather than abandonment.

  • Acts 20:36-38 shows closure enacted, not just announced: a shared physical act, open grief, direct naming of the loss, and an extended goodbye.
  • William Bridges' distinction between a change (a single external event) and a transition (an internal process that takes time and reliably needs an ending) explains why announcing news well is not the same as providing closure.
  • Concrete closure practices — naming the loss specifically, marking a last gathering, allowing grief without rushing to reframe it, and extending the goodbye — are what turn a well-communicated change into an actual ending.
  • A departure can read as abandonment even when it was explained clearly and well in advance, if none of these practices happen; good communication about reasons is not a substitute for closure.
  • Skipping the transition does not make it unnecessary; it tends to surface later, less visibly, often as quiet disengagement rather than acknowledged grief.

One-sentence summary: Sending someone off well requires marking the ending on purpose — naming the loss, holding a last gathering, allowing grief, and extending the goodbye, the way Acts 20:36-38 shows Paul and the Ephesian elders doing — because a clearly communicated change is not the same as a completed transition, and skipping the transition tends to surface later as quiet disengagement rather than disappearing.

Terms to remember: change versus transition, closure practices.

Carry forward to 7-4: the Practice Lab asks you to bring 7-1 through 7-3 together into a single concrete plan — apprenticing a specific person, over a specific timeline, toward a specific and well-marked handoff.

  • A 90-day apprenticeship plan is a first phase, not a full handoff — concrete enough to start next week rather than an open-ended intention.
  • Naming the apprentice honestly against the character-and-teachability filter from 7-1, rather than defaulting to the most charismatic person in the room, is the exercise's first and most important check.
  • A sequence of three or more specific, ordered pieces of the meeting, each with a stated approximate timing, turns "someday" into an actual plan with checkpoints.
  • Observable readiness signs — something you could point to and explain afterward — are what let a leader assess progress without relying on vague impressions.
  • Even a 90-day partial handoff benefits from one explicit transition-marking practice drawn from 7-3, scaled down from a full farewell to a moment named out loud.

One-sentence summary: This Practice Lab turns the chapter's three arguments — choose for character and teachability, hand off real pieces early on a stated timeline, and mark transitions rather than letting them pass unnamed — into a concrete 90-day plan for one actual or realistic person, with observable signs of readiness at each step.

Terms to remember: first-phase plan, observable readiness sign.

Carry forward: this Practice Lab closes Chapter 7 and, with it, the course's progression from what a group is for, through designing and facilitating it, reading Scripture together, caring for members, handling conflict, and finally multiplying leadership so the group's usefulness is not capped by any one person's calendar.