The Good Fight Summary: Make Team Conflict Productive

Key Ideas

1. Name the decision that avoidance keeps postponing

Conflict debt is useful as a lens for work that remains unsettled after people stop discussing it. A team can defer the same tradeoff through optimistic language, private workarounds and promises to coordinate better. The first practical task is to identify the decision underneath the recurring friction. A complaint about attitude may be covering a resource or priority question that nobody has owned.

In the original example, sales promises a customer date before delivery confirms capacity. The teams repeatedly discuss communication, yet the pattern continues. The unresolved decision is how a customer commitment becomes authorized when demand exceeds available capacity. Naming that question changes the conversation. The teams can examine the approval route, the escalation point and the consequence of making an early promise.

Before a meeting, write what keeps recurring and which choice has not been made. Keep the wording about the work rather than a broad accusation about either team. Ask who owns the decision and what information that person needs. This matters because a vague discussion can consume time without reducing the debt. A specific decision gives the conflict a legitimate purpose. It also prevents avoidance from appearing cost-free: somebody is already absorbing the uncertainty through overtime, disappointed customers or repeated replanning. Describe the actual consequence you can verify, and use it to explain why the issue deserves a clear response now.

2. Validate the concern without accepting every proposed solution

Validation appears in Davey's identified conversation sequence. A practical application is to recognize the legitimate concern behind a position before debating the remedy. A person can have a valid pressure and an unworkable request at the same time. Acknowledging the pressure helps separate the person's responsibility from the particular solution they currently advocate.

In the sales-and-delivery illustration, sales worries that a slow answer will lose the customer. Delivery worries that an unsupported date will create a broken promise. Each concern is understandable. Stating both does not mean the team can satisfy every demand or that the premature commitment was appropriate. It creates a clearer basis for discussing an option, such as a rapid capacity check before a date is confirmed.

Use language tied to the specific concern. Avoid a formulaic acknowledgment followed immediately by a dismissal that shows you did not engage with it. Ask the person to correct your understanding if necessary. Do not validate a factual claim you have not checked merely to calm the discussion. This matters because productive conflict needs people to feel that the tension they represent is being understood accurately. It does not require false agreement. Once the concern is clear, state the constraint or expectation that must also be met. The conversation can then focus on how to handle both responsibilities, rather than forcing one person to defend why their concern deserves to exist.

3. Ask questions that reveal the specific tradeoff

The question part of the sequence should produce information relevant to the disagreement. General curiosity can be pleasant while leaving the choice untouched. A useful question identifies the condition, assumption or consequence that makes the current positions hard to reconcile. It should be answerable without requiring someone to defend their entire team.

For the original customer-date dispute, ask what minimum delivery would preserve the customer's opportunity and what work must move to create that capacity. Sales may discover that the customer needs only one part of the proposed service by the early date. Delivery may discover that a smaller initial commitment is possible if another priority changes. Neither answer should be assumed before the question is asked.

Prepare questions about scope, timing, authority and consequence. Distinguish a hard constraint from a preference where the facts allow it. Avoid using a question as an accusation, such as asking why another team never considers the business. This matters because cross-functional conflict often reflects different information and incentives. Better questions make those differences visible enough to manage. If the answers reveal a tradeoff the participants cannot authorize, identify the decision owner instead of continuing to argue as though either side can solve it alone. A productive question can therefore lead to a clearer escalation as well as a local solution. Its value is the improved decision route, not the appearance that everyone has become more agreeable.

4. Pivot toward an option while preserving the unresolved concern

Pivot is the third element in the author-identified sequence. In this guide's application, it means moving from understanding the tension toward a useful next decision. It should not become a polite way to change the subject before the concern is addressed. The option needs to connect to what the conversation has actually revealed.

In the sales-and-delivery case, the participants might propose a short capacity check with an agreed response time and a named escalation owner. That option responds to sales's need for speed and delivery's need for a reliable commitment. If capacity remains insufficient, the next step is a priority decision or a smaller offer, not a promise that both teams will try harder. State what the option resolves and what remains open.

Before closing, compare the proposal with each concern that was validated. Ask whether a critical constraint has been lost during the search for compromise. Avoid dividing the difference automatically when the underlying requirement cannot be split. This matters because a constructive tone does not make an option workable. A useful pivot keeps the conversation moving while preserving accuracy about the tradeoff. Name an owner, timing and a way to report risk. If no acceptable option is available, state the disagreement and the appropriate next decision route. Explicit unresolved conflict is often more manageable than apparent agreement that quietly transfers an impossible commitment to someone who was not in the room.

5. Make necessary disagreement part of planning rather than an emergency

The book's productive-conflict focus invites a broader practice change: give competing demands a routine place in planning. If a team only discusses tradeoffs after a promise fails, every conflict begins with accumulated frustration. A regular opportunity to test assumptions can keep the disagreement closer to the work and reduce the need for personal blame.

In the original example, a planning meeting can include a brief check on which customer commitments exceed current capacity and which decision is needed before a date is offered. The purpose is not to make every meeting argumentative. It is to surface the tension at the point where the team still has options. The chair should make it possible for relevant roles to raise concerns without having to interrupt a nearly finalized plan.

Choose one recurring question that reveals a meaningful tradeoff. Invite the people who have information and clarify who decides. Avoid rewarding only enthusiastic agreement if you also expect people to identify risk. This matters because a conflict habit is shaped by the response to an inconvenient answer. Thanking someone for a concern while repeatedly ignoring it teaches a different lesson from examining it and making a clear choice. Review whether the practice changes the decision process: are commitments more understandable, are risks raised earlier and is ownership clearer? Use concrete observations rather than claiming that all conflict debt has disappeared because a new meeting question was added.