Most leaders are conflict-avoidant. Instead of running from tension, view it as a data point signaling an unaddressed issue or misalignment. This reframes conflict from a threat into an opportunity for discovery and improvement, prompting curiosity rather than fear.

A team that "gets along" isn't one that agrees on everything initially; immediate consensus is a red flag. True alignment comes from respectful, data-driven debate, followed by a unified commitment to the final decision.

Similar to technical debt, "narrative debt" accrues when teams celebrate speed and output while neglecting shared understanding. This gap registers as momentum, not risk, making the system fragile while metrics still look healthy.

The Artemis co-founders maintain high velocity by minimizing disagreements. When they have differing opinions, the person who has thought less deeply about the specific issue defers to the one with more context. This is built on a foundation of mutual trust and recognizing most decisions are reversible.

To foster productive debate, teams must move beyond simply encouraging disagreement. Implement specific, pre-agreed rules of engagement, such as using a neutral mediator or applying a 'two-minute rule' that grants a person uninterrupted speaking time. These protocols transform potential fights into structured, truth-seeking conversations.

Instead of escalating disagreements, Atlassian's founders operated on a simple principle: if one couldn't be persuaded that an idea was good, it was likely not worth pursuing. This served as a critical decision-making filter and prevented major conflicts.

When a critical technical decision is stalled, force a resolution with a timed design competition. Split all relevant tech leads into two competing teams and give them a few hours to independently architect a solution. This quickly reveals areas of consensus and isolates points of disagreement.

The primary bottleneck to organizational speed isn't how fast individuals work; it's decision latency—the time it takes for decisions to be made and flow through the organization. This stems from unclear decision rights, poor communication, or lack of empowerment. Reducing this latency is the key to accelerating engineering and overall business velocity.

Most conflicts between PMs and architects aren't truly technical. They stem from a lack of three crucial, vulnerability-based conversations: 1) What does success look like for you in your role? 2) What is your biggest fear? 3) How can we disagree productively?