Lecture 1-3: Covenant and Size — the Unglamorous Infrastructure
Contents 29
- Lecture 1-1: What a Crowd Cannot Do
- Lecture 1-2: Host and Shepherd, Not Resident Expert
- Lecture 1-3: Covenant and Size — the Unglamorous Infrastructure
- Lecture 1-4: Practice Lab — Diagnose Your Group
- Lecture 2-1: The Anatomy of a Gathering
- Lecture 2-2: Opening Well
- Lecture 2-3: Closing Well and Following Through
- Lecture 2-4: Practice Lab — Build a Session Plan
- Lecture 3-1: Open Questions and Closed Questions
- Lecture 3-2: Silence and the Quiet Member
- Lecture 3-3: The Dominant Talker and the Tangent
- Lecture 3-4: Practice Lab — Rewriting Questions and Planning Your Moves
- Lecture 4-1: The Inductive Method — Seeing Before Concluding
- Lecture 4-2: Prepared, Not Performing
- Lecture 4-3: Sitting With a Hard Text
- Lecture 4-4: Practice Lab — Build a Full Inductive Study
- Lecture 5-1: Praying Together, and What Confidentiality Actually Means
- Lecture 5-2: Noticing, and Following Up Without Becoming Surveillance
- Lecture 5-3: The Leader's Limits
- Lecture 5-4: Practice Lab — A Disclosure You Did Not See Coming
- Lecture 6-1: Naming the Kind of Conflict You Actually Have
- Lecture 6-2: Difficult Personalities, Named Fairly
- Lecture 6-3: When and How to Escalate
- Lecture 6-4: Practice Lab — A Live, Escalating Conflict
Nobody joins a small group because they are excited about a covenant document or a stated size limit. Both feel like administrative overhead next to the actual point — knowing people, studying Scripture together, praying for one another. This lecture argues that the overhead is not separate from the point; it is what protects it. A group with no stated expectations around confidentiality and attendance will eventually have a confidentiality breach or a member nobody can rely on, and by then it is too late to introduce the rule the incident would have prevented. A group with no sense of a size ceiling will eventually grow past the point where it can still do the things Lecture 1-1 said a small group exists to do — and nobody will have decided that on purpose; it will simply have happened.
What these 14 minutes give you
- Name the specific elements a group covenant should address (confidentiality, attendance, and what happens when the group changes shape) and explain what problem each one is actually solving for.
- State, with a reason grounded in group dynamics research rather than assertion alone, why somewhere in the range of roughly five to twelve people is a durable size for the kind of participation Lecture 1-1 described.
- Explain, using Exodus 18:13-23, what problem Jethro diagnosed in Moses' arrangement and what solution he proposed.
- Describe at least one concrete option for what a group should do once it outgrows its workable size.
Moses' father-in-law said to him, 'The thing that you do is not good. You will surely wear away, both you, and this people that is with you; for the thing is too heavy for you. You are not able to perform it yourself alone. Listen now to my voice. I will give you counsel, and God be with you. You represent the people before God, and bring the causes to God. You shall teach them the statutes and the laws, and shall show them the way in which they must walk, and the work that they must do. Moreover you shall provide out of all the people able men, such as fear God: men of truth, hating unjust gain; and place such over them, to be rulers of thousands, rulers of hundreds, rulers of fifties, and rulers of tens. Let them judge the people at all times. It shall be that every great matter they shall bring to you, but every small matter they shall judge themselves. So shall it be easier for you, and they shall share the load with you. If you will do this thing, and God commands you so, then you will be able to endure, and all of these people also will go to their place in peace.'
Exodus 18:17-23 (World English Bible):
1. What a covenant is actually for
Group
A group covenant is a short, explicit, agreed-upon statement of what members can expect from each other. It is not a legal document and it does not need to be formal — a single page, read aloud in the first meeting and revisited occasionally, is enough. Three elements do most of the work.
Confidentiality. "What's said in the group stays in the group" sounds obvious enough that it seems unnecessary to state — until someone shares something vulnerable, it travels outside the room through an ordinary, well-meaning conversation with a spouse or another friend, and the person who shared it stops trusting the group with anything real again. Stating confidentiality explicitly, before anyone has been hurt by its absence, is what makes vulnerability feel safe enough to attempt. It is worth being concrete about its limits too: most groups reasonably carve out an exception for anything suggesting risk of serious harm to the person or someone else, a point Chapter 5 of this course addresses directly.
Attendance expectations. A group where showing up is treated as optional will, over time, become a group where showing up feels optional — and a member who is absent more than they are present cannot be known or missed in the way Lecture 1-1 described. This does not mean punishing absence; it means naming, out loud, that consistent presence is what the group actually needs from its members in order to do what it exists to do, so that a member missing three weeks running is a known problem the group can address rather than a drift nobody named.
What happens when the group changes shape. Groups do not stay the same size or composition forever, and a covenant that never anticipates this leaves the moment of change to be improvised under pressure — usually badly. Naming in advance, even briefly, how the group will handle growth, departures, or eventually multiplying into two groups (the subject of Chapter 7) keeps a later transition from feeling like betrayal or abandonment to whoever is affected by it.
2. Why size has a ceiling, and it is not arbitrary
The Suggested Scripture for this lecture is Jethro's advice to Moses, and it is worth reading as more than an ancient administrative anecdote. Moses had structured Israel's dispute resolution around a single point of contact — himself — for a nation numbering in the hundreds of thousands. Jethro's diagnosis in Exodus 18:18 is blunt: "You will surely wear away, both you, and this people that is with you; for the thing is too heavy for you." Notice the diagnosis names harm to both sides — Moses would wear out, and the people would suffer worse and slower justice for it. His solution was not to work harder or delegate less; it was to build a tiered structure so that "every great matter" reached Moses while "every small matter" was handled at a scale where it could actually be handled well.
The small-group version of this principle is size itself. Group dynamics research offers a concrete reason a durable ceiling exists, not just pastoral instinct. Social psychologist Ivan Steiner's work on group productivity documented what is sometimes called process loss: as a group's size grows, the potential contribution of each additional member does not translate into actual participation at the same rate, because coordination costs rise and individual voices get less airtime. In plain terms — the bigger the group, the smaller the fraction of the meeting any one person can expect to speak, and past a certain size, the quietest members effectively stop participating at all, not because they have nothing to say but because the format no longer makes room for them. This is exactly the finding behind the widely repeated pastoral guidance — echoed across small-group ministry literature such as Bill Donahue's Leading Life-Changing Small Groups — that somewhere in the range of roughly five to twelve members is the durable band: small enough that everyone can speak in a single meeting and be tracked by the leader across weeks, large enough to survive normal attrition (a family moving, a work schedule changing) without collapsing to two or three people.
Five to twelve is a range, not a law, and this lecture is not claiming Scripture specifies a number — it does not. What Exodus 18 does specify is the principle: past a certain span of care, the structure itself starts failing the people it was meant to serve, and the honest response is not more effort from the person at the center but a change in structure.
3. What to do when a group outgrows itself
A group that has grown past its workable size has a decision to make, and pretending the growth is only good news avoids the decision rather than making it. Concrete options include: capping membership and directing new people to start or join another group; identifying and apprenticing a co-leader so the group can split into two groups that each stay in the durable range (the subject of Chapter 7 in full); or, if growth is temporary — a short-term influx around a particular season or series — being honest that the current format will only hold for a limited time and naming that limit to the group rather than letting the meeting simply get worse. What a healthy group does not do is let growth happen silently until the quietest third of the group has effectively stopped attending in any way that matters, having concluded, correctly, that the room no longer has space for them.
In short
- A group covenant makes explicit, before anyone is hurt by its absence, what members can expect around confidentiality, attendance, and how the group will handle changing shape.
- Confidentiality stated explicitly is what makes real vulnerability feel safe; most groups reasonably carve out an exception for risk of serious harm.
- Exodus 18:17-23 records Jethro diagnosing that Moses' single-point structure was wearing out both Moses and the people, and proposing a tiered structure instead — the same principle behind a small group's size ceiling.
- Group dynamics research (Steiner's concept of process loss) gives a concrete mechanism for why roughly five to twelve members is a durable range: airtime and trackability per person shrink as the group grows.
- A group that outgrows its size has real options — capping and redirecting, apprenticing a co-leader toward a split, or naming a temporary limit — and letting growth happen silently is not a neutral choice.
One-sentence summary: A group covenant and a defensible size ceiling are not administrative overhead but the infrastructure that protects what a small group is actually for — a covenant makes vulnerability safe, and a size limit, grounded in both Exodus 18 and group dynamics research, keeps every member able to actually be known.
Terms to remember: group covenant, process loss, tiered structure.
Carry forward to 1-4: the Practice Lab asks you to turn Lectures 1-1 through 1-3 on your own group and produce a one-page written diagnosis.
Check yourself
Not "did you read it" but "can you explain it". Ticks are kept on this device only.
Reflection and discussion
- Does your current group (or a group you have been part of) have an explicit covenant, or an unspoken one? What would writing it down explicitly change?
- Think of a time confidentiality was broken in a group setting, even in a small, well-meaning way. What effect did it have on what people were willing to share afterward?
- Jethro tells Moses "the thing is too heavy for you," naming harm to both Moses and the people. Can you think of a leadership situation — in a small group or elsewhere — where pushing through past a structural limit hurt both the leader and the people being served?
- This lecture cites research on group size and participation (Steiner's process loss) alongside pastoral literature recommending five to twelve members. Does grounding the number in research change how persuasive you find it, compared to simply being told "keep it small"?
- If your own group were to outgrow its workable size next month, which of the three options in this lecture (cap and redirect, apprentice and split, name a temporary limit) would fit your situation best, and why?