Conflict
Conflict is a state of disagreement, opposition, or incompatibility among people, positions, interests, actions, or information.
Collaborative Software Design: How to facilitate domain modeling decisions
A conflict is a state of disagreement or opposition between people or positions within a group.
- How it is used
- Surfaces disagreement as a facilitation concern that affects shared models and software design decisions.
- How deep it goes
- Explains observable patterns, learning opportunities, conflict types, and facilitation heuristics without reducing behavior to fixed motives.
- Examples
- Uses BigScreen design discussions, edge behavior, gossiping, and EventStorming facilitation scenarios.
- What you can do after
- Practice neutral observation, classify conflict, invite perspectives, and de-escalate conversations without taking over resolution.
Think Like a Software Engineering Manager
Conflict is a disagreement or opposition between people arising from incompatible interests, interpretations, expectations, or goals.
- How it is used
- Uses conflict management to protect trust, team cohesion, project execution, and progress toward shared goals.
- 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 you can do after
- Apply facilitation, coaching, shared-goal alignment, and decision-authority practices to diagnose and resolve workplace disagreements.
Read how Think Like a Software Engineering Manager explains conflict →
Interview Speak
A conflict is a disagreement or incompatibility between people, groups, or interests that requires resolution or management.
- How it is used
- Tests whether applicants can manage interpersonal problems positively and remain effective collaborators.
- How deep it goes
- Provides a procedural answer framework: context, root-cause questions, listening, de-escalation, compromise, and results.
- Examples
- Uses a sales-territory dispute and prompts for project, deadline, priority, mediation, and team-disagreement stories.
- What you can do after
- Practice/perform it by delivering a specific conflict-resolution answer that shows de-escalation and results.
Lead Developer Career Guide
A disagreement or incompatibility between people, interests, expectations, or positions.
- How it is used
- Guides lead developers through recognizing, discussing, and resolving team conflict while protecting collaboration and team success.
- How deep it goes
- Explains recognition, listening, mediation, compromise, and follow-through through workplace scenarios, but stops short of a formal conflict-resolution framework.
- Examples
- Uses nonverbal tension, independent team approaches, a health-related absence, missed deadlines, and respectful disagreement as teaching examples.
- What you can do after
- Practice/perform conflict resolution by noticing tension, hearing all sides, holding difficult conversations, and developing mutually workable plans.
Related concepts
- conflict resolutionaddressed by · Conflict resolution is the process of addressing incompatible positions, decisions, or changes to reach an acceptable and consistent outcome.
- collaborationaddressed by · Collaboration is coordinated activity in which multiple participants contribute toward a shared goal or outcome.
- dysfunctional conflictincludes · A harmful conflict centered on interpersonal emotions or relationships that impedes collaboration, progress, or outcomes.
- interviewused by · An interview is a structured or semi-structured conversation in which questions elicit information about a participant’s experiences, views, needs, qualifications, or requirements.
- signalkind of · A signal is an observable value, event, or pattern that conveys information about a condition, state, or phenomenon.
- resistance to changeincludes · Resistance to change is opposition or reluctance to adopt or participate in a change to established practices, processes, structures, or ways of working.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.