Lecture 6-1: Defining Roles Before Recruiting People
목차 53
- Lecture 1-1: Missio Dei — Mission Belongs to the Sending God
- Lecture 1-2: Church Planting as the New Testament's Ordinary Pattern
- Lecture 1-3: Calling the Things That Are Not — A Theology of Apparent Nothing
- Lecture 1-4: What Makes a Plant a Church — Ecclesiology for Planters
- Lecture 2-1: The Antioch Pattern — From Scattered to Sending
- Lecture 2-2: Did Paul Have a Strategy? Reading Acts Honestly
- Lecture 2-3: The Apostolic Band — A Team, Not a Solo Act
- Lecture 2-4: When Planting Partners Fall Out — Paul and Barnabas
- Lecture 2-5: What This Chapter's Evidence Does Not Settle
- Lecture 3-1: The Theology of Calling
- Lecture 3-2: Assessment — What a Serious Process Actually Looks For
- Lecture 3-3: Named Failure Patterns
- Lecture 3-4: The Sending Church's and Assessor's Own Responsibility
- Lecture 4-1: Demographic and Needs Analysis
- Lecture 4-2: Reading Receptivity and Existing Gospel Presence
- Lecture 4-3: Cultural and Spiritual Exegesis
- Lecture 4-4: Prayer-Walking and Spiritual Preparation
- Lecture 5-1: The Parent-Child Model
- Lecture 5-2: Networks and Denominational Planting
- Lecture 5-3: Organic and House-Church Multiplication
- Lecture 5-4: Bivocational Versus Fully Funded Planting
- Lecture 5-5: Choosing a Model Responsibly
- Lecture 6-1: Defining Roles Before Recruiting People
- Lecture 6-2: Recruiting a Core Team
- Lecture 6-3: Team Covenant and Shared Expectations
- Lecture 6-4: Team Health and Conflict in the Early, High-Pressure Season
- Lecture 7-1: Funding Sources Compared
- Lecture 7-2: Building a Launch Budget
- Lecture 7-3: The Path to Self-Sustainability
- Lecture 7-4: Financial Integrity from Day One
- Lecture 8-1: Urban Church Planting
- Lecture 8-2: Rural and Small-Town Church Planting
- Lecture 8-3: Cross-Cultural and Immigrant-Context Planting
- Lecture 8-4: Generational and Subcultural Contextualization
- Lecture 9-1: Relational Evangelism — One Relationship at a Time
- Lecture 9-2: Sustained Prayer as Pre-Launch Infrastructure
- Lecture 9-3: Preview Gatherings — Rehearsing Before the Real Thing
- Lecture 9-4: Setting a Realistic Launch Date and Readiness Criteria
- Lecture 10-1: Designing a First Public Gathering
- Lecture 10-2: Preaching and Teaching in a Launch Season
- Lecture 10-3: First-Time Guest Follow-Up and Assimilation Pathways
- Lecture 10-4: Baptism, Membership, and Belonging in a New Congregation
- Lecture 10-5: Sustaining Momentum After the Initial Launch Excitement Fades
- Lecture 11-1: Identifying and Developing Emerging Leaders Early
- Lecture 11-2: Raising Up Elders in a Young Congregation — Too Fast, Too Slow
- Lecture 11-3: Defining and Transmitting a Plant's Theological and Missional DNA
- Lecture 11-4: Planning for the Plant's Own Future Multiplication
- Lecture 12-1: The Church-Planting-Movements Debate — Speed and Depth
- Lecture 12-2: Denominational Oversight and Independent Autonomy
- Lecture 12-3: Planting in Persecution and Restricted-Access Contexts
- Lecture 12-4: Sustainability and Burnout Specific to Church Planting
- Lecture 12-5: Capstone — A Personal Theology and Strategy of Church Planting
Most planters do not fail a core team by choosing the wrong people. They fail it by never deciding, before they started asking anyone to join, what the team was actually for. A planter under pressure to show momentum will often recruit first and sort out roles later — collecting whoever is willing and enthusiastic, then improvising a structure around the people who showed up rather than the work that needs doing. The opposite failure looks more responsible and is not: a planter who spends months drafting an org chart with a worship director, a children's ministry coordinator, a small-group pastor, and a facilities team before a single person outside the planter's own household has agreed to show up on a Sunday. Both failures share a cause. Neither one asked, honestly, what a team of this size, at this stage, with this little track record, actually needs in order to do the specific work in front of it — and what it can safely leave unbuilt until later.
This lecture treats role definition as a distinct step that has to happen before recruitment, not as something recruitment will sort out on its own. It draws on Exodus 18 — Jethro's counsel to Moses about delegated leadership — not because a chapter about Moses appointing judges over Israel maps directly onto a modern core team's org chart, but because the underlying criteria Jethro names (character and competence, named together, before any title is assigned) apply to a much smaller and earlier decision than the one Moses faced.
이 13분으로 얻는 것
- State the difference between what a core team needs at its earliest stage and what a full staff structure needs, and explain why collapsing the two produces either understaffing or premature over-structuring.
- Name the qualities Exodus 18:21 lists for delegated responsibility, and explain how they apply — by extension, not by direct mapping — to selecting core team members before any titles exist.
- Identify at least three functions an early core team must cover regardless of a plant's size or model, distinct from functions it can defer.
- Explain the specific cost of over-structuring a team before it has proven anything, as distinct from the more commonly discussed cost of understaffing.
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.
Exodus 18:21 (World English Bible)
Jethro is advising Moses about a national judiciary, not a church plant's launch team, and this lecture does not pretend the scale is comparable. What transfers is narrower and more useful: the criteria come in a fixed order, and character precedes function. Jethro does not tell Moses to find the most naturally gifted administrators available and then check afterward whether they can be trusted. He names the trust qualifications first — "able," "fear God," "men of truth," "hating unjust gain" — and only then assigns them a scope of responsibility calibrated to what has already been established about who they are. A planter assembling a first team of five or six people is doing something far smaller than appointing judges over thousands, but the same ordering question applies: is this person being evaluated for trustworthiness and maturity before being handed a role, or is a role being handed out first because the person is available and the planter is in a hurry to look staffed?
1. What a core team needs, and what it does not need yet
A core team at the pre-launch stage needs three things that no later stage of the plant's life can substitute for. It needs enough people who are spiritually mature enough to be trusted with something before there is any structure to hold them accountable — no employee handbook, no board yet, sometimes not even bylaws (this course does not re-teach the administrative structures covered in this school's dedicated course on , but it assumes a reader who has been through that material knows how much of it does not yet exist for a team of five people meeting in someone's living room). It needs gifting that complements the planter's own gaps rather than duplicates the planter's own strengths — a planter who is a gifted teacher and recruits four more gifted teachers has built a team that is uniformly strong in exactly the area the planter already covers and correspondingly weak everywhere else. And it needs a settled willingness to do work that will not look like ministry to an outside observer: moving folding chairs, running errands, sitting with one lonely visitor for an hour when it would be more energizing to be doing something more visibly spiritual.
What a core team does not need yet is a staff structure sized for a congregation that does not exist. A plant with twelve attenders does not need a children's ministry director, a worship pastor, an executive pastor, and a communications coordinator, even if a planter can picture needing all four eventually and wants to fill the roles early so the people are "already in place" when growth arrives. Filling roles ahead of need has a real cost beyond the obvious inefficiency: it creates positional authority before the position has proven necessary, which means a team member can end up defending a role's existence rather than serving the plant's actual, current needs. It also front-loads a level of formality — titles, defined lanes of responsibility, an implicit hierarchy — that a small team without an established culture often cannot bear without becoming brittle. A team of six people wearing eleven titles between them has usually organized itself around an org chart it copied from a much larger church rather than around the work six people can actually do well together.
2. Understaffing is the more visible failure, over-structuring is the quieter one
Most cautionary conversations about early planting teams focus on understaffing — not having enough hands for the launch, running the whole operation on one exhausted planter and a spouse. That failure is real and well documented, and this lecture does not minimize it. But the opposite failure gets less attention precisely because it looks more responsible from the outside. A planter with a fully diagrammed structure, defined job descriptions for roles nobody has been asked to fill yet, and a five-year staffing plan can present as thorough and strategic, when in practice the structure is solving a problem the plant does not have and has quietly deferred the problem it does have, which is that nobody has actually been asked yet to do the specific, unglamorous work the next six weeks require. A useful diagnostic question for a planter drafting any structure before launch: does this role describe work that needs doing in the next month, or does it describe a title the planter wants to have already assigned before anyone asks whether the plant is real?
3. Applying Jethro's ordering to a small team
Character and competence, named together and in that order, is a criterion a planter can apply at a much smaller scale than Moses's national appointments. Before assigning any function — even an informal one, like "you're handling setup and teardown" — a planter can ask the same two questions Jethro's list implies: is this a person of demonstrated trustworthiness (not necessarily a long track record, since a new plant rarely has the luxury of only recruiting people with decades of proven ministry history, but some real, observable pattern of integrity and reliability), and does this person actually have the competence the specific function requires, rather than simply the willingness. A team built entirely on willingness, with competence assumed to follow, tends to produce well-meaning failure in exactly the areas — finances, public teaching, of someone in crisis — where willingness is not sufficient substitute for either character or skill.
핵심 요약
- Planters fail core teams in two ways: recruiting first and sorting roles later, or drawing a full org chart before anyone has agreed to come. Both skip asking what the team actually needs now.
- Exodus 18:21 puts character ("able," "fear God," "men of truth") before function. Applied by extension to a small team, trustworthiness comes before a role is given.
- An early team needs maturity, gifts that fill the planter's gaps, and willingness to do unseen work. It can defer a staff structure sized for a church that does not yet exist.
- Over-structuring is the quieter failure. It gives authority to roles not yet needed and adds formality a young team cannot bear.
- Test each role: does it describe work needed in the next month, or a title the planter wants to assign?
Topic: Defining what an early core team needs, and what can wait, before recruiting anyone.
Remember: Decide the work first, then judge character and competence, in that order, before giving anyone a role.
Caution: Exodus 18 concerns a national judiciary, not a church plant. Only its criteria transfer. The lecture does not minimize understaffing. It adds that over-structuring is also a failure.
One line to carry into ministry: Create only the roles that describe work needed in the next month, and give them to people whose character you have observed.
스스로 확인해 보세요
읽었는지가 아니라 설명할 수 있는지를 묻는 것입니다. 체크는 이 기기에만 저장됩니다.
묵상 및 토론
- Look at your own plans, or a plant you have observed. Is there a role currently defined that no one is actually doing yet, kept in place because the planter wants it "already there"? What would it cost to remove it for now?
- Exodus 18:21 names character before competence. Can you think of a case — in this ministry context or another — where competence was allowed to substitute for character in a role assignment, and what resulted?
- This lecture argues that over-structuring is a quieter failure than understaffing because it looks more responsible. Do you find that claim persuasive from your own observation, or does it understate how damaging understaffing actually is?
- Name one function your own core team, present or planned, must cover regardless of size or model. Name one you are tempted to build structure for before it is needed.