liveBook · Manning

Conflict

As explained in Think Like a Software Engineering Manager

Conflict is a disagreement or opposition between people arising from incompatible interests, interpretations, expectations, or goals.

Conflict is disagreement or opposition caused by incompatible interests, interpretations, expectations, or goals. At work, diverse perspectives make conflict natural; managed well, it can improve decisions and collaboration. section 3.1.3 section 9.3.2

Manage workplace conflict by:

  • Keep discussions data-driven, prevent dominance, and give each person space to explain their perspective. section 3.1.3
  • Ask about effort, timelines, reusability, constraints, and resource allocation instead of defending personal preferences. section 3.1.3
  • Reconnect disagreements to shared goals, project road maps, and long-term outcomes. section 9.3.2
  • Assign a project authority or directly responsible individual whose decision is final when consensus cannot be reached. section 9.1.5 section 9.3.2
  • Separate the issue from personal identity: pause, seek understanding, explore another communication method, and find common ground. section 11.2.3
  • Set explicit goals and regular check-ins when coaching behavior or using a mentoring relationship to repair team dynamics. section 3.1.4

Choosing a promotions tool

Jack favored building a new promotions interface for control and backend management. Jamie preferred an existing internal tool for familiarity and faster sales onboarding. After separate coaching conversations and questions about cost, timing, reuse, and resources, the team reached consensus. Transparency about prioritization then helped rebuild trust. section 3.1.3

Figure 3.1 Bring a neutral party to help build alignment in times of conflict.
figure

A neutral party can help conflicting participants build alignment when direct discussion has stalled. section 3.1.3

How Think Like a Software Engineering Manager covers it

How deep it goes
Provides intervention steps, coaching tactics, authority assignment, and examples, but stops short of formal conflict-resolution theory.
Examples
Uses technical design disputes, cross-functional document disagreements, dismissive behavior, and defensive reactions to feasibility questions.
What it assumes
Assumes workplace collaboration and team leadership, while teaching beginners how to intervene, listen, coach, and depersonalize disagreements.
What you can do after
Apply facilitation, coaching, shared-goal alignment, and decision-authority practices to diagnose and resolve workplace disagreements.
How it connects
Connects conflict with consensus, decision-making, trust, transparency, shared goals, feedback, mentoring, and cross-functional collaboration.

Also explained in

Compare how 4 books explain conflict →

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Think Like a Software Engineering Manager. The section links point to the parts of the book it draws on.