무료

수료증 무료 발급 — 2027년 3월 31일까지.

LM403E Building a Ministry Team

Lecture 3-5: In My Own Seat, Writing a Role Description

카드로 보기 (3분)
목차 41
LM403E Building a Ministry Team
제 0 장 · Introduction: Why a Team, Not Just Yourself
  1. Introduction: Why a Team, Not Just Yourself
제 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
제 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
제 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
제 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
제 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
제 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
제 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
제 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

핵심만 먼저 보기 ↓

15분

Four lectures have argued for the same underlying claim from four different angles: that a role belongs on paper, that decision authority belongs on paper, that even a team of two benefits from this, and that unwritten roles are exactly how one person quietly ends up carrying four. This lecture stops arguing and asks you to do the thing: write one real role description, for one real role, on your actual team, using a template short enough to finish in one sitting.

This is not a discussion exercise. It produces an artifact — one page, filled in with real names and real specifics — that should outlive this course and actually get used the next time someone joins your team, the next time a role changes hands, or the next time you yourself need to remember exactly what you agreed to take on.

이 15분으로 얻는 것

  • Write a complete, specific role description for one real role on your team, using the five-part template in section 4-1.
  • State the difference between a purpose sentence and a list of responsibilities, and explain why a role description needs both.
  • Identify who a given role reports to, or name honestly that this has never been decided.
  • Explain how Acts 6:4's model of a precisely stated role protects both the person in it and the ministry it serves.

But we will continue steadfastly in prayer and in the ministry of the word." — Acts 6:4

World English Bible

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

WEB

Acts 6:4 is a role description in miniature — one sentence, naming what the apostles would continue doing, precise enough that everyone in that early church knew exactly what belonged to the apostles and what did not. It is worth noticing what the sentence does not do: it does not say "the apostles will keep doing important spiritual things," a phrase vague enough to justify almost anything or exclude almost anything, depending on who is arguing. It says two specific things — prayer, and the ministry of the word — and stops there. That precision is what protected the role. Nobody could quietly expand "ministry of the word" to include tasks the apostles had just handed off, and nobody could shrink it either, because the sentence was specific enough to hold its own shape. Luke 14:28's counting the cost, already used in lecture 1-5 of this course's companion volume for mapping a whole leadership seat, applies here at the scale of a single role: know exactly what a role actually requires before agreeing to hold it, or before asking someone else to.

Why a role description needs five parts, not one

A role description that is only a job title ("Sound Technician") tells you almost nothing. A role description that is only a long list of tasks tells you a great deal about this week but nothing about what the role is for, which matters the moment an unlisted task shows up and someone has to decide whether it belongs to this role or not. The template in section 4-1 asks for five specific things because each one answers a question the others cannot answer on their own: a title (so the role has a name people can refer to), a one-sentence purpose (so a new, unlisted situation can be judged against the role's actual reason for existing, the way Acts 6:4's single sentence let the early church judge new requests against the apostles' stated purpose), three to five specific responsibilities (so the role's regular content is not left to memory), who the role reports to (so a question or a conflict has somewhere specific to go), and a time commitment (so nobody, including the person in the role, is guessing at how much this is actually supposed to take).

Filling in the form

Use the template in section 4-1. Reproduce the headings on paper or in whatever document you use for this course if a printed copy is not available.

Step 1. Choose one real role. Pick a role that actually exists on your team right now — yours, or someone else's, with their knowledge if it is not yours. Do not invent a hypothetical role for the sake of the exercise; the value of this lab depends entirely on it being real.

Step 2. Write the role title. Keep it short and specific enough that someone hearing it for the first time would have a rough idea what it covers.

Step 3. Write the purpose in exactly one sentence. This is the hardest step, and the one most worth taking seriously. If you cannot compress the role's reason for existing into one sentence, you likely do not yet have full clarity on what the role is actually for — which is itself a useful, if uncomfortable, thing to discover.

Step 4. List three to five specific responsibilities. Specific enough that two different people reading the list would agree on whether a given task belongs to this role. "Helps with music" is not specific. "Confirms the setlist with the pastor by Thursday and leads rehearsal on Saturday" is.

Step 5. Name who this role reports to. If your honest answer is "nobody, currently," write that down rather than guessing at an answer that sounds better. An unassigned reporting line is a real and useful finding, not a failure of this exercise.

Step 6. Estimate the time commitment. A rough, honest number — hours per week, or hours per month for something less frequent — matters more than false precision. The goal is naming a number at all, not naming the perfect one.

What usually goes wrong while filling it in

"The purpose sentence keeps turning into a list." This is the most common snag, and it usually means the role has grown past its original shape without anyone noticing. Write the list version first if you need to, then force yourself to compress it to one sentence afterward — the compression itself often reveals what the role's real center is, separate from everything that has accumulated around it.

"I don't actually know who this reports to." As with lecture 1-5's version of this same finding, write the true answer down rather than inventing a comfortable one. A role with no reporting line is not automatically a crisis, but it is a gap worth naming and, ideally, closing in a short conversation this week rather than leaving unnamed.

