무료

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

LM403E Building a Ministry Team

Lecture 1-3: The Difference Between a Group and a Team

카드로 보기 (3분)
목차 41
LM403E Building a Ministry Team
제 0 장 · Introduction: Why a Team, Not Just Yourself
  1. Introduction: Why a Team, Not Just Yourself
제 1 장 · Week 1: What a Team Is
  1. Lecture 1-1: Why a Team, Not Just You Alone
  2. Lecture 1-2: Biblical Teams
  3. Lecture 1-3: The Difference Between a Group and a Team
  4. Lecture 1-4: Where Is Our Team Right Now?
  5. Lecture 1-5: In My Own Seat, Mapping Our Team's Current State
제 2 장 · Week 2: Gathering People
  1. Lecture 2-1: The Weight of the Ask
  2. Lecture 2-2: An Eye for Gifting
  3. Lecture 2-3: Come and See
  4. Lecture 2-4: The Sad Walk Away
  5. Lecture 2-5: In My Own Seat, Needs List and Candidate List
제 3 장 · Week 3: Building Roles and Structure
  1. Lecture 3-1: Putting a Role in Writing
  2. Lecture 3-2: Who Decides What
  3. Lecture 3-3: The Structure of a Small Team
  4. Lecture 3-4: Preventing Double-Duty and Overload
  5. Lecture 3-5: In My Own Seat, Writing a Role Description
제 4 장 · Week 4: Onboarding and Training
  1. Lecture 4-1: The First Ninety Days Decide Everything
  2. Lecture 4-2: What to Teach, and What to Let Them Experience
  3. Lecture 4-3: Pairing People Up — Mentoring and Accompaniment
  4. Lecture 4-4: The Risk of Responsibility Without Training
  5. Lecture 4-5: In My Own Seat, Building the First Ninety Days
제 5 장 · Week 5: Team Culture and Meetings
  1. Lecture 5-1: Culture Is Not a Vibe, It Is a Set of Repeated Practices
  2. Lecture 5-2: A Meeting That Builds a Team, Not Just an Agenda
  3. Lecture 5-3: Naming Gratitude Specifically and Often
  4. Lecture 5-4: Deciding On Purpose How News Actually Travels
  5. Lecture 5-5: In My Own Seat, Redesigning Our Team's Meetings
제 6 장 · Week 6: Conflict and Performance
  1. Lecture 6-1: A Different Kind of Conflict
  2. Lecture 6-2: When Contributions Differ
  3. Lecture 6-3: Naming What Isn't Working
  4. Lecture 6-4: When Someone Needs to Leave the Team
  5. Lecture 6-5: In My Own Seat, Preparing a Hard Conversation
제 7 장 · Week 7: Team Crisis
  1. Lecture 7-1: When Burnout Spreads Through the Whole Team
  2. Lecture 7-2: Factions and Taking Sides
  3. Lecture 7-3: When the Leader Is the Problem
  4. Lecture 7-4: How to Recover After a Team Breaks
  5. Lecture 7-5: Boundary Rules and Crisis Response Procedure
제 8 장 · Week 8: Lasting and Succession
  1. Lecture 8-1: What Long-Lasting Teams Have in Common
  2. Lecture 8-2: Rotation and Rest
  3. Lecture 8-3: Team Leader Succession
  4. Lecture 8-4: Raising Up the Next Generation of Leaders
  5. Lecture 8-5: The Sending — A One-Year Team Plan and Handover Notes

핵심만 먼저 보기 ↓

12분

Nehemiah 3 is one of the least-read chapters in a widely-read book, and it is easy to see why: it is, on the surface, a list. Name after name, family after family, each one assigned a section of wall to repair. No drama, no dialogue, no speeches. It reads like an inventory.

Read it as a description of how a team actually gets built, and it becomes one of the most concrete pictures of team structure in the whole Bible. Every entry follows something close to a formula: a specific person or family, building a specific, named section, often located precisely relative to something else — "next to him," "across from his own house." And the chapter's significance is not the list itself but what the list adds up to: Nehemiah 6:15 records that the wall was finished — one connected, functioning structure, built by dozens of separate hands working separate, specific sections. This lecture uses Nehemiah 3 and 6:15 together to define, precisely, what actually distinguishes a team from a group of people doing similar work near each other.

이 12분으로 얻는 것

  • Describe the specific pattern Nehemiah 3 repeats for each name or family listed, and explain what that pattern reveals about role clarity.
  • Explain why Nehemiah 6:15's completed wall is the chapter's real point, not merely a historical footnote to the list in chapter 3.
  • State, in one sentence, the actual difference between a group and a team, using Nehemiah 3 as your evidence.
  • Apply that definition to a real example from your own ministry context, identifying whether it currently functions as a group or a team.

Then Eliashib the high priest rose up with his brothers the priests, and they built the sheep gate; they sanctified it, and set up its doors... Next to him built the men of Jericho. Next to them built Zaccur the son of Imri... Next to them, Jedaiah the son of Harumaph made repairs across from his house. Next to him, Hattush the son of Hashabneiah made repairs." — Nehemiah 3:1-2, 10

World English Bible

So the wall was finished in the twenty-fifth day of Elul, in fifty-two days." — Nehemiah 6:15

WEB

Notice what Nehemiah 3 gives, and what it withholds. It gives a name, or a family, or a group ("the men of Jericho") for nearly every section. It gives a specific location — often relative to a landmark, or, in Jedaiah's case, precisely "across from his own house." What it withholds is any sense that these builders worked in the same place, doing the same task, interchangeably. Each entry is distinct: a specific person, a specific section, adjoining specific neighbors on either side. And Nehemiah 6:15's single sentence — the wall was finished, in fifty-two days — is the payoff the entire list has been building toward. Dozens of separate, specific assignments produced one connected, finished structure that none of them could have built alone.

