Lecture 3-1: Putting a Role in Writing
목차 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
Ask a volunteer on a small ministry team what their role is, and most will answer in a sentence: "I help with the music," "I'm on the welcome team," "I look after the kids' snacks." Ask them a second question — what exactly are you responsible for, and what happens if it doesn't get done — and the answer usually gets vaguer, not clearer. That gap between a role someone can describe and a role someone can actually be held to is this lecture's whole subject.
Nehemiah 3 is an unlikely place to look for team-building material. It is a list — forty verses of names and wall sections, the kind of chapter many readers skip on the way to somewhere more interesting. But read as a document about role clarity, it is exactly the opposite of boring. Every section of the wall belongs to a specific person or a specific family, named, with a specific stretch of stone assigned to them and no one else. This lecture argues that the specificity itself, not the wall, is the point worth learning from — and it is also this chapter's required lecture on a genuine disagreement: how early, and how formally, a small volunteer team should put its roles in writing.
이 17분으로 얻는 것
- Explain what Nehemiah 3's repeated naming pattern demonstrates about written role clarity, using at least one specific verse.
- Define, in your own words, the difference between a role that is understood and a role that is written.
- State fairly both positions in this lecture's disagreement over how early a small team should formalize its roles.
- Identify one role on your own team that exists only as a shared understanding, with no written form at all.
Then Eliashib the high priest rose up with his brothers the priests, and they built the sheep gate; they sanctified it, and set up its doors; even to the tower of Hammeah they sanctified it, to the tower of Hananel." — Nehemiah 3:1
World English Bible
Above the horse gate, the priests made repairs, everyone across from his own house." — Nehemiah 3:28
WEB
Next to them, the Tekoites made repairs; but their nobles didn't put their necks to the work of their lord." — Nehemiah 3:5
WEB
Read Nehemiah 3:1 and 3:28 together, and a pattern emerges that runs the length of the chapter: this section, this specific gate or stretch of wall, was built by this named person or this named group, and no other section is credited to them. Verse 28 pushes the specificity down to the smallest scale in the whole list — not simply "the priests," a group already named, but priests working "everyone across from his own house," a role subdivided until it points at one person and one stretch of stone. Nobody reading Nehemiah 3 has to ask who was supposed to build the horse gate section. It says so, in writing, forty verses before anyone could plausibly forget or dispute it.
Verse 5 supplies the chapter's one counter-example, and it is worth taking seriously rather than skipping past. The Tekoites — ordinary people, not nobility — show up twice in the list and are credited both times with real work. Their nobles, however, "didn't put their necks to the work of their lord." The text does not soften this. It names the group, states plainly that they were expected to contribute, and records that they didn't. That a list this careful about who built what also records who declined to build anything is not an accident. It is evidence for exactly the point this lecture is making: writing a role down does not guarantee it gets done, but it does mean a failure to do it can be named specifically, by name, rather than dissolved into a vague sense that things didn't quite come together this month.
1. What "the role is understood" actually means
Most small ministry teams do not lack roles. They lack written roles. Someone leads worship because they have led worship for two years and everyone has come to expect it. Someone handles the sign-up sheet for meals because they started doing it once and it stuck. These are real roles, doing real work, and in a small enough team with a stable enough group of people, an unwritten role can function acceptably for a surprisingly long time.
It stops functioning the moment any of three ordinary things happens: the person holding the role is unavailable for a season and someone else has to guess what they actually did; two people both believe a task falls under their own responsibility, or neither does, and it goes undone in the gap; or a new team member joins and has no way to learn what the role actually requires except by watching and hoping they infer it correctly. None of these are exotic failures. They are the normal, predictable cost of a role that exists only as a shared understanding in people's heads.
2. What Nehemiah 3 demonstrates that a modern list of names would not
It would be possible to read Nehemiah 3 as simply an ancient construction record, useful to historians and skippable for everyone else. But look again at what the chapter actually does. It does not say "the people built the wall." It divides the wall into named sections and assigns each section to a named party — Eliashib and his fellow priests at the sheep gate (3:1), the Tekoites at their stretch (3:5, 27), priests "everyone across from his own house" at the horse gate (3:28). The specificity is not decoration. It is the mechanism that let Nehemiah, or anyone else standing at any point on that wall, know exactly whose responsibility that stretch of stone was — and it is the same mechanism that let the failure of the Tekoite nobles be named specifically rather than lost in a general, unattributed sense that "some of the work didn't get done."
A ministry team's roles work the same way. A role written down — this specific task, this specific person, this specific standard for done — can be checked against reality. A role that exists only as an understanding cannot be checked against anything except memory, and memory is exactly what fails first when a team is under real pressure: a leader out sick, an unexpected conflict, a Sunday when three things go wrong at once.
3. Writing a role down is not the same thing as writing a contract
It is worth being precise about what this lecture is not arguing. Nehemiah 3 is not a legal document, and nothing about writing a ministry role down needs to feel like drafting one. A written role can be as short as a single sentence taped inside a supply cabinet: "The snack coordinator brings enough snacks for 20 kids each week and tells the lead teacher by Thursday if they can't." That sentence took under a minute to write. It does more real work than a year of "everyone just kind of knows Maria handles snacks" — because now, if snacks don't show up one Sunday, there is a specific, agreed thing that didn't happen, rather than a vague disappointment nobody can quite locate the source of.
4. This is a point where readers will not agree
Some readers, at this point, will already be uneasy — not about the principle, but about how far to take it on a team of two or three unpaid volunteers who already give up their evenings and weekends for this ministry. That unease deserves a fair hearing, because both sides of this disagreement are held by thoughtful people who care about the same teams, for reasons that make real sense from where they stand.
The case for writing roles down early, even for a two-person team: A role that lives only in memory is a role that quietly changes shape depending on who is remembering it, and it disappears the moment the person holding it disappears. Nehemiah 3's specificity was not reserved for large projects — the text names individual families building individual houses' worth of wall. On this view, "we're too small to need this" gets the size question backward: a team of two has less slack to absorb a misunderstanding than a team of twenty, because there is no one else to quietly cover the gap. Writing down even a one-sentence role description costs almost nothing and removes a real, if small, risk every week it goes undone.
The case for waiting, or formalizing lightly: A role description, a form, and a review conversation can, in a small volunteer team held together mostly by relationship and shared purpose, read less like clarity and more like an employer treating a friend like an employee. Volunteers who give their time freely can experience early formalization as a signal that they are no longer trusted, or that the ministry has started to feel like a job rather than a — and a team that loses that sense of shared calling can lose its volunteers along with it. On this view, structure should follow real friction (a missed handoff, a genuine disagreement about whose job something was), not arrive in advance of any problem it is meant to solve, especially in a team small enough that everyone already knows, in practice, roughly who does what.
Neither position is careless, and neither is obviously right for every team. A children's ministry with high turnover and real safety stakes has different reasons to formalize early than two friends who have run the same small prayer group together for six years. This course's own position — stated plainly, not hidden — leans toward writing roles down even in small teams, on the strength of Nehemiah 3's own example and the specific, low cost of a short written role. But a reader who weighs the relational cost more heavily and chooses to formalize later, and lightly, is not disregarding this lecture. They are making the same trade-off this lecture names, and landing on the other side of it. What both sides should refuse is the third option neither position defends: never writing anything down, and discovering the cost of that only when a role goes silently undone, the way the Tekoite nobles' work went silently undone, and nobody can quite say whose job it was.
Diagram 1. Understood role versus written role
핵심 요약
- Nehemiah 3's list of named builders and named sections demonstrates that specificity, not the size of the project, is what makes a role checkable against reality.
- Nehemiah 3:28's detail — priests working "everyone across from his own house" — pushes role clarity down to the individual level, not just the group level.
- Nehemiah 3:5's Tekoite nobles show the cost of an unwritten expectation: even in a chapter this careful, a failure can only be named specifically because the role itself was specific.
- Readers genuinely disagree on how early a small volunteer team should formalize its roles — some hold clarity matters most at the smallest scale, others worry early formalization feels bureaucratic and demotivating; this course states its own lean while treating both as reasonable.
- Writing a role down does not require a contract. A single clear sentence can do most of the real work.
| Front | Back |
|---|---|
| Nehemiah 3's pattern | Named person, named section -- specificity that lets a role be checked against reality. |
| Nehemiah 3:28 | "Everyone across from his own house" -- role clarity down to the individual. |
| Nehemiah 3:5 | The Tekoite nobles didn't work -- a failure only nameable because the role was specific. |
| Where readers disagree | How early and how formally a small volunteer team should write its roles down. |
★ One sentence to remember An unwritten role is not a flexible role -- it is a role nobody, including the person doing it, can actually be held to.
✓ This week's action Pick one role on your team that has never been written down, and write the shortest honest sentence that describes it.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Pick one role on your own team that exists only as a shared understanding. What would the shortest possible written version of it look like?
- Nehemiah 3:5 names the Tekoite nobles' failure specifically. Would your team currently be able to name a gap that specifically, or would it dissolve into a vague sense that "things didn't get done"?
- Which side of this lecture's disagreement do you find yourself leaning toward for your own team, and what about your team's size, history, or turnover is shaping that lean?
- Has your team ever lost a volunteer, or nearly lost one, over something that felt like excessive formality? Has it ever suffered from the opposite — too little clarity? Which risk currently feels closer to your team's actual situation?
- What is the smallest, least bureaucratic way you could write down one role on your team this week, without it feeling like a contract?