Lecture 1-5: In My Own Seat, Mapping Our Team's Current State
Contents 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 an argument about teams in general: why they are structurally necessary, how biblical ministry was actually built as team ministry, what genuinely distinguishes a team from a group, and how to diagnose which state a ministry is currently in. This lecture asks you to stop arguing in general and draw one specific map: your own team, right now, as it actually is.
The task is concrete: a form that has you list who is actually on your team, what each person actually does, where the gaps sit, and — using the tests from 1-3 and 1-4 — whether what you have functions as a true team or a loose group standing near each other. Not a discussion question to talk through in the abstract. A form to fill in, in your own handwriting or your own typing, with your own actual names and actual gaps in it.
What these 16 minutes give you
- List, specifically, everyone currently involved in your ministry team, rather than describing the team only as a category ("the volunteers").
- Apply the Nehemiah 3 interdependence test and the Moses/Acts 6 diagnostic tests from 1-3 and 1-4 to your own team, using them as a check rather than a general impression.
- Identify at least one specific gap in your current team — a section of the wall with no one building it, or one person quietly holding two sections.
- Explain why Luke 14:28's instruction to "count the cost before building" frames this exercise as sober planning, not as criticism of a team that already exists.
For which of you, desiring to build a tower, doesn't first sit down and count the cost, to see if he has enough to complete it?" — Luke 14:28
World English Bible
Jesus's instruction comes in the middle of a hard teaching about the cost of , but the illustration itself is ordinary building wisdom, not a spiritual test: nobody starts a tower without first checking what they actually have to work with. Applied here, the point is not "second-guess whether your team should exist." It is "know exactly what you are building with, and where it is thin, before you build anything further on top of it." A leader who moves straight to recruiting (chapter 2), writing role descriptions (chapter 3), or planning training (chapter 4) without first drawing an honest map of the team that already exists is building without having counted anything — not because they are careless, but because nobody told them counting came first. This lab is that count.
Why this comes before chapter 2
Chapters 2 through 8 of this course will ask you to recruit, structure, train, run meetings, handle conflict, survive a crisis, and eventually plan a succession. None of that can be built well on top of a team you have never actually mapped. A leader who moves straight to "who should we recruit next" without first knowing where the current team's actual gaps and overlaps sit will very often recruit for the wrong thing — filling a slot that looks empty from a distance while a genuinely thin section, invisible without the map, keeps failing quietly.
Luke 14:28 makes this ordinary wisdom, not spiritual anxiety. Nobody builds a tower without first checking what they have. A leader who has never mapped their own team — who is actually on it, what each person actually does, where the sections connect or fail to connect, and whether the whole thing passes the tests from 1-3 and 1-4 — is building without having counted anything.
What usually goes wrong when leaders skip this
Three patterns are worth naming before you begin.
Describing the team as a category instead of a list of people. Ask an untrained leader who is on their team, and the answer is often a role or a number ("about six volunteers," "the greeting team") rather than actual names and actual tasks. A leader who cannot name, specifically, who does what is mapping a category, not a team — and every test from 1-3 and 1-4 requires specific names doing specific, checkable things.
Confusing "everyone is busy" with "the team is interdependent." It is tempting to conclude a team is healthy because everyone involved is clearly working hard. Busyness is not evidence of interdependence. The Nehemiah 3 test from lecture 1-3 asks a different question: if this specific person's section were removed, would the wall actually gap, or would the task simply continue because the contributions were interchangeable all along?
Skipping the gap question because naming a gap feels like an accusation. Some leaders will avoid writing down "no one is actually doing X" because it feels like either an admission of failure or an implicit criticism of a teammate. The form below asks for the gap plainly, on purpose — a wall section with no one building it is a fact about the wall, not a verdict on anyone's character.
How to fill in the form
Use the form in section 4-1. Copy the headings onto paper if a printed copy is not available, or reproduce them in whatever document you use for this course.
Five steps to follow
Step 1. List everyone currently involved in your ministry team, by name, and next to each name write, in a few words, what they actually do — not their title, their actual current activity.
Step 2. For each name, apply the Nehemiah 3 test: is this person's contribution distinct from every other name on the list, and does something else on the list depend on it? Mark each name as "distinct and depended-on" or "interchangeable with another name here."
Step 3. Run the Moses test from lecture 1-4: is there a question or task, anywhere on this list, where the line forms for one specific person regardless of what the actual question is? Name that person and that task honestly if one exists.
Step 4. Name at least one gap — a section of the work that nobody on your current list is actually building, or a section two names both quietly hold at once because no one else was ever recruited for it.
Step 5. Using Steps 2 and 3 together, write one honest sentence classifying your current team: solo, informal group, or true team, and the specific evidence for that classification.
What usually goes wrong while filling it in
"Everyone on my list is technically doing something different, but Step 2 still feels wrong." If your list has distinct titles but every task would survive any one person's absence unchanged, you may be describing a group with a Nehemiah 3 vocabulary layered on top of it. Trust the removal test over the title.
"My honest answer to Step 3 names me." This is extremely common and is not a failure to admit. If you are the person the line forms for, on nearly everything, write that down plainly. Discovering that your own team is currently solo, with your name in Moses's seat, is exactly the finding this lab exists to surface.
"Step 4's gap feels like it will hurt someone's feelings if I write it down." Write it anyway, using the language of the wall, not the language of a verdict on a person. "No one currently follows up with first-time visitors during the week" is a fact about a missing section. It is not the same statement as "so-and-so is failing at their job."
Leader's note, for running this in a group
Starting the group
Frame the exercise with Luke 14:28 before anyone starts writing. State plainly that mapping a team's current gaps is not an audit meant to expose anyone, and it is not a criticism of the team that already exists — it is what any builder does before adding another course of stones. Say this explicitly; without it, some participants will experience Step 4 as an accusation against a specific teammate rather than sober, ordinary planning.
Complete your own form in full, including Step 3, alongside the group. A leader asking others to name where the line forms in their own ministry, while quietly exempting their own leadership from the same test, undermines the exercise. If Moses's seat is, honestly, your own seat, your own form should say so.
Do not let Step 4's gaps turn into naming who is underperforming. The form asks for gaps in the wall, not verdicts on individual builders. If a participant starts describing a specific teammate's shortcomings rather than a specific missing or doubled-up section, gently redirect the language back to the structure: what is the actual task with no one on it, independent of whose fault that might be.
Treat a "solo" or "informal group" finding as useful information, not a crisis. Most readers of this course, honestly filling this form in, will land somewhere short of "true team," and that is the expected, ordinary starting point this course is built to work from — not evidence that something has already gone wrong. Chapter 2 onward exists specifically for teams at this starting point.
Watch for a participant who cannot name any gap at all. A team with genuinely zero gaps and zero overlaps is rare enough that "I found nothing" is usually worth a second look together, gently, rather than being accepted at face value — often the gap is simply invisible to someone standing too close to it.
4-1. The form: Our Team's Current State
4-2. Leader's checklist for this lab
| Item | Done |
|---|---|
| Framed the exercise with Luke 14:28 as sober planning, not an audit, before anyone wrote anything | [ ] |
| Completed my own form in full, including Section C, alongside the group | [ ] |
| Redirected Section D away from naming underperforming individuals, toward naming missing sections | [ ] |
| Treated a "solo" or "informal group" finding in Section E as an expected starting point, not a crisis | [ ] |
| Followed up privately with anyone who reported finding no gap at all | [ ] |
In short
- This lab maps four things plainly: who is actually on the team and what they actually do, whether each contribution is distinct and depended-on or merely interchangeable, where the Moses-style bottleneck sits if one exists, and at least one real gap in the current structure.
- Luke 14:28's "count the cost before building" frames the exercise as ordinary, sober planning — not an accusation against the team that already exists.
- The most common failures of this lab: describing the team as a category instead of specific people, mistaking busyness for interdependence, and avoiding the gap question because it feels like an accusation.
- A gap should be named as a fact about a missing or doubled-up section of the wall, not as a verdict on a specific person's performance.
- Most leaders honestly completing this form will land somewhere short of "true team" — the expected, ordinary starting point this course is built to work from, not a sign that something has already gone wrong.
| Front | Back |
|---|---|
| The form's five sections | Who and what they do, the Nehemiah 3 test, the Moses test, at least one gap, the honest classification. |
| Luke 14:28 | Count the cost before building -- sober planning, not an accusation against the team that exists. |
| The most common failure | Naming a category instead of specific people, or mistaking busyness for interdependence. |
| Gaps are facts, not verdicts | Name the missing section of the wall, not the person's shortcomings. |
★ One sentence to remember You cannot build chapters 2 through 8 well on top of a team you have never actually mapped.
✓ This week's action Complete the form in section 4-1 in full, including the honest classification in Section E, before week 2 begins.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Looking at Section A of your completed form, was it harder to list actual names and actual tasks than you expected? What does that tell you?
- Looking at Section B, how many names came out "interchangeable" rather than "distinct and depended-on"? Does that surprise you?
- If Section C named you specifically, what is one concrete change you could make this month toward not being the only person the line forms for?
- Read your Section E classification back to yourself. Is it more or less honest than the answer you would have given before doing Sections A through D?
- Luke 14:28 frames counting the cost as ordinary wisdom, not criticism. Did filling in this form feel more like sober planning or more like an indictment of your team — and if the latter, what would need to change for it to feel like the former?