Lecture 8-5: The Sending — A One-Year Team Plan and Handover Notes
목차 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
This course opened with a claim that most ministry teams, formed by accident rather than design, never actually get to test: that a team is not a more organized way to do one person's job. It is the only way certain ministry actually gets done at all — because a body with one member is missing organs, not merely running lean — and it is also the only way certain kinds of damage happen, which is exactly why chapter 7 asked you to look plainly at crisis before this course would let you close it. Everything since the introduction — gathering people with real weight, building roles that can actually be held accountable, onboarding well, building a culture that does not happen by itself, handling conflict honestly, surviving a crisis — has been in service of one final test this lecture actually applies: not whether your team runs well today, with you in the room, but whether it would still run well a year from now, and whether it would still run at all if you were not in the room to hold it together.
Today you do not read one more argument. You write two documents: a one-year plan for your team, and a handover note naming what someone else would need to know to lead this team if you left tomorrow. Both are signed and dated. Neither is a promise you cannot revise — chapter 8-3's Moses did not treat succession as a single irreversible event, and neither should you — but a written, dated page survives in a way a private good intention does not.
이 22분으로 얻는 것
- Write a one-year team plan naming three specific goals, one role currently being prepared for succession, and a rotation and rest rhythm for your team.
- Write a signed, dated handover note naming what someone would actually need to know to lead your team if you left tomorrow.
- Explain, in your own words, this course's opening claim about why a team is structurally different from one person's job divided up, and how chapter 8 has turned that claim into a practice.
- Identify the one habit from this course — recruiting with real weight, writing roles down, building deliberate culture, naming conflict plainly, or preparing for succession — you are most likely to let slip once the course itself is over.
Here, moreover, it is required of stewards, that they be found faithful." — 1 Corinthians 4:2
World English Bible
I have fought the good fight. I have finished the course. I have kept the faith." — 2 Timothy 4:7
WEB
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
WEB
1 Corinthians 4:2 names the actual standard a team leader is judged against, and it is worth being precise about what it does not say. It does not say stewards are required to have built something large, or something that never had a hard season, or something that outperformed every comparable team nearby. It says stewards are required to be found faithful — a standard about what was actually done with what was actually entrusted, not a standard about outcomes a leader never fully controlled in the first place. 2 Timothy 4:7's "I have finished the course" is Paul's own accounting at the very end, and notice what it does not claim either: not that the church he built never had conflict, never lost a member, never faced a crisis. Only that the fight was fought, the course was finished, the faith was kept. And 2 Timothy 2:2, returning one final time in this course, is the specific shape faithfulness takes at the level of a team: not holding on to what you built, but committing it to others able, in turn, to carry it further than you did.
1. What eight chapters actually built, in one page
Before writing anything, look back honestly at what this course has actually given you, one line per chapter.
Chapter 1 established that a team is not people doing similar things near each other — it exists only where the parts genuinely need each other, and Scripture treats this as structural, not merely efficient.
Chapter 2 treated recruiting as a real request with real weight, never a slot to fill with whoever happens to say yes.
Chapter 3 insisted an unwritten role is a role nobody, including the person doing it, can actually be held accountable to.
Chapter 4 argued that a new member's first ninety days set a ceiling on how well they will ever do the role, which makes early, close accompaniment worth the real time it costs.
Chapter 5 showed that team culture is never what a team says it values — it is what actually happens by default unless someone deliberately shapes it.
Chapter 6 faced the fact that ministry-team conflict tangles relationship and task together in a way ordinary workplace or family conflict does not, and gave you four ways to work inside that tangle rather than around it.
Chapter 7 named, plainly and without softening, what threatens a team in crisis — burnout, faction, a leader becoming the actual problem — because every crisis it named had a warning sign visible before the crisis arrived.
Chapter 8, this week, has asked what it means to build something that actually lasts: knowledge deliberately transmitted rather than assumed to persist, rest and rotation built by structure rather than left to whoever is too devoted to say no, succession initiated by the leader rather than forced by circumstance, and a next generation actually developed rather than kept as permanent assistants.
2. The claim this course opened with, returned to
Return, one final time, to the introduction's actual argument, because today's plan and handover note only make full sense in light of it.
The introduction refused an easy way of thinking about teams that this course could have quietly assumed without saying so: that a ministry team is fundamentally a management convenience, a way of dividing one big job among several willing hands so that no single person has to carry all of it. The truer claim, running underneath every chapter since, is this: a team is not a divided job. It is a different kind of thing than a job at all. Ecclesiastes 4:9-12 did not argue that two people finish a task faster than one — it argued that two people can do things structurally that one person cannot do at all: lift each other up, share warmth neither can produce alone, withstand what would overcome either one separately. 1 Corinthians 12:12 did not argue that a body works more efficiently with many parts cooperating — it argued that the many parts are the one body's actual identity, so that one person attempting the whole is not a lean, efficient version of ministry. It is an incomplete body, missing organs it was never meant to be missing.
Nothing since the introduction has walked that claim back. Chapter 3's insistence on written roles, chapter 5's deliberate culture, chapter 6's honest conflict, chapter 7's plain-spoken warnings, and chapter 8's rotation, succession, and next-generation leaders — every one of these assumes, and depends on, the fact that this is not one person's job divided into pieces for convenience. It is a body, with its own real identity, that exists only where its distinct parts actually need each other — which is exactly why a body's health cannot be measured only by how it functions while one particular organ is present and working hard. It has to be measured by whether the whole body keeps functioning when any one part, including the leader, is eventually gone. This is why the course closes here rather than on one more principle to apply personally. A team whose health depends entirely on the founding leader's continued presence was never actually functioning as the different kind of thing chapter 1 described. It was one person's job, informally shared, wearing a team's name.
3. Why write it down, and why sign it
You could resolve, quietly, to keep building rotation, keep developing your successor, keep the culture deliberate rather than accidental. Most leaders who finish a course like this one resolve exactly that, in good faith, and most such private resolutions do not survive the first ordinary busy month back in the actual work.
A written, dated plan survives differently, for the same reason this course has already given more than once. Specificity is what a plan can actually be checked against. "I will keep developing leaders" cannot be verified by anyone, six months from now, including you. "I will hand the setup checklist to [a named person] by the end of this month, and check in with them about it on [a specific date]" can be checked by both of you, on that date, honestly.
There is a second reason, and chapter 8-3 has already given you its shape: a plan that stays entirely private is a plan nobody else has witnessed, which means nobody else can hold you to it, and — just as importantly — nobody else has been prepared by watching you make it. A one-year plan and a handover note that at least one other person on your team has seen are not merely more likely to be kept. They are themselves a small act of the deliberate transmission chapter 8-1 already argued for.
4. How to write the one-year team plan: five steps
One: reread this chapter's Key Points, all four lectures. Fifteen minutes. Notice which lecture — lasting knowledge, rotation and rest, succession, or raising up the next generation — you resisted most while reading it; that is usually the one most worth planning around specifically.
Two: choose three specific, checkable goals for your team's next year. Not "keep the team healthy." Something a fellow team member could ask you about eleven months from now and get a clear yes or no: "Build a working monthly rotation for the setup role by [a specific month]." "Write down the reasons behind our three most important recurring decisions, somewhere more permanent than my own memory, by [a specific date]." "Have one honest team-culture conversation, using chapter 5's Acts 2:42-47 pattern, before the year is out."
Three: name one role currently being actively prepared for succession. Not a general hope that "someone will eventually be ready." A specific role, a specific person already being developed toward it, and one concrete thing you will hand them this quarter.
Four: name your team's rotation and rest rhythm. Even a small, imperfect rhythm — two people trading a role monthly, a fixed week each quarter when the usual leader is deliberately off — counts, per lecture 8-2, as real structure rather than an accidental default.
Five: sign and date it, and show it to at least one other person on your team. The same small, weighty act this course has asked of you before, at a smaller scale, in the "In My Own Seat" labs. Use it here, at the largest scale the course offers, one final time.
5. How to write the handover note
Address it honestly, to a specific name if you already know who would take over, or to "whoever leads this team next" if you do not.
Name what they would need to know that is not written down anywhere else. The reason behind a decision that looks arbitrary from the outside. Who to call if a specific kind of problem comes up. What has already been tried and failed, so they do not have to relearn it the hard way chapter 8-1 already warned against.
Name one honest warning specific to this team. A pattern this particular group tends toward, a boundary worth protecting, a form of overload this specific role tends to produce — chapter 7's own honesty, aimed forward rather than backward.
Name one thing worth the cost. Leading this team, across everything this course has named, has cost you something real — time, exposure, the discomfort of conflict named plainly rather than avoided. Tell your successor, honestly, what has made that cost worth carrying.
Sign and date it, and decide, specifically, where it will actually be kept — with a co-leader, a pastor, a specific file — so it is genuinely findable by the person who eventually needs it, not simply written and then lost.
6. A compass, not a cage
Say this plainly, the same way chapter 8-3 said it of Moses' own succession: this plan and this note are a steward's honest accounting for the year ahead, not a vow that fails entirely the moment one part of it does not go as planned. 1 Corinthians 4:2's standard is faithfulness, not flawless execution. You will very likely fall short of at least one of these three goals this year — a season that gets busier than expected, a person being developed who moves away before the investment finishes, a rotation that has to bend for a real emergency. That is not the plan failing. Its purpose is not perfect compliance with a document. Its purpose is a fixed, dated point you return to honestly, to ask what actually happened, and adjust rather than quietly abandon.
7. The last word
It would be easy to end this course with one more principle to remember, one more verse to file away alongside the others from eight chapters. That would undo the actual work this course has been doing, because it would leave you exactly where a stack of good advice always leaves its reader: informed, and unchanged.
So end, instead, where the argument actually lands. The introduction opened by naming what a team is not — a more organized way to divide one job. It closes by asking you to write down, specifically, what it means to have actually built the different thing it claimed a team could be: something that does not merely function today, but is deliberately built to keep functioning, honestly and faithfully, after you are no longer the one holding it together.
"Here, moreover, it is required of stewards, that they be found faithful." — 1 Corinthians 4:2 (WEB)
You are not finished with this question when this course ends. You have been given a plan, and a note, to keep answering it on — for as long as you hold this seat, and then, faithfully, past it.
Diagram 1. The form: my one-year team plan
Diagram 2. The form: handover notes for whoever leads this team next
핵심 요약
- This course closes on succession because it is the introduction's own claim, finally made into a practice: a team is not one person's job divided up, and its health is measured by whether it survives that person's absence.
- Today's plan and handover note gather eight chapters into two signed pages: three checkable goals, one role in active succession prep, a rotation and rest rhythm, and a note naming what a successor would need to know that is not written down anywhere else.
- 1 Corinthians 4:2's standard is faithfulness, not flawless execution or guaranteed outcomes — a steward is judged by what they did with what was entrusted, not by results outside their control.
- The plan is a compass revisited on a fixed date, not a vow kept perfectly or failed entirely — falling short of one goal does not void it.
- Ecclesiastes 4:9-12 and 1 Corinthians 12:12, from the introduction, were never claims about efficiency. They were claims that a team can do, and be, what one person alone structurally cannot — and everything since has depended on taking that claim seriously.
| Front | Back |
|---|---|
| The plan's four parts | Three checkable goals, one role in succession prep, a rotation and rest rhythm, one fixed revisit date — signed and dated. |
| The handover note's three parts | What isn't written elsewhere, one honest warning, one thing worth the cost — signed, addressed even without a name. |
| 1 Corinthians 4:2 | Stewards are required to be found faithful — not to guarantee results. |
| The course's opening claim, closed | A team is not one person's job divided up. Chapter 8's practices are that claim finally lived out. |
★ One sentence to remember A team's success is not how well it runs while you are there. It is whether it still runs well after you are gone — and that is a thing you can actually build toward, starting today.
✓ Action for this week Tell the person named in your succession-prep goal, this week, that you are developing them on purpose, and put your plan's revisit date in your calendar before the day ends.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Of the three goals in your plan, which one do you expect to be hardest to keep, and why did you choose it anyway?
- This course opened by claiming a team is not one person's job divided up, but a genuinely different kind of thing. After eight weeks, do you believe that more, less, or the same as when you started?
- Who is the person named in your succession-prep goal, and have you actually told them yet that you are developing them — not just decided it privately?
- Looking back over all eight chapters, which single lecture changed something concrete in how you actually lead your team, not just how you think about leading it?
- If your handover note is addressed to "whoever leads this team next" rather than a name, what does it feel like to write something this honest to someone you cannot yet picture?