Lecture 8-1: What Long-Lasting Teams Have in Common
목차 41
- Lecture 1-1: Why a Team, Not Just You Alone
- Lecture 1-2: Biblical Teams
- Lecture 1-3: The Difference Between a Group and a Team
- Lecture 1-4: Where Is Our Team Right Now?
- Lecture 1-5: In My Own Seat, Mapping Our Team's Current State
- Lecture 2-1: The Weight of the Ask
- Lecture 2-2: An Eye for Gifting
- Lecture 2-3: Come and See
- Lecture 2-4: The Sad Walk Away
- Lecture 2-5: In My Own Seat, Needs List and Candidate List
- Lecture 3-1: Putting a Role in Writing
- Lecture 3-2: Who Decides What
- Lecture 3-3: The Structure of a Small Team
- Lecture 3-4: Preventing Double-Duty and Overload
- Lecture 3-5: In My Own Seat, Writing a Role Description
- Lecture 4-1: The First Ninety Days Decide Everything
- Lecture 4-2: What to Teach, and What to Let Them Experience
- Lecture 4-3: Pairing People Up — Mentoring and Accompaniment
- Lecture 4-4: The Risk of Responsibility Without Training
- Lecture 4-5: In My Own Seat, Building the First Ninety Days
- Lecture 5-1: Culture Is Not a Vibe, It Is a Set of Repeated Practices
- Lecture 5-2: A Meeting That Builds a Team, Not Just an Agenda
- Lecture 5-3: Naming Gratitude Specifically and Often
- Lecture 5-4: Deciding On Purpose How News Actually Travels
- Lecture 5-5: In My Own Seat, Redesigning Our Team's Meetings
- Lecture 6-1: A Different Kind of Conflict
- Lecture 6-2: When Contributions Differ
- Lecture 6-3: Naming What Isn't Working
- Lecture 6-4: When Someone Needs to Leave the Team
- Lecture 6-5: In My Own Seat, Preparing a Hard Conversation
- Lecture 7-1: When Burnout Spreads Through the Whole Team
- Lecture 7-2: Factions and Taking Sides
- Lecture 7-3: When the Leader Is the Problem
- Lecture 7-4: How to Recover After a Team Breaks
- Lecture 7-5: Boundary Rules and Crisis Response Procedure
Picture two teams, both healthy today. The first team's health depends entirely on one person — the founding leader who recruited everyone, holds the whole calendar in her head, and quietly fixes whatever breaks before anyone else notices it broke. The second team's health does not depend on any one person continuing, because what that team actually knows — how to run the thing, why it runs that way, what to do when it goes wrong — has already been taught to more than one person, on purpose. Both teams look identical from the outside this Sunday. They are not the same team. Only one of them will still be a team in five years.
This chapter is about the difference, and this lecture starts where the difference actually gets made: not in a crisis, but in an ordinary season, long before anyone is forced to ask what happens if the leader leaves.
이 14분으로 얻는 것
- State 2 Timothy 2:2's multiplication principle in your own words, and explain why it names a chain of transmission rather than a single act of teaching.
- Explain why Psalm 78:4, 6 and Deuteronomy 32:7 treat passing on what a generation knows as a command, not a hope that it will happen naturally.
- Identify one piece of knowledge your own team currently holds only in one person's head.
- Distinguish a team that merely functions well today from a team built to last past its current leader.
The things which you have heard from me among many witnesses, commit the same to faithful men, who will be able to teach others also." — 2 Timothy 2:2
World English Bible
Remember the days of old. Consider the years of many generations. Ask your father, and he will show you; your elders, and they will tell you." — Deuteronomy 32:7
WEB
We will not hide them from their children, telling to the generation to come the praises of Yahweh, his strength, and his wondrous works that he has done... that the generation to come might know, even the children who should be born; who should arise and tell their children." — Psalm 78:4, 6
WEB
Count the links in Paul's sentence to Timothy. Paul taught Timothy — that is one link. Timothy is to commit it to faithful men — a second link. Those faithful men are to be "able to teach others also" — a third link, and the sentence explicitly plans for a fourth generation it does not name, because the chain does not have a stated end. This is not a verse about a good teacher training a good student. It is a verse about building a transmission mechanism sturdy enough to outlast every single person currently in it. Deuteronomy 32:7 and Psalm 78:4, 6 make the same demand at the level of an entire people: what one generation knows about God's faithfulness is not automatically inherited by the next. It has to be told, on purpose, or it is lost — "we will not hide them from their children" is a decision, not a default.
1. Two kinds of health
A team can be healthy in a way that says nothing at all about whether it will last. It can have a full roster, a competent leader, smooth Sundays, and genuine warmth among its members — and still be one departure away from collapse, because every piece of institutional knowledge that keeps it running lives in a single head. Call this fragile health: real, present, and entirely dependent on one person's continued presence.
Durable health
The alternative is not a different level of competence. It is a different structure. Call it durable health: a team where more than one person could explain why things are done a certain way, more than one person could actually run the Sunday if the usual leader were unexpectedly gone, and the knowledge that makes the team work has been deliberately placed in more than one place. A durably healthy team might look, on an ordinary Sunday, exactly like a fragile one. The difference does not show up until the test comes — and by the time the test comes, it is too late to build durability quickly.
This chapter's principle names the actual measure: a team's success is not how well it runs while the founding leader is present. It is whether it still runs well after that leader is gone. Everything else in this chapter — rotation, succession, raising up leaders, the final handover — serves that one measure.
2. The multiplication principle, read carefully
2 Timothy 2:2 is often quoted as a general statement about , which it is, but read at the level of a sentence's actual structure, it says something more specific and more useful for a team leader. Paul does not tell Timothy "teach people well." He tells Timothy to commit what he has heard to people who are, themselves, able to teach others — the qualification is built into the instruction. Paul is not asking for good students. He is asking for a specific kind of good student: one capable of becoming, in turn, a source.
Apply this to a ministry team directly. If you train a new volunteer only to do the task well, you have produced a competent volunteer. If you train a new volunteer to do the task well and to be able to explain and hand off that task to someone else, you have produced something closer to what 2 Timothy 2:2 actually describes — a link that can hold the next link, not just perform the task itself. A team made only of excellent individual performers, none of whom could train a replacement, is one departure away, at every single position, from a gap nobody else can fill.
3. Why this has to be commanded, not hoped for
Deuteronomy 32:7's instruction to "ask your father" and "your elders" and Psalm 78:4, 6's "we will not hide them from their children" share an assumption worth stating plainly: left alone, knowledge does not automatically pass to the next generation. It has to be actively told, actively asked for, actively preserved on purpose against the ordinary tendency of things to be forgotten once the person who knew them is no longer in the room.
A ministry team's institutional knowledge behaves exactly the same way, on a much smaller and faster timescale. Why does the hospitality team set up the coffee station in that specific order? Somebody learned, once, the hard way, that doing it out of order means the coffee is cold when people arrive — and if that reason was never told to anyone else, the next leader will eventually "simplify" the process, lose the reason, and relearn the same hard lesson six months later. Multiply this by every small, hard-won piece of knowledge a team accumulates over years, and the cost of never deliberately transmitting any of it becomes clear: a team that does not tell its own story to its own next generation is condemned to keep relearning it.
4. What this looks like on an ordinary team
None of this requires a formal program. It requires a habit, kept deliberately rather than left to chance:
- When you learn something the hard way, say the reason out loud to at least one other person on the team, not just the fix itself.
- When you make a decision about how something is done, write the one-sentence reason down somewhere more permanent than your own memory.
- Ask, periodically, "if I disappeared this week, who could actually explain why we do it this way?" — and if the honest answer is nobody, that is this chapter's diagnostic question working correctly.
5. A caution against the wrong kind of comfort
It is tempting to hear "build a team that outlasts you" and feel quietly accused, as though wanting to be needed were itself the problem. That is not this lecture's claim. Wanting to matter to a team you have poured years into is not a defect. The defect is treating your own indispensability as evidence of faithfulness rather than as a gap still waiting to be closed. A leader who has trained no one to replace them has not proven their devotion more thoroughly than a leader who has. They have simply left a debt for someone else to discover at the worst possible moment.
Diagram 1. Fragile health versus durable health
핵심 요약
- A team's success is measured by whether it runs well after the founding leader is gone, not by how well it runs while that leader is present.
- 2 Timothy 2:2's multiplication principle asks for people able to teach others, not just people who perform a task well — a chain, not a single handoff.
- Deuteronomy 32:7 and Psalm 78:4, 6 treat passing knowledge to the next generation as a deliberate act, not something that happens by default.
- Fragile health and durable health can look identical on an ordinary Sunday; the difference only shows up under the test of a departure.
- Wanting to matter to a team is not a defect. Treating your own indispensability as proof of faithfulness, instead of a gap still waiting to be closed, is.
| Front | Back |
|---|---|
| Fragile vs. durable health | Both look fine today. Only durable health survives the leader's departure. |
| 2 Timothy 2:2's chain | Paul to Timothy to faithful men to "others also" — a transmission mechanism, not one lesson. |
| Psalm 78:4, 6 | "We will not hide them" — telling the next generation is a decision, not a default. |
| This chapter's measure | Not how well it runs now. Whether it runs well after you are gone. |
★ One sentence to remember A team that has never told its own story to its own next generation is condemned to keep relearning it.
✓ This week's action Tell one other person on your team the reason behind one thing you currently do a certain way — not just the instruction, the reason.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Is your own team's current health closer to "fragile" or "durable" as this lecture defines them? What is the honest evidence either way?
- Name one piece of knowledge — a reason, a fix, a hard-won lesson — that currently lives only in your own head. What would it take to tell it to one other person this month?
- 2 Timothy 2:2 asks Timothy to commit truth to people "able to teach others also." Think of someone on your team who does the task well but has never been asked to explain it to anyone else. What would change if you asked them to?
- Psalm 78:4, 6 frames telling the next generation as something the psalmist actively decides to do ("we will not hide them"), not something that happens automatically. Where in your own leadership have you assumed something would simply carry forward on its own?
- This lecture warns against treating your own indispensability as evidence of faithfulness. Has that temptation ever shown up in your own leadership, even quietly?