Two high Ds: one team, one wheel, two sets of hands on it

Annual planning offsite, whiteboard hour. Your two high Ds have spent twenty minutes politely annexing each other's territory. One has expanded "go-to-market" to include the partnerships pipeline. The other has expanded "partnerships" to include pricing, which was never anyone's to give. Each annexation arrives as a reasonable-sounding bullet point.

The rest of the room has gone quiet, the way rooms do when two strong people negotiate through a facilitator who has not noticed yet. You are the facilitator.

They are not fighting over the roadmap. They are fighting over who steers.

Why this keeps happening

What is happening: Two Ds on one team means two people whose default is to take the wheel. Ambiguity about ownership does not stay ambiguous; it becomes a contest, conducted politely in planning docs and bluntly in decision meetings.

How it feels: You hired two drivers on purpose and you would do it again. But you spend real energy refereeing, and the rest of the team has learned to wait out the weather before committing to anything.

Why it should not be this way: Two Ds is not too many Ds. It is too few territories. Drive scales beautifully when the hills are different; it cannibalises when the hill is shared.

Five questions for your next working session

1. Which decisions are yours alone, theirs alone, and genuinely shared? Keep the shared list under five.
2. Where did you cross the line last month, and was it drift or a land grab?
3. What is the other D carrying that you are glad you do not have to?
4. Which shared decision is currently stuck, and are you stuck on substance or on who decides?
5. What win does each of you want credit for this quarter, by name?

Coaching script

Territory talk, both in the room, map on the wall. Ds respect explicit deals and ignore vibes.

• Say the quiet part: "You are both wired to drive. That is why you are both here. Unsplit territory turns that asset into a contest."
• Draw the map together: every domain gets exactly one owner. Shrink the shared list ruthlessly; shared is where the fights live.
• Set the tiebreak rule for what remains shared: who decides, how fast, no appeals. Ds can lose a decision cleanly; they cannot tolerate an undecided one.

Conflict repair script

For the week one of them annexes anyway. Move fast; territory disputes compound daily.

• Call it what it is, privately, to the one who crossed: "That was a land grab. The map says otherwise. Roll it back or make the case to me, not around them."
• Tell the other one it was handled, specifically. Ds keep score; an unaddressed grab licenses the next one.
• If the grab had merit, redraw the map openly in the next planning session. Lines can move; they cannot be moved silently.

A plan you can start this week

1. Split the territory explicitly. One owner per domain, written, signed by both. Ambiguity is not flexibility here; it is the arena.
2. Install a fast tiebreaker. For genuinely shared calls: who decides, within what deadline. An undecided question is the only thing two Ds cannot leave alone.
3. Give each one a scoreboard. Two Ds sharing credit curdles. Separate wins, named publicly, each quarter. They compete with the market instead of each other.

What happens if you wait

Unmanaged, the contest goes underground: duplicated initiatives, teams asked to pick a sponsor, decisions re-litigated in side channels. Eventually the board notices you have two strategies.

Split well, two Ds is the fastest leadership configuration you can run. Two hills, two drivers, no waiting on anyone.

What you'll see in Team Mode

Department Dynamics turns this page from a read into a tool you put in front of both groups this week. Two teams, plotted on the pace and focus axes, with the working agreement written for both sides.

See Team Mode

Frequently asked

Can two high D personalities work together?

Yes, when the territory is split explicitly and ties get decided fast. Two Ds fail on shared ground and thrive on separate hills. The map has to be written, owned, and enforced.

How do you manage two dominant personalities on one team?

One owner per domain, a ruthless cut of the shared list, a tiebreak rule with a deadline, and separate scoreboards. Ds can lose a decision cleanly; what they cannot tolerate is an undecided one.

What happens when two high Ds clash?

Politely at first: planning docs, annexed bullet points, expanded definitions. Then bluntly. Treat the first land grab as the real event it is, roll it back or ratify it openly, and never let lines move silently.

How do you know a two-D pair is failing?

Decisions are getting re-litigated in side channels. Both have their version of the agreement and neither is updating the canonical doc. The map is no longer trusted, which means it is no longer the map.

Should the two Ds report to each other or peer?

Peer, almost always. Two Ds in a reporting chain creates two contests at once: the territorial one and the hierarchical one. Peer relationships at least keep the contest at one level.

What is the right tiebreaker if there is no shared boss?

A pre-agreed rotation. Odd-numbered shared decisions go to one of them, even-numbered to the other. The rule sounds silly until it ends the third dispute by noon on a Tuesday.

What do two Ds need from the team around them?

Calibration. Direct teammates have to be able to tell each D when they are bulldozing, in private and on the record. Without that signal, the territory map drifts faster than anyone realises.