A curated collection of psychological models, communication frameworks, and management strategies designed to help new engineering managers navigate interpersonal disputes, technical disagreements, and team friction to maintain a healthy, high-velocity development environment.
Get targeted exposure with custom position pinning and highlighted placement.
A framework for handling high-stakes discussions where opinions vary and emotions run strong. It teaches managers how to create psychological safety, identify the 'pool of shared meaning,' and move conversations from conflict to productive action.
A diagnostic tool that identifies five conflict-handling styles: competing, collaborating, compromising, avoiding, and accommodating. It helps managers understand their natural tendencies and choose the most effective approach based on the situation's urgency and importance.
Developed by Marshall Rosenberg, this framework focuses on four steps: observation, feeling, need, and request. It is particularly effective for engineering managers to separate objective technical facts from emotional reactions during peer review conflicts.
A management philosophy that encourages 'challenging directly' while 'caring personally.' This framework prevents the toxicity of obnoxious aggression and the inefficiency of ruinous empathy, ensuring technical debt and performance issues are addressed honestly.
A mental model that illustrates how humans jump from raw data to conclusions and actions. Managers can use this to help engineers backtrack through their assumptions and discover where a misunderstanding began during architectural disputes.
A method that separates the people from the problem by focusing on underlying interests rather than rigid positions. It encourages engineers to collaborate on a shared goal rather than fighting for a specific implementation detail.
Standing for Situation, Behavior, and Impact, this framework provides a structured way to deliver corrective feedback. It minimizes defensiveness by focusing on observable actions and their tangible effects on the project or team.
A communication tool involving Describe, Express, Specify, and Consequences. It provides a clear script for managers to address disruptive behavior or performance gaps without escalating the emotional tension of the encounter.
A foundational framework for creating an environment where team members feel safe to take risks and admit mistakes. This reduces conflict stemming from fear and replaces it with constructive dissent and innovative problem-solving.
A model by Patrick Lencioni that identifies a pyramid of team failure, starting with a lack of trust. It provides a roadmap for managers to move from artificial harmony to productive ideological conflict.
A set of techniques including mirroring, paraphrasing, and empathetic labeling. This ensures that engineers feel heard and understood, which often diffuses emotional escalation before a technical solution can be negotiated.
While often used for time management, this matrix helps managers decide which conflicts require immediate mediation (Urgent/Important) and which can be handled via asynchronous processes or ignored to avoid micromanagement.
Standing for Goal, Reality, Options, and Will, this coaching framework helps managers guide conflicting employees to find their own solutions. It shifts the manager from 'judge' to 'facilitator' during interpersonal disputes.
A specialized extension of Crucial Conversations that focuses on what to do when people don't do what they said they would. It is essential for managing missed deadlines and broken commitments in agile environments.