Lecture 6-4: Team Health and Conflict in the Early, High-Pressure Season
The first year of a plant strains a team in predictable ways, so name the strain and keep the team healthy.
Church Planting: Theology and Practice
Swipe or use the arrow keys →
Course certificates are free until March 31, 2027.
The first year of a plant strains a team in predictable ways, so name the strain and keep the team healthy.
Church Planting: Theology and Practice
Swipe or use the arrow keys →
An established church's team works inside a culture built over years. A core team in a plant's first year has none of that. It builds its culture while doing the work, under real uncertainty about whether the plant will survive, with each member covering several roles. A team that does not see these pressures as distinct may read ordinary strain as proof that something has gone wrong.
The lecture says Paul wrote this to a congregation and grounds it in Christ's self-emptying. It uses the passage as a diagnostic: rivalry and conceit are the alternative to unity, and counting others better than oneself is the posture that displaces them.
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.
First, there is no existing culture, so every hard moment is also the team inventing its future way of handling conflict. Second, everyone does several roles they may not feel confident in, which raises the emotional stakes of any critique. Third, sustained uncertainty about whether it will work sits under every interaction as background pressure.
An established leadership team has usually worked together long enough to know who goes quiet under stress and who needs direct feedback. A core team may have known each other only briefly. Ordinary friction that a long-serving team would absorb can read, on an unfamiliar team, as a sign that the relationship itself is broken.
When roles are undefined and everyone does hard, visible work with little outside recognition, comparing one's sacrifice to a teammate's becomes an easy habit. Paul's naming of rivalry and conceit describes a live temptation of this stage, not a sign that these people are unusually proud. Giving credit out loud, naming exactly what a person did and why it mattered, removes the scarcity of recognition that rivalry feeds on.
A regular time that is not a logistics meeting, where the question is how people actually are.
State it as a team value to name conflict early and directly, since avoidance is the default under pressure.
A planter who names the team's uncertainty and stress honestly, instead of performing confidence, lets others admit their own strain.
The lecture treats the strain of this stage as structural, not as evidence of failure.
Which of the stresses, no culture, many roles, uncertainty, or unfamiliar teammates, is hardest on your team, and what one practice would help?
Early-plant strain is largely predictable and structural, so name it rather than reading it as proof that something has gone wrong. Hold a regular check-in about how people really are, and name good work aloud and specifically.
These cards are a short preview. Your reading is recorded only when you read the full lecture, and the chapter quiz and the exams test what the full lecture teaches.