1. What Nehemiah 3 actually records

It would be easy to read Nehemiah 3 as simply a long list of names doing "wall repair" — a group of similar volunteers assigned to a similar task. Read closely, the chapter records something considerably more specific. Eliashib the high priest and his brother priests build the sheep gate specifically, and sanctify it. The men of Jericho build next to him. Zaccur son of Imri builds next to them. Jedaiah son of Harumaph makes repairs "across from his own house" — a detail specific enough to place him at a particular point on the wall, not simply somewhere in the general vicinity. Nehemiah 3:28's later detail, that a group of priests each worked "across from his own house," makes the same point even more sharply: specificity down to the individual level, not a general assignment to a general area.

This is not "everyone did some wall repair." It is dozens of named, distinct, non-interchangeable assignments, each occupying a specific, adjoining section, each connected to the sections on either side of it.

2. The connection is the point, not the list

If Nehemiah 3 ended without a payoff, it would be an impressive administrative record and nothing more — evidence of organization, but not evidence of a team in any meaningful sense. Nehemiah 6:15 is the sentence that makes chapter 3 mean something: "the wall was finished." Not "the sections were finished" — the wall, one connected structure, was finished. Eliashib's sanctified gate connects to the men of Jericho's section, which connects to Zaccur's, which eventually connects, all the way around, back to itself. No individual builder built the wall. Every individual builder's section was necessary to the wall existing at all, and none of their sections, alone, was the wall.

What a team is

This is the exact structure this chapter has been building toward as a definition: a team is not a group of people doing similar tasks near each other. A team is a set of distinct, specific, interdependent contributions that connect into one shared, checkable goal — a goal none of the individual contributors could reach alone, and that genuinely fails if any one contributor's section is left undone.

3. Applying the definition: group or team?

Consider two ministries that look identical from a distance. In the first, five people take turns running the sound board on a rotating schedule — whoever is assigned that week runs it, alone, exactly as the others would. There is no adjoining section, no one whose contribution depends on what the sound person specifically did differently from another sound person. This is a group: five interchangeable people sharing one task in sequence.

In the second, a Sunday morning hospitality team has one person greeting at the door, one running the coffee station, one seating late arrivals discreetly, and one following up during the week with first-time visitors whose names the greeter collected. Remove the greeter, and the follow-up person has no names to call. Remove the coffee person, and the greeter is fielding coffee complaints instead of greeting. Each section is specific, adjoining, and necessary — and the whole only works, like Nehemiah's wall, if every section is actually built. This is a team, by the definition this lecture has argued for: not people doing similar work in proximity, but distinct, interdependent contributions united by one shared, checkable goal.

The test this lecture leaves you with is not "does everyone have a job" — every group has that. The test is Nehemiah's: is each contribution specific and distinct, does it adjoin and depend on the contributions next to it, and does the whole thing produce one finished wall that would visibly fail if any one section were left undone?


Diagram 1. Nehemiah 3's pattern, and the group-versus-team test it yields

One Wall, Many Sections Nehemiah 3's repeated pattern Eliashib sheep gate sanctified it Men of Jericho next section Zaccur next section Jedaiah "across from his own house" ... and so on, all the way around the wall ... Nehemiah 6:15 — "the wall was finished" — one structure, from many specific sections A group Interchangeable people doing the same task, independently of each other. Remove one: task continues. A team Distinct, adjoining sections that depend on each other, united by one shared goal. Remove one: the wall gaps.

핵심 요약

  • Nehemiah 3 repeats a specific pattern: a named person or family assigned a specific, located section, adjoining specific neighbors — not a general assignment to a general task.
  • Nehemiah 6:15's "the wall was finished" is the chapter's real point: dozens of distinct sections produced one connected structure that none of them could have built alone.
  • The actual test for a team, drawn from Nehemiah 3: is each contribution specific and distinct, does it depend on the contributions adjoining it, and does the whole produce one shared, checkable goal that visibly fails if a section is left undone?
  • A group is interchangeable people doing similar tasks independently — remove one, and the task continues unaffected.
  • A team is distinct, adjoining, interdependent contributions — remove one, and the whole structure gaps.
Front Back
Nehemiah 3's pattern Specific person or family, specific located section, adjoining specific neighbors.
Nehemiah 6:15 "The wall was finished" — the payoff the whole list of separate sections was building toward.
The group-vs-team test Distinct and interdependent, uniting into one shared goal that fails if a section is missing — or interchangeable and independent.
The failure test Remove one contributor: a group's task continues; a team's wall gaps.

★ One sentence to remember A team is not people doing similar things near each other — it is distinct, adjoining sections that only add up to one finished wall together.

✓ This week's action Pick one task in your ministry and run the removal test on it: if this one person were gone this week, would the task continue unaffected, or would something visibly gap?

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • Apply this lecture's test to your own ministry: is each person's contribution specific and distinct, or is everyone doing roughly the same interchangeable task?
  • Nehemiah 3:10 places Jedaiah's section "across from his own house." Why might that level of specificity matter more than a general assignment like "help with the wall"?
  • Nehemiah 6:15 records the wall's completion in one sentence, after an entire chapter of individual assignments. What would be lost if chapter 3 existed without that sentence?
  • Think of a ministry task in your church that looks like a team but is actually, by this lecture's test, a group. What would need to change to make the contributions genuinely interdependent?
  • Is there a risk in making every task interdependent — a downside to a team where nothing can proceed if one section is missing? How would you guard against that risk?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.