"The responsibilities list is either much longer than five items, or the role clearly overlaps with someone else's role." Either finding is useful. A responsibilities list this long may be evidence of exactly the silent overload lecture 3-4 named — this role has likely absorbed pieces of two or three roles that were never separately staffed. Note it honestly rather than shrinking the list artificially to fit the template.

Leader's note, for running this in a group

Make it a keeper

Frame the exercise as building something the team keeps, not an audit. State plainly, before anyone starts writing, that a finished role description is meant to be reused — handed to a new team member, referred back to in a disagreement about whose job something is, revisited when the role changes. This is not paperwork produced once and filed away; it earns its keep by being consulted later.

Complete your own role description alongside the group. If you lead this team, write your own role description in full, including a purpose sentence and an honest reporting line (even if your honest answer to "who do I report to" is a pastor, an board, or nobody). A leader who asks others to define their roles precisely while leaving their own vague undermines the exercise for everyone else.

Do not let "we'll write it later" survive the session. A role description that does not get finished in the room, in this lab, has a strong tendency to never get finished at all. If time is short, prioritize finishing one complete role description over starting several incomplete ones.

Watch for a responsibilities list that reveals hidden overload. If someone's honest list runs well past five items, or clearly contains pieces of what should be two or three separate roles, follow up with them individually using lecture 3-4's framework, rather than only noting it in the group setting.

Treat Acts 6:4's precision as the standard to aim for, not a Bible-times ideal that doesn't translate. One sentence, specific enough to hold its shape when tested by an unlisted situation, is achievable for a modern volunteer role — it is exactly what this lab's Step 3 is asking each person to produce.


4-1. The form: writing a role description

ROLE DESCRIPTION -- ONE REAL ROLE, FILLED IN HONESTLY Team: ____________________ Date: ____ / ____ A. Role title Short and specific enough that a stranger could guess roughly what it covers. B. Purpose, in exactly one sentence Like Acts 6:4 -- specific enough to hold its shape when an unlisted situation comes up. C. Specific responsibilities (3 to 5) Specific enough that two different people would agree whether a task belongs here. Much more than 5 items may mean this role absorbed pieces of two or three roles. D. Reports to "Nobody, currently" is a real answer. E. Time commitment A rough honest number beats false precision. F. One thing writing this down showed me Acts 6:4 -- one precise sentence protects both the person and the role.

4-2. Leader's checklist for this lab

Item Done
Framed the exercise as building something the team keeps, not an audit [ ]
Completed my own role description in full, including an honest reporting line [ ]
Did not let anyone leave with an unfinished role description [ ]
Followed up individually with anyone whose responsibilities list revealed hidden overload [ ]
Named Acts 6:4 as the standard of precision to aim for [ ]

핵심 요약

  • A complete role description names five things: a title, a one-sentence purpose, three to five specific responsibilities, who the role reports to, and a time commitment.
  • The purpose sentence matters most and is hardest to write — it is what lets an unlisted, new situation be judged against the role's actual reason for existing, the way Acts 6:4's sentence protected the apostles' stated role.
  • "Nobody, currently" is a legitimate, useful answer to who a role reports to — naming the gap is more useful than inventing a comfortable answer.
  • A responsibilities list running well past five items may be evidence of the silent overload lecture 3-4 named, not simply a role that needs a longer template.
  • A role description finished in this lab should outlive the course — reused with new team members, in disagreements about whose job something is, and whenever the role itself changes.
Front Back
The form's five parts Title, one-sentence purpose, 3-5 responsibilities, reports to, time commitment.
Acts 6:4 One precise sentence -- specific enough to hold its shape against new demands.
A list too long May mean this role has absorbed pieces of two or three unstaffed roles.
"Nobody, currently" A legitimate answer to who a role reports to -- name the gap, don't paper over it.

★ One sentence to remember A role description this course produces is not paperwork filed away -- it earns its keep the next time someone new joins, or someone argues about whose job it was.

✓ This week's action Complete the form in section 4-1 for one real role on your team, and show it to at least one other person on that team.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.

묵상 및 토론

  • Which step of the form was hardest for you to complete — the one-sentence purpose, the specific responsibilities, or the reporting line? What does that difficulty tell you about the role?
  • If your honest answer to Section D was "nobody, currently," what is one concrete step you could take this month to name someone?
  • Compare your Section C list to your actual week. Does the role, as written, match what you or the role-holder actually spend time on — or has it quietly grown or shrunk since anyone last thought about it?
  • Acts 6:4's one sentence protected the apostles' role from being silently redrawn by an urgent new demand. Has your own role, or a role you supervise, ever been silently redrawn this way?
  • Now that you have written one role description, what would it take to write one for every role currently active on your team?

로그인하시면 여기에 답을 적고 보관하실 수 있습니다

다음 단계

여기까지가 강의입니다. 아래는 읽은 사람들이 남긴 글입니다.