Lecture 4-5: In My Own Seat, Building the First Ninety Days
목차 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
Four lectures have made claims about what forms a new team member well: sustained presence rather than a single briefing, instruction paired with real unprotected practice, an established person willing to vouch for and accompany them, and a pace that respects how long character and skill actually take to test. This lecture asks you to stop reflecting on those claims and build something with them: an actual onboarding checklist, for one actual role on your team, covering the first week, the first month, and the first ninety days.
The task is small and concrete. Not a discussion question. A form to fill in, for a real role, with real names attached wherever you can put them.
이 17분으로 얻는 것
- Build a first-week plan that gives a new team member sustained presence near the real work, not only orientation content, drawing on lecture 4-1.
- Build a first-month plan that pairs clear instruction with real, appropriately scaled practice, and names a specific mentor who will accompany the new person the way Barnabas accompanied Saul, drawing on lectures 4-2 and 4-3.
- Build a first-ninety-days review that honestly assesses whether responsibility has been extended at a pace character and skill can actually support, drawing on lecture 4-4.
- Explain why Numbers 11:28's image of formation through sustained proximity, not a single orientation session, should shape how you read your own completed checklist.
Joshua the son of Nun, the servant of Moses, one of his chosen men, answered, 'My lord Moses, forbid them!'" — Numbers 11:28
World English Bible
As you go, preach, saying, 'The Kingdom of Heaven is at hand!' Heal the sick, cleanse the lepers, and cast out demons. Freely you received, so freely give." — Matthew 10:7-8
WEB
Barnabas went out to Tarsus to look for Saul. When he had found him, he brought him to Antioch. For a whole year they were gathered together with the assembly, and taught many people." — Acts 11:25-26
WEB
not a new convert, lest being puffed up he fall into the same condemnation as the devil." — 1 Timothy 3:6
WEB
These four verses are this chapter's whole argument compressed. Numbers 11:28 is the fruit of years of proximity, not a single lesson — a reminder that whatever you build below has to actually sustain itself past a first week if it is to produce anything like what it produced in Joshua. Matthew 10:7-8 is the model for what belongs in the checklist as explicit instruction, stated clearly before responsibility begins. Acts 11:25-26 is the model for what belongs in it as an actual, named, returning mentor relationship, not a box checked once. And 1 Timothy 3:6 is the check against moving faster than a real person's actual formation can support, whatever the calendar says the timeline should be.
Why this comes at the end of the chapter, not the start
The temptation, faced with a checklist assignment, is to fill it in generically — orientation on day one, a buddy assigned in week one, a review meeting at some point down the line — the same shape any competent HR department would produce without ever having read Exodus 18, Matthew 10, Acts 9 and 11, or 1 Timothy 3. That is not what this lab is asking for. Each section of the form below is tied to a specific principle from the four lectures that preceded it, and filling it in honestly means checking each answer against the passage it is drawn from, not simply against what sounds thorough.
What usually goes wrong when leaders skip this
Three patterns are worth naming before you begin.
Treating the first week as pure information transfer. A new team member sits through an orientation, receives a handbook, meets a few names, and is then largely left to figure out the actual rhythm of the role alone. This looks efficient and looks complete on paper. Lecture 4-1 argues it builds a lower ceiling than sustained presence does — Joshua was not oriented, he was present, repeatedly, near the actual work.
Naming a mentor without specifying what the mentor actually does. A checklist item that reads "assign a mentor" is easy to check off and easy to leave meaningless. Lecture 4-3 showed that what made Barnabas's mentoring real was specific, visible action — vouching publicly, returning to Tarsus, working alongside Saul for a full year — not simply being listed as available if needed.
Handing over full responsibility on a fixed schedule regardless of what has actually been observed. A ninety-day mark is a useful checkpoint, but if a leader treats it as an automatic promotion date rather than an honest review of what has actually been tested and shown, lecture 4-4's warning applies directly: responsibility extended ahead of demonstrated character and skill risks pride in the new person and exposure for the whole team.
How to fill in the form
Use the form in section 4-1, built around one actual, current or upcoming role on your team — not a hypothetical role, and not every role at once.
Step 1 — First week. Name the specific orientation content this person needs (drawing on Matthew 10:7-8's model of clear instruction given before responsibility begins), and, separately, name at least one way they will simply be present near the real work happening that week, the way Joshua was present at the mountain and the Tent, not merely told about it.
Step 2 — First month. Name the specific mentor who will accompany this person, and describe, concretely, what that mentor will actually do — not "check in occasionally," but a specific, recurring action modeled on Barnabas: vouching for the new person to others, working alongside them on a real task, being visibly present with them more than once.
Step 3 — First ninety days. Name what real, appropriately scaled responsibility this person will be given during this window, matched to what they have already been taught and have already been observed doing well — not the full weight of the role on day one, and not indefinite observation with no real responsibility ever extended.
Step 4 — The ninety-day review. Write down, in advance, the honest questions you will ask at the ninety-day mark: what has actually been tested and shown, not merely what time has passed. Use 1 Timothy 3:6-7 as your check — is there now a track record, visible enough to justify what comes next, or is the calendar doing work that actual observation has not yet earned?
What usually goes wrong while filling it in
"I can't think of anything specific for the mentor to actually do." If this happens, it is a useful finding, not a failure of the exercise — it usually means no specific person has actually been asked to play this role yet, only assumed to be available in general. Naming the gap plainly is more useful than filling the box with something vague to complete the form.
"Ninety days feels too slow for how badly we need this role filled." This pressure is real and worth naming honestly rather than pretending it does not exist. But note what 1 Timothy 3:6-7 actually warns against: not caution itself, but responsibility extended faster than character and skill have been tested. If your team's need is urgent enough to compress this timeline, name explicitly what you are choosing to risk by doing so, rather than compressing it silently and discovering the cost later.
"This role has never had anyone dedicated to actually accompanying a new person into it before." This is common, and worth treating as the most important finding this lab can produce. A checklist filled in for a role that has never had real mentoring built into it before is not a small paperwork exercise — it is the first time this role's onboarding is being designed on purpose rather than accumulating by default, which is exactly the problem this course's introduction named.
Leader's note, for running this in a group
Ground the exercise in Numbers 11:28 before anyone starts filling in the form. State plainly that Joshua's formation took years of ordinary, repeated proximity, not a single orientation session — and that the checklist being built here is meant to start that same kind of sustained pattern, not to complete a training obligation in ninety days and then stop. Without this framing, participants will treat the ninety-day mark as an ending rather than as the close of only the most formative opening season.
Require a specific, named mentor for Step 2, not a role or department. "Someone from the worship team will help them" is not a mentor in the sense Acts 9 and 11 describe. Push participants to write an actual name, and if no name comes to mind, treat that gap as the lab's most important output for that role rather than something to paper over before moving on.
Watch for checklists that skip Step 3 entirely, offering only observation with no real responsibility extended. This is the opposite failure from rushing someone in too fast, but it is still a failure — Matthew 10 shows Jesus giving the Twelve real, if appropriately scaled, responsibility, not indefinite shadowing. A checklist with nothing genuinely at stake for the new person by day ninety has not actually applied lecture 4-2.
Take 1 Timothy 3:6-7 seriously enough to ask hard questions about existing team members, not only future ones. If, while building this checklist, a participant realizes a currently serving team member was given significant responsibility without ever having gone through anything like Steps 1 through 3, that realization is worth surfacing and addressing directly — not as blame for a past decision, but as a present gap this lab has just made visible.
4-1. The form: A New Team Member's First Ninety Days
4-2. Leader's checklist for this lab
| Item | Done |
|---|---|
| Framed the exercise with Numbers 11:28 -- a first pattern, not a training obligation that ends at day ninety | [ ] |
| Required an actual named mentor in Step B, not a role or a department | [ ] |
| Confirmed Step C names real, appropriately scaled responsibility, not indefinite observation alone | [ ] |
| Wrote the ninety-day review questions in Step D in advance, checked against 1 Timothy 3:6-7 | [ ] |
| Asked whether any currently serving team member skipped a process like this one, and surfaced that gap honestly | [ ] |
핵심 요약
- This lab builds one concrete checklist for one real role, covering the first week, first month, and first ninety days, each tied to a specific principle from this chapter's four lectures.
- A generic checklist — orientation, a named-but-undefined mentor, an automatic ninety-day promotion — is easy to produce and does not actually apply what Exodus 18-24-33, Matthew 10, Acts 9 and 11, or 1 Timothy 3 modeled.
- The most valuable finding this lab can produce is often a gap: no specific mentor yet, no real responsibility scaled into the plan, or a currently serving team member who never went through anything like this.
- Numbers 11:28 should frame the whole exercise: the ninety-day mark closes only the most formative opening season, not the whole process of forming a team member well.
- The ninety-day review should ask what has actually been tested and shown, not simply whether the calendar date has arrived.
| Front | Back |
|---|---|
| The form's four sections | First week (instruction + presence), first month (named mentor), first ninety days (scaled responsibility), the review. |
| Step B's standard | An actual name and a specific action -- not a role, not "someone will help." |
| Step D's check | 1 Timothy 3:6-7 -- what has been tested and shown, not just how much time has passed. |
| Numbers 11:28 | Formation through sustained proximity -- day ninety closes an opening season, not the whole process. |
One sentence to remember A checklist that cannot name an actual mentor or an actual scaled responsibility is not yet an onboarding plan -- it is a description of what you intend to eventually figure out.
This week's action Complete the form in section 4-1 in full, for one real role, including an actual name in Section B, before week 5 begins.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Looking at Section A of your completed form, is the "real presence" line concrete enough that you could point to exactly where and when it will happen, or is it still closer to a general intention?
- Looking at Section B, did you write an actual person's name for the mentor, and can you describe specifically what they will do, the way Acts 9 and 11 describe what Barnabas did?
- Looking at Section C, does the responsibility you named feel appropriately scaled — enough to be real, drawing on Matthew 10, without outrunning what has actually been tested, drawing on 1 Timothy 3:6?
- If your honest answer at Section D's ninety-day mark turned out to be "not enough has actually been tested yet," what would you do — extend the timeline, or proceed anyway? Which pressure would be harder to resist?
- This lab asked you to build a plan for one specific role. Was it harder to be specific than you expected, and if so, what does that difficulty tell you about how this role has been onboarded so far?