FREE

Course certificates are free until March 31, 2027.

LM403E Building a Ministry Team

Lecture 6-3: Naming What Isn't Working

View as cards (3 min)
Contents 41
LM403E Building a Ministry Team
Chapter 0 · Introduction: Why a Team, Not Just Yourself
  1. Introduction: Why a Team, Not Just Yourself
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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
Chapter 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

Jump to the key points ↓

13 min

Most leaders know, in the abstract, that a real problem should eventually be named. Far fewer actually do it — plainly, specifically, to the person's face, without an audience and without softening the substance into something so vague it can be nodded past. Galatians 2:11-14 records the moment Paul did exactly that to Peter, a senior apostle, over a real and serious inconsistency, and the relationship and the shared mission survived the correction. This lecture asks what made that possible.

What these 13 minutes give you

  • Describe what Peter actually did at Antioch, and why Paul judged it serious enough to require direct correction.
  • Identify the specific features of Paul's correction — where, how, and to whom it was addressed — that distinguish it from gossip, vagueness, or public humiliation.
  • Explain why naming a real problem plainly is different from naming it harshly, and why both softening and escalating a correction can fail the same underlying goal.
  • Practice drafting one specific, observation-based statement of a real problem on your own team.

But when Peter came to Antioch, I resisted him to his face, because he stood condemned. For before some people came from James, he ate with the Gentiles. But when they came, he drew back and separated himself, fearing those who were of the circumcision. And the rest of the Jews joined him in his hypocrisy; so that even Barnabas was carried away with their hypocrisy. But when I saw that they didn't walk uprightly according to the truth of the Good News, I said to Peter before them all, 'If you, being a Jew, live as the Gentiles do, and not as the Jews do, why do you compel the Gentiles to live as the Jews do?'" — Galatians 2:11-14

World English Bible

Read the sequence carefully. Peter had been eating freely with Gentile believers — living out, in practice, the truth that in Christ there is no wall between Jew and Gentile. Then men associated with James arrived, and Peter, out of fear of "those who were of the circumcision," began withdrawing from the very table fellowship he had been practicing. This was not a minor social slight. Paul calls it hypocrisy, and names its cost precisely: it was compelling Gentile believers, by Peter's visible example, to live as though they needed to become Jewish to be fully accepted — a direct contradiction of the gospel both men actually believed.

1. What made this correction necessary rather than optional

It would have been possible for Paul to let this go. Peter was senior to him in the church's public standing. The withdrawal was, on its face, a matter of table fellowship — who eats with whom — rather than an explicit doctrinal statement. And correcting Peter carried real relational and reputational risk: Paul was a newer, more controversial figure confronting one of the original twelve.

Paul did not let it go, because the stakes were not actually about table manners. Verse 14 names the real cost: Peter's visible withdrawal was functioning to "compel the Gentiles to live as the Jews do" — pressuring Gentile believers, through the example of a respected leader, toward a false gospel of required conformity. And it was not only Peter. "The rest of the Jews joined him in his hypocrisy; so that even Barnabas was carried away" — meaning the problem was actively spreading through the community by imitation, not staying contained to one man's private choice. A leader's example carries weight precisely because people follow it, and Peter's example, left uncorrected, was teaching something false by demonstration even while Peter himself, presumably, would have denied believing it.

This is the test worth applying before deciding whether something on your own team needs to be named: is this actually shaping what other people believe or do, through visible example, in a direction that matters — or is it a preference, an irritation, a style difference that does not actually mislead anyone? Paul was not policing Peter's personal comfort. He was correcting a visible act that was teaching the wrong thing by example.

2. The specific shape of the correction

Three features of verses 11 and 14 do real work and are worth naming separately, because a correction missing any one of them tends to fail differently.

"I resisted him to his face." Not behind his back. Not through a letter to a third party, and not through a quiet word to others in the community that Peter's example was troubling. Paul went directly to Peter. Whatever discomfort this cost either man, it is the only version of correction that gives the other person a genuine chance to hear the concern directly and respond to it directly, rather than discovering it secondhand, distorted by however many people relayed it.

"Before them all." This detail is easy to read as public shaming, and worth pausing on, because Paul's own account gives the reason: the hypocrisy itself had already been public and visible — Peter's withdrawal from Gentile table fellowship had been witnessed and was already shaping other people's behavior, Barnabas's included. Correcting a visible, already-public action privately would have left the actual damage — other believers' false impression of what the gospel required — completely unaddressed. The correction matched the scope of what needed correcting. It was not privacy sacrificed for spectacle; it was a public wrong requiring a correction visible to the same audience that had witnessed the wrong.

Specific, not vague. Paul does not say Peter has "been struggling lately" or that "some things haven't felt right." He states the exact behavior — eating with Gentiles, then withdrawing under pressure — and the exact contradiction it produced. A leader who cannot state a problem this specifically has usually not yet done the work of figuring out what, precisely, is actually wrong.

3. Why the relationship and the mission survived

Nothing in Galatians suggests Paul and Peter's working relationship ended here, or that the church at large treated this as a scandal ending either man's ministry. Paul's correction was plain, specific, and public in proportion to the public nature of the offense — but it was not personal destruction. He named the behavior and its cost. He did not attack Peter's character wholesale, question his salvation, or attempt to strip him of standing. The correction was sized to the actual problem, not inflated into a referendum on the man.

This is the distinction worth carrying forward: naming a real problem plainly is not the same thing as naming it harshly. A leader who softens every correction into vague, deniable language protects nobody — the problem persists, uncorrected, because it was never actually stated. A leader who escalates every correction into a character attack destroys more than the problem requires, and teaches the team that naming any issue means risking total relational rupture, which guarantees the next real problem stays unnamed even longer. Paul's model sits between both failures: direct, specific, proportionate, and aimed at correcting the actual behavior rather than winning or wounding.

4. Drafting a specific, observation-based statement

The skill this lecture teaches has a concrete form: state the specific observed behavior, state its specific cost or effect, and say it to the person, not about them. "You've seemed distant lately" is not this. "The last three Sundays, you arrived after the service started without letting anyone know in advance, and the team had to reassign your part with no notice" is this. The second version can actually be responded to. The first can only be denied, deflected, or vaguely apologized for without anything changing.

Lecture 6-5 will ask you to draft exactly this kind of statement for a real, current situation on your own team. This lecture's job is to make sure you understand why the specificity matters before you try to produce it.


Diagram 1. Galatians 2:11-14 — the shape of the correction

Galatians 2:11-14 -- Three Features That Made It Work Missing any one of these tends to fail in a different, predictable way To his face Directly to Peter, not through a third party. Missing this = gossip, not correction. Before them all Matched to the scope of an already-public wrong. Missing this = the visible damage stays uncorrected. Specific behavior Named exactly: eating, then withdrawing under pressure -- and its cost. Missing this = vague, deniable, unchangeable. Plain is not the same as harsh Paul named the behavior and its cost. He did not attack Peter's character wholesale. The relationship and the shared mission survived the correction because it was proportionate.

In short

  • Peter's withdrawal from Gentile table fellowship under pressure was not a minor social matter — it was, by example, compelling Gentile believers toward a false requirement, and it was already spreading by imitation to others, including Barnabas.
  • Paul's correction had three specific features: directly to Peter's face, proportionate in scope to an already-public wrong, and specific about the exact behavior and its cost.
  • Plain correction is not the same thing as harsh correction — Paul named the behavior, not a wholesale attack on Peter's character or standing.
  • Softening a correction into vagueness leaves the actual problem uncorrected; escalating it into a character attack destroys more than the problem requires and teaches the team to avoid naming issues at all.
  • A specific, observation-based statement names the exact behavior and its exact cost, addressed to the person — not a vague impression addressed about them.
Front Back
What made it serious Peter's example was compelling Gentile believers toward a false gospel requirement, and it was spreading by imitation.
Three features of Paul's correction To his face, proportionate to an already-public wrong, specific about the exact behavior and its cost.
Plain vs. harsh Naming the behavior specifically is not the same as attacking the person's character wholesale.
A usable correction States the exact behavior, its exact cost, addressed to the person -- not a vague impression addressed about them.

★ One sentence to remember A correction vague enough to be denied has not actually named the problem.

✓ This week's action Write down, in one specific sentence, a real issue on your team you have so far only named vaguely or not at all.

Review every summary in this course →

Check yourself

Not "did you read it" but "can you explain it". Ticks are kept on this device only.

Reflection and discussion

  • What made Peter's withdrawal at Antioch a matter serious enough to require direct correction, rather than something Paul could reasonably have let go?
  • Paul corrected Peter "before them all." Why does the text's own account of the offense's public, already-visible nature make this proportionate rather than a public shaming?
  • Think of a correction you have given or received that was vague rather than specific. What made it possible to deny, deflect, or agree with in words without anything actually changing?
  • This lecture distinguishes "plain" from "harsh." Which failure is more natural for you — softening a correction into vagueness, or escalating it into a character attack?
  • Name one real, current issue on your team you have been naming vaguely, if at all. What would a specific, observation-based version of that statement actually say?

Sign in to write and keep your answers

What next

The lecture ends here. What follows was written by its readers.