The Kagan Method for Conflict Resolution

The Win Win Discipline model is Spencer Kagan's structured approach to resolving conflicts between people, usually applied in classrooms but totally usable in workplaces or any setting where two parties need to reach a solution without one side dominating. It comes out of his broader Cooperative Learning framework, which he's been refining since the late 1980s. The idea is straightforward on paper: both parties get what they need, no scorekeeping, no compromise that leaves someone unhappy. You start by having each person state their position in their own words, not the other person's version. Then they restate what they heard the other side say, and that other person confirms whether the restatement was accurate. Only after both positions are clearly on the table do you move into brainstorming solutions together. The whole process usually takes between 15 and 30 minutes for a moderately involved conflict, maybe 5 minutes if it's something small like a scheduling disagreement. The key mechanic is that neither person can push a solution until the other person has felt heard. This isn't some soft touch sentiment — it's structural. The format literally won't advance until both restatements are verified. I found this to be the hardest part to enforce in practice, especially when people are tired or emotional.

What Actually Happens When You Try This

Most people assume the rephrasing step is just a formality. It isn't. In my experience, it catches about 60 to 70 percent of conflicts right there, because people realize their position isn't as opposed to the other side as they thought it was once it's spoken out loud and validated. The remaining 30 to 40 percent genuinely need the brainstorming phase, and even then, the structured turn-taking prevents the conversation from derailing into circular arguments. Here's the thing nobody tells you about the Win Win format: it only works when both parties agree to participate. If one person walks away or refuses to restate the other side's position, the whole process breaks down. I've seen this happen more than once, especially in parent-teacher conferences where one party treats the mediation as a performance rather than a problem-solving session. In those cases, the facilitator needs to be prepared to pivot to a simpler directive approach or schedule a follow-up with clearer boundaries.

Practical Problems and Workarounds

I ran into a specific edge case last year that the standard training materials don't address. One of my students would consistently restate the other person's position but add evaluative language — phrases like "she thinks her way is better" or "he's being unreasonable." The other party would immediately react to the loaded language instead of the substance, and the process would stall out within the first two minutes. The workaround was simple enough: I started requiring participants to read their restatements verbatim from a piece of paper. Writing it down forced them to slow down and removed the spontaneous editorializing. It also made the facilitator's job easier because I could catch the evaluative language before it was spoken aloud. Took me about five minutes to adjust the routine, and it completely eliminated that particular failure mode for the rest of the term. Another counter-intuitive detail: the model works best when the conflict is relatively low-stakes. I've noticed diminishing returns on disputes involving deep personal values or long-standing resentments. When the underlying issue is something like shared resources, scheduling, communication style, or procedural disagreements, the Win Win format produces solid results in a single session. When it's a fundamental values mismatch — say, disagreement over fairness in grading or a breach of trust — the structured dialogue surfaces the position but doesn't resolve the root cause. In those cases, you're better off using the format to clarify where the disagreement actually lies, then moving to a different intervention like referral to counseling or administrative mediation.

Get the Full Details

Win-Win Discipline by Spencer Kagan | Goodreads
Win-Win Discipline by Spencer Kagan | Goodreads

What the Model Gets Wrong

The biggest limitation is time. Even a basic Win Win session requires 20 to 40 minutes of focused attention from both parties plus a trained facilitator. In a classroom setting, that means losing a full lesson period. In a workplace, it's taking two people out of productive work for half a day if the conflict is substantive. Some organizations try to compress it into 10-minute fragments, which strips away the restatement verification step and turns the whole thing into a structured argument rather than a resolution process. There's also a cultural assumption baked into the model that both parties value agreement over being right. In environments where hierarchy, competition, or blame are the default operating norms, participants will treat the format as a trap. They'll either game the restatement step by giving inaccurate summaries, or they'll refuse to engage meaningfully and wait for the facilitator to impose a solution anyway. I've seen this in corporate settings where the legal or compliance department was involved — the Win Win process became a recording mechanism for the dispute rather than a path to resolution, which is basically the opposite of what the model is designed for. If you're working in one of those environments, the alternative is to use a modified version that focuses on interest-based bargaining rather than the full Kagan structure. The core principle — separate the people from the problem, focus on interests not positions — is the same, but the delivery is less formal and doesn't require the strict turn-taking protocol. It's faster, less structured, and easier to justify time-wise, though it requires more skill from the facilitator to keep the conversation productive without the scaffolding.

The Spencer Kagan Win Win Discipline model is useful enough to learn, but it's not a universal fix. It does what it says it does under the right conditions, and it fails predictably when those conditions aren't met. Know both outcomes before you invest the time in setting it up.