liveBook · Manning

Conflict resolution

As explained in Lead Developer Career Guide

A process for addressing disagreement and reaching an acceptable resolution among conflicting parties.

Conflict resolution is the work of addressing disagreement so a team can move forward together. For a lead developer, the goal is not to look decisive or defend a solution chosen in advance. It is to hear the people involved, understand their concerns, and find a resolution that supports the team’s success. This can feel uncomfortable at first; it takes practice, and no single approach fits every situation. section 3.1.3 section 3.0

When tension appears, use these practical checks:

  • Notice conflict that nobody has reported. Changes in tone, behavior, or body language may signal tension; so may people pursuing separate approaches after agreeing on a plan. section 3.1.3
  • Invite each person to explain their concerns. Listen with an open mind, including when you arrived with a preferred answer. Ask how people feel about the conflict, not only what happened. section 3.1.3 section 11.1.2
  • Keep the discussion constructive. If tension rises, stay composed, avoid a defensive response, acknowledge feelings even when you disagree, and return attention to the problem. section 11.4

A disagreement over project priorities

Suppose developers want to fix an existing codebase before adding features, but the project schedule cannot accommodate all that work. Listening to their frustration does not require accepting every proposed fix. One workable compromise is to fix bugs that directly affect the features being built. section 11.1.2

Some conflicts surface through a difficult conversation about behavior or performance. Prepare the relevant facts, make room for the person’s perspective, and watch for signs of escalation. A performance concern may also have circumstances you cannot see at first: in one case, asking how a team member was doing led to a conversation about personal difficulties and support arranged with human resources. section 11.4

If you tend to avoid conflict, treat that as a skill gap rather than a fixed trait. Avoidance can create more conflict. Seek feedback from team members, look for training, and keep practicing; the aim is progress, not a flawless first mediation. section 10.4.1 section 3.1.3

How Lead Developer Career Guide covers it

How deep it goes
Offers recognition cues and conversation tactics, while acknowledging that situations have no one-size-fits-all solution.
Examples
Uses a feature-versus-bug-fix compromise and a performance conversation that revealed a need for personal support.
What it assumes
Assumes a workplace team context while treating conflict resolution as a leadership skill developed through practice.
What you can do after
Practice conflict resolution by recognizing tension, hearing all sides, managing escalation, and seeking a workable resolution.
How it connects
Connects conflict resolution to emotional intelligence, empathy, active listening, difficult conversations, and de-escalation.

Also explained in

Compare how 4 books explain conflict resolution →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Lead Developer Career Guide. The section links point to the parts of the book it draws on.