무료

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

PT703E Church Planting: Theology and Practice

Lecture 6-4: Team Health and Conflict in the Early, High-Pressure Season

카드로 보기 (3분)
목차 53
PT703E Church Planting: Theology and Practice
제 0 장 · Introduction: The God Who Calls Things That Are Not
  1. Introduction: The God Who Calls Things That Are Not
제 1 장 · Chapter 1: Foundations — Missio Dei and the Theology of Church Planting
  1. Lecture 1-1: Missio Dei — Mission Belongs to the Sending God
  2. Lecture 1-2: Church Planting as the New Testament's Ordinary Pattern
  3. Lecture 1-3: Calling the Things That Are Not — A Theology of Apparent Nothing
  4. Lecture 1-4: What Makes a Plant a Church — Ecclesiology for Planters
제 2 장 · Chapter 2: Biblical Models — Antioch, Paul's Journeys, and the Apostolic Band
  1. Lecture 2-1: The Antioch Pattern — From Scattered to Sending
  2. Lecture 2-2: Did Paul Have a Strategy? Reading Acts Honestly
  3. Lecture 2-3: The Apostolic Band — A Team, Not a Solo Act
  4. Lecture 2-4: When Planting Partners Fall Out — Paul and Barnabas
  5. Lecture 2-5: What This Chapter's Evidence Does Not Settle
제 3 장 · Chapter 3: Discerning the Call and Assessing a Planter
  1. Lecture 3-1: The Theology of Calling
  2. Lecture 3-2: Assessment — What a Serious Process Actually Looks For
  3. Lecture 3-3: Named Failure Patterns
  4. Lecture 3-4: The Sending Church's and Assessor's Own Responsibility
제 4 장 · Chapter 4: Reading a Context — Exegeting a Community Before Planting
  1. Lecture 4-1: Demographic and Needs Analysis
  2. Lecture 4-2: Reading Receptivity and Existing Gospel Presence
  3. Lecture 4-3: Cultural and Spiritual Exegesis
  4. Lecture 4-4: Prayer-Walking and Spiritual Preparation
제 5 장 · Chapter 5: Models and Strategies of Church Planting
  1. Lecture 5-1: The Parent-Child Model
  2. Lecture 5-2: Networks and Denominational Planting
  3. Lecture 5-3: Organic and House-Church Multiplication
  4. Lecture 5-4: Bivocational Versus Fully Funded Planting
  5. Lecture 5-5: Choosing a Model Responsibly
제 6 장 · Chapter 6: Building a Core Team and Launch Team
  1. Lecture 6-1: Defining Roles Before Recruiting People
  2. Lecture 6-2: Recruiting a Core Team
  3. Lecture 6-3: Team Covenant and Shared Expectations
  4. Lecture 6-4: Team Health and Conflict in the Early, High-Pressure Season
제 7 장 · Chapter 7: Funding, Budgeting, and Sustainability
  1. Lecture 7-1: Funding Sources Compared
  2. Lecture 7-2: Building a Launch Budget
  3. Lecture 7-3: The Path to Self-Sustainability
  4. Lecture 7-4: Financial Integrity from Day One
제 8 장 · Chapter 8: Contextualization Across Culture
  1. Lecture 8-1: Urban Church Planting
  2. Lecture 8-2: Rural and Small-Town Church Planting
  3. Lecture 8-3: Cross-Cultural and Immigrant-Context Planting
  4. Lecture 8-4: Generational and Subcultural Contextualization
제 9 장 · Chapter 9: Pre-Launch — Evangelism, Prayer, and Preview Gatherings
  1. Lecture 9-1: Relational Evangelism — One Relationship at a Time
  2. Lecture 9-2: Sustained Prayer as Pre-Launch Infrastructure
  3. Lecture 9-3: Preview Gatherings — Rehearsing Before the Real Thing
  4. Lecture 9-4: Setting a Realistic Launch Date and Readiness Criteria
제 10 장 · Chapter 10: Launch and Early Assimilation
  1. Lecture 10-1: Designing a First Public Gathering
  2. Lecture 10-2: Preaching and Teaching in a Launch Season
  3. Lecture 10-3: First-Time Guest Follow-Up and Assimilation Pathways
  4. Lecture 10-4: Baptism, Membership, and Belonging in a New Congregation
  5. Lecture 10-5: Sustaining Momentum After the Initial Launch Excitement Fades
제 11 장 · Chapter 11: Leadership Development and Reproducing DNA
  1. Lecture 11-1: Identifying and Developing Emerging Leaders Early
  2. Lecture 11-2: Raising Up Elders in a Young Congregation — Too Fast, Too Slow
  3. Lecture 11-3: Defining and Transmitting a Plant's Theological and Missional DNA
  4. Lecture 11-4: Planning for the Plant's Own Future Multiplication
제 12 장 · Chapter 12: The Multiplication Debate, Sustainability, and a Capstone
  1. Lecture 12-1: The Church-Planting-Movements Debate — Speed and Depth
  2. Lecture 12-2: Denominational Oversight and Independent Autonomy
  3. Lecture 12-3: Planting in Persecution and Restricted-Access Contexts
  4. Lecture 12-4: Sustainability and Burnout Specific to Church Planting
  5. Lecture 12-5: Capstone — A Personal Theology and Strategy of Church Planting

핵심만 먼저 보기 ↓

13분

An established church's staff and lay leadership team operates inside a culture that already exists — an accumulated set of norms about how decisions get made, how conflict gets raised, who has authority over what, built up over years and generally not requiring active maintenance to keep functioning day to day. A core team in the first year of a plant has none of that. It is building its culture and doing its actual ministry work at the same time, under real uncertainty about whether the plant will survive, with every team member typically covering multiple roles that would be separate jobs in a larger church. This lecture names those specific pressures directly, because a team that does not recognize them as distinct from ordinary church-staff stress will tend to interpret ordinary early-plant strain as evidence that something has gone specifically wrong, when in fact it is close to the predictable cost of doing this particular kind of work at this particular stage.

이 13분으로 얻는 것

  • Name at least three stresses specific to an early core team that an established church's team does not face in the same degree, and explain why each one is a structural feature of the plant's stage rather than a sign of a team gone wrong.
  • Apply Philippians 2:1-4's call to unity, humility, and other-regard to a concrete conflict scenario on an early core team.
  • Describe at least two concrete practices for maintaining team health specifically under early-plant pressure, distinct from general conflict-resolution advice that would apply to any team.
  • Explain why a team's inexperience with each other, not merely its workload, is itself a source of stress specific to this stage.

If there is therefore any exhortation in Christ, if any consolation of love, if any fellowship of the Spirit, if any tender mercies and compassion, make my joy full, by being like-minded, having the same love, being of one accord, of one mind; doing nothing through rivalry or through conceit, but in humility, each counting others better than himself; each of you not just looking to his own things, but each of you also to the things of others.

Philippians 2:1-4 (World English Bible)

Paul writes this to a congregation, not to a church-planting team specifically, and the passage's next verses (the Christ hymn beginning at verse 5) ground the appeal in Christ's own rather than in any practical team-management principle — this lecture does not collapse that theological weight into a leadership technique. What the passage offers a core team directly, without needing to be stretched, is a diagnostic for exactly the kind of strain this lecture describes: rivalry and conceit are named as the corrosive alternative to unity, and "each counting others better than himself" is named as the practical posture that displaces them. A team under the specific pressures of an early plant — everyone doing multiple roles, no existing culture to defer to, high uncertainty about whether any of it will work — is a team in which rivalry over credit, and self-protective conceit about one's own indispensability, have unusually fertile ground to grow, precisely because roles are undefined enough that anyone's contribution can be second-guessed or claimed by comparison to someone else's.

1. The specific stresses of an early core team

Three pressures distinguish an early plant's core team from an established church's staff or leadership team, and naming them precisely matters because each calls for a somewhat different response. First, there is no existing culture to fall back on. An established church's team, when conflict arises, has years of precedent about how disagreements typically get handled, who typically has final say on what, and what "normal" looks like when things are tense — even an unhealthy precedent gives people something known to react against. A new team has none of this; every difficult moment is simultaneously a real conflict to resolve and an occasion on which the team is inventing, often without realizing it, what its own future culture around conflict will look like. Second, everyone is doing multiple roles, often roles they did not train for and do not feel confident in, which raises the emotional stakes of any critique — a comment about how the makeshift children's ministry space was set up lands differently on a person who is also unpaid, exhausted, and doing three other jobs than the same comment would land on a trained children's ministry director in an established church. Third, there is genuine, sustained uncertainty about whether the whole endeavor will work, which sits underneath every other interaction as background pressure even when nobody names it directly — a level of existential stress an established church's team, whatever its other struggles, does not carry in the same way.

A fourth stress deserves separate naming because it is easy to miss: the team members frequently do not yet know each other well. An established church's leadership team has usually worked together long enough to have calibrated expectations of one another — who tends to go quiet under stress, who needs direct feedback rather than a hint, whose confidence in a meeting does or does not reflect actual certainty. A core team assembled specifically to launch a plant may have known each other only briefly, or only in a different context (a small group, a previous church, a denominational network) before being thrown into the much more demanding and much more exposed work of building something together from nothing. Ordinary interpersonal friction that a longer-tenured team would recognize and absorb without much drama can read, on an unfamiliar team, as a sign that the working relationship itself is broken.

2. What Philippians 2:1-4 names, applied to this specific pressure

Rivalry over credit is a predictable outcome when roles are genuinely undefined and everyone is doing visible, difficult work with little outside recognition — in that environment, comparing one's own sacrifice and contribution to a teammate's becomes an easy, almost automatic way to measure whether the effort is being noticed. Paul's naming of rivalry and conceit as the alternative to unity is not abstract in this setting; it describes a live temptation a core team faces specifically because of its stage, not because its members are unusually prone to pride. The passage's remedy — humility that counts another's interests as worth attending to, not merely one's own — has a concrete early-plant application: a team culture where credit is actively and specifically given out loud (naming, in a team meeting, exactly what a particular person did and why it mattered, rather than only offering generic encouragement) does more to prevent rivalry than any rule against rivalry itself could do, because it removes the scarcity of recognition that rivalry usually feeds on.

3. Concrete practices for health under this specific pressure

A regular, protected rhythm of team check-in that is explicitly not a logistics meeting — a separate time, even briefly, where the question on the table is how people actually are, not what needs to get done before Sunday — counters the tendency of an overloaded team to let relational maintenance be the first thing cut when time is short, which is exactly backward given how much this stage depends on relational trust holding under pressure. A norm of naming conflict early and directly, stated as an explicit team value rather than assumed, matters more on a team with no existing culture to fall back on, because without an explicit norm the default under pressure tends toward avoidance, which lets small friction accumulate into something much harder to resolve later. And a planter's own willingness to name the team's uncertainty and stress honestly, rather than performing confidence the planter does not actually feel, gives the rest of the team permission to be honest about their own strain rather than each person privately concluding they are the only one struggling.

Four pressures an established team does not carry Naming the stage, not blaming the team 1. No existing culture Every conflict also invents how future conflict will be handled — there is no known precedent yet 2. Everyone multi-role Critique of an undertrained, exhausted volunteer covering three jobs lands harder than it would elsewhere 3. Existential uncertainty Whether the plant survives sits under every interaction as background pressure, even unnamed 4. Team members barely know each other Ordinary friction a longer-tenured team would absorb reads as a broken relationship on an unfamiliar one

핵심 요약

  • An early core team has no existing culture, covers several roles, and faces real uncertainty whether the plant will survive. These are features of the stage, not signs of a failed team.
  • A fourth stress is that members often barely know each other, so ordinary friction can look like a broken relationship.
  • Philippians 2:1-4 names rivalry and conceit as the alternative to unity. Undefined roles and little recognition give them fertile ground.
  • Giving credit out loud, naming exactly what a person did and why it mattered, removes the scarcity of recognition that rivalry feeds on.
  • Helpful practices: a regular check-in that is not about logistics, a stated norm of naming conflict early, and a planter who honestly names stress.

Topic: Why the first year of a plant puts special strain on a core team, and how to keep the team healthy.

Remember: Early-plant strain is largely predictable and structural, so name it as such rather than reading it as proof that something has gone wrong.

Caution: Philippians 2:1-4 is written to a congregation, and its theological base is Christ's self-emptying. It is not only a leadership technique. Honest naming should not turn into performing certainty or spreading anxiety.

One line to carry into ministry: Hold a regular check-in about how people really are, and name good work aloud and specifically.

이 과목 요약 전체 보기 →

스스로 확인해 보세요

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

묵상 및 토론

  • Of the four pressures named in this lecture, which do you expect to be the most acute in your own context, and why?
  • Philippians 2:3 names "rivalry" and "conceit" specifically. Where have you seen rivalry over credit emerge on a team doing hard, under-recognized work — and what, concretely, reduced it?
  • This lecture recommends naming a team's uncertainty and stress honestly rather than performing confidence. What is the risk of doing this too much, and how would a planter tell the difference between honest naming and undermining the team's confidence?
  • Design a brief, recurring team check-in practice for a hypothetical five-person core team that is explicitly not about logistics. What single question would you ask every time?

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

다음 단계

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