FREE

Course certificates are free until March 31, 2027.

LM403E Building a Ministry Team

Lecture 3-3: The Structure of a Small Team

View as cards (3 min)
Contents 41
LM403E Building a Ministry Team
Chapter 0 · Introduction: Why a Team, Not Just Yourself
  1. Introduction: Why a Team, Not Just Yourself
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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

Jump to the key points ↓

13 min

"We're only three people. We don't need roles and decision structure — we just talk." This is the most common objection to everything lectures 3-1 and 3-2 have argued, and it deserves a direct answer rather than a dismissal, because the instinct behind it is not wrong: a team of three genuinely does not need the same structure a team of thirty needs. What this lecture argues is narrower and, on reflection, harder to disagree with: a team of two or three still needs some real structure, just scaled to fit — and Jesus's own smallest working group shows exactly what that looks like.

Peter, James, and John appear together, set apart from the other nine disciples, at three of the most significant moments in the Gospels: the raising of Jairus's daughter, the transfiguration, and Gethsemane. Jesus, who could have treated the twelve as a single undifferentiated group at every moment, deliberately drew an inner circle of exactly three. This lecture is not primarily about why those three were chosen — it is about what their consistent, repeated presence together demonstrates: that meaningful structure, real and stable enough to matter at the most important moments, does not require large numbers to exist.

What these 13 minutes give you

  • Name the three occasions Mark records Peter, James, and John being set apart together, and state what each occasion had in common.
  • Explain why a small team still benefits from named structure, even when "we just talk" currently feels sufficient.
  • Describe at least two specific, low-effort ways a team of two or three can establish role clarity and decision structure without behaving like a large organization.
  • Identify what structure, if any, currently exists on your own smallest ministry team.

He allowed no one to follow him, except Peter, James, and John the brother of James." — Mark 5:37

World English Bible

After six days Jesus took with him Peter, James, and John, and brought them up onto a high mountain privately by themselves, and he was changed into another form in front of them." — Mark 9:2

WEB

He took with him Peter, James, and John, and began to be greatly troubled and distressed." — Mark 14:33

WEB

Three different moments, three different kinds of significance — a private miracle at Jairus's house, a revelation of Jesus's glory on the mountain, and Jesus's own deepest anguish in Gethsemane — and the same three names each time. This is not incidental. Jesus had twelve disciples, all called, all sent out, all entrusted with real ministry. And yet at the moments this Gospel treats as most significant, he consistently draws the same smaller group in close. Whatever else this pattern shows about these three individuals, it demonstrates something structural: a working group of exactly three, used consistently and deliberately across very different situations, was not too small to matter. It was, in these Gospel accounts, exactly the group Jesus repeatedly chose to work through.

1. What "structure" does not mean at this scale

It is worth being precise, before going further, about what this lecture is not recommending for a team of two or three. It is not recommending an org chart. It is not recommending a title for each person, a formal reporting line, or regular structured meetings with an agenda and minutes. All of that would be, exactly as the objection at the top of this lecture suspects, disproportionate to a team this size — and disproportionate structure on a small team can do real damage, making three friends serving together feel like they have been enrolled in a bureaucracy neither asked for.

What this lecture is recommending is much smaller, and fits inside a single honest conversation: knowing, without having to guess, what each of the two or three people is actually responsible for; knowing who makes the call when the group can't agree; and knowing this consistently enough that it does not have to be renegotiated from scratch every time a decision comes up. That is the entire structure a team of three needs. It is also, importantly, structure the team does not currently have if nobody has ever actually said it out loud — "we just talk" and "we have agreed, if only once, on who decides what" are not the same thing, even though both can feel identical from the inside on an ordinary week.

2. What Peter, James, and John's consistency actually demonstrates

The temptation, reading Mark 5:37, 9:2, and 14:33, is to focus entirely on why these three — what made them different from the other nine. That is a legitimate question, but it is not this lecture's question, and answering it fully is not necessary for the point being made here. The relevant observation is simpler: Jesus worked, repeatedly, through a defined smaller group inside a larger group, and he did this consistently enough that "Peter, James, and John" functions almost as a fixed unit across the Gospel, recognizable the moment the three names appear together.

A team of three volunteers running a hospitality ministry, or two people alternating Sundays in the nursery, is not too small a unit to have real, stable structure. If anything, the opposite is true: a group this small has less room to absorb confusion about who does what, because there is no larger pool of people to quietly cover a gap. A misunderstanding between two people on a two-person team is not a fraction of the team's problem. It is the whole team's problem.

3. Two concrete practices that fit a team of two or three

Naming responsibilities once, out loud, and writing the single sentence down. This is lecture 3-1's practice, scaled to its smallest form. On a two-person team, this might be as short as: "You handle the sign-up sheet and reminders; I handle the actual teaching schedule." Ten seconds to say. Worth having said, the first time a reminder doesn't go out and both people privately assumed the other one sent it.

Naming, in advance, what happens when the two or three of you disagree. A larger team can sometimes let a disagreement sit unresolved for a week while more people weigh in. A team of two does not have that luxury — an unresolved disagreement between the only two people on the team stops the team's actual work immediately. Deciding in advance, before any specific disagreement exists, whether decisions default to consensus, to whoever has been doing the role longer, or to a coin flip on genuinely minor questions, removes the need to invent a process under pressure, mid-disagreement, when neither person is at their most patient.

4. Why this matters more, not less, as a team grows

A team that establishes this habit at two or three people is not simply solving today's problem. It is establishing the pattern the team will need when it grows to five or eight — because a team that has never once said out loud who decides what will not suddenly develop the habit automatically once there are more people in the room to make the silence more expensive. The smallest team is, in a real sense, the cheapest and easiest place to build this habit, precisely because the stakes of getting the conversation slightly wrong the first time are so low.


Diagram 1. Real structure at the smallest scale

One Group, Three Moments -- The Same Three Names Peter, James, and John, set apart consistently, not once Mark 5:37 Jairus's house. A private miracle, a raising from death. "No one, except..." Mark 9:2 The mountain. Transfiguration -- Jesus's glory revealed. "Privately by themselves." Mark 14:33 Gethsemane. Jesus's own deepest anguish, before the cross. "He took with him..." A group of exactly three, used consistently across very different situations A team of two or three is not too small for real, stable structure to exist It just needs less of it, said out loud once, not renegotiated every time

In short

  • Mark 5:37, 9:2, and 14:33 show Jesus repeatedly, deliberately setting apart the same three disciples across very different, highly significant occasions.
  • This consistency demonstrates that a defined group of exactly three is not too small to function as a real, structured, working unit.
  • Real structure at this scale does not mean an org chart or formal meetings — it means naming, once and out loud, who is responsible for what and who decides when the group can't agree.
  • A small team has less room, not more, to absorb an unresolved misunderstanding, because there is no larger pool of people to quietly cover a gap.
  • Establishing this habit at two or three people builds the pattern a team will need later, when it grows and the cost of silence rises.
Front Back
Mark 5:37, 9:2, 14:33 The same three names, set apart across three very different, significant moments.
What this demonstrates Meaningful, stable structure does not require large numbers to exist.
Structure at this scale Not an org chart -- one honest conversation naming who does what and who decides.
Why smaller teams need it more No larger pool to quietly absorb a gap when only two or three people are on the team.

★ One sentence to remember "We just talk" and "we have agreed who decides what" feel identical on an ordinary week -- they are not the same thing.

✓ This week's action On your smallest team, say out loud, once, who is responsible for what and who decides when you disagree.

Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • Does "we just talk" currently describe your smallest ministry team? Has that ever caused a specific misunderstanding, even a minor one?
  • What do the three occasions in Mark 5:37, 9:2, and 14:33 have in common, beyond the same three names appearing? Why might consistency across different situations matter more than any single occasion alone?
  • If your smallest team is two or three people, what is the shortest sentence you could say out loud this week to name who is responsible for what?
  • What happens, currently, on your team when two people genuinely disagree and can't settle it themselves? Is there an agreed default, or does it get worked out fresh each time?
  • This lecture argues small teams have less room to absorb confusion, not more, because there is no larger pool to cover a gap. Does that match your own experience of a small team, or does it feel overstated?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.