Two High-D Leaders on One Team: How to Stop the Collision

One High-D raises the pace. Two High-Ds raise the pace and the body count if you do not design the interface.

This is common in founder pairs, sales + product duos, and hospitals or clinics where two strong attendings share authority.

What the collision looks like

• Meetings become parallel monologues
• Decisions get re-litigated in Slack after the meeting
• The team learns to wait for "who won today"
• Speed increases while trust decreases

Neither leader is "the problem." The missing artifact is.

Interfaces that work

1. Domain ownership on one page.
   Who is final call on product, revenue, people, brand, clinical quality? Ambiguity is gasoline.

2. Decision SLA.
   If we disagree, we decide by time T with a tie-break rule. Endless "alignment" is just delayed dominance theater.

3. Private disagreement, public unity.
   Fight hard behind the door. Exit with one message. Teams can handle hard truths. They cannot handle two captains pointing different directions.

4. A third instrument.
   A High-C operator, a board chair, or a written metric that both accept as referee. Two Ds without a referee invent politics.

Language for the hard conversation

"I respect your drive. When we both push without a lane, the team freezes. I want us dangerous to the market, not to each other. Can we write lanes and a tie-break this week?"

If you are the High-D reading this

Your instinct is to win the interface design too. Resist turning process into another conquest. The goal is shared velocity, not dominance over your co-lead.

If you co-lead with another High-D, schedule a 45-minute lane meeting this week. Write the ownership map. Your team is already paying for the absence of that page.