Two high Cs: the most rigorous debate on the team, and the least decided

The schema spec is on version fourteen. Your two high Cs have been debating normalisation strategy in the margins for nine days: citations, benchmark links, a shared appendix one of them built to model the read patterns. It is, without irony, the highest-quality technical writing your team has produced this quarter.

Neither will concede, because neither is wrong. They are optimising for two different futures, both plausible, and each new comment raises the standard of the disagreement without moving it an inch.

Nine days of your two most careful minds, spent producing a document about why nothing has shipped. That is the bill, and it arrives every week they remain tied.

Why this keeps happening

What is happening: Two Cs share the standard of proof but not the same priors. Each can meet the other's evidence bar indefinitely, so the debate never runs out of fuel, and deferring to the other feels like abandoning rigour itself.

How it feels: You keep waiting for them to converge because the debate is so plainly intelligent. Intelligence is not the missing ingredient. A verdict is.

Why it should not be this way: Rigour is a way of preparing decisions, not a substitute for making them. Two Cs need an agreed tiebreaker the way two Ds need a territory map: not as a failure of character, as a property of the pairing.

Five questions for your next working session

1. What would have to be true for the other person’s position to be right? Write it down before debating again.
2. Which of our agreed decision criteria does this dispute actually hinge on?
3. What is the cost per week of remaining undecided, in concrete terms?
4. What experiment would settle this in days instead of comments, and why have we not run it?
5. Whose decision is this, by our rotation, and when is it due?

Coaching script

Install the machinery while they are not mid-debate. Two Cs will honour any process they helped specify, precisely.

• Honour the rigour first: "This is the best technical argument on the team. The problem is not the quality of the debate; it is that nothing ends it."
• Agree the decision criteria in advance, with both of them drafting: what we optimise for, in what order, when values conflict.
• Set the verdict mechanism: a page limit, a deadline, rotating decision rights, and the dissenter’s risk register shipped inside the decision doc. Dissent gets recorded, not relitigated.

Conflict repair script

For the stalemate already in progress, the one currently on version fourteen.

• Freeze the document: no more comments. Each writes one page: recommendation, top three risks, the evidence they consider decisive.
• Decide within a day, in person, against the agreed criteria, and name what tipped it. Two Cs accept a reasoned verdict; what they cannot accept is a coin flip dressed as one.
• Ship the dissent: the other C’s risk register goes into the decision doc verbatim, with their name on it. Being on the record is what conceding needed to feel like.

A plan you can start this week

1. Agree the criteria before the dispute. What this team optimises for, in what order. Half of every C-versus-C stalemate is a hidden disagreement about the ranking, not the evidence.
2. Cap debates with a verdict mechanism. Page limit, deadline, rotating decision rights. The debate prepares the decision; it does not replace it.
3. Record dissent instead of relitigating it. The losing analysis ships inside the decision doc with full credit. It converts conceding from a defeat into a contribution.

What happens if you wait

Unmanaged, the pairing converges on the one thing both can agree on: deciding nothing. Dependencies stack up behind their open questions, faster teams route around them, and two of your best minds become the place where roadmaps go to wait.

With criteria and a tiebreaker, two Cs produce the most defensible decisions in the company, complete with a pre-written risk register for everything that might go wrong. That document is worth its weight the first time something does.

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 C personalities work together?

Superbly, on everything except calling the vote. Each can meet the other’s evidence bar forever, so debates need machinery: agreed criteria, a page limit, a deadline, and rotating decision rights.

Why do two high Cs take so long to decide?

Because conceding feels like abandoning rigour, and both positions usually are defensible. The fix is recording dissent inside the decision doc, so conceding becomes a contribution instead of a defeat.

What are two high Cs best at together?

Decisions that have to survive scrutiny: architecture, security, compliance, anything audited later. Give them the verdict machinery and you get rigour at shipping speed.

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

The doc grows, the version number climbs, and dependencies pile up behind their open questions. When the doc has become more impressive than the decision, you are watching the failure mode in slow motion.

Should two Cs lead an audit or a compliance project?

Yes; nobody you employ will produce a defensible artefact faster. Give them the verdict machinery up front or the artefact will be defensible and late.

Can two Cs run a research function?

Beautifully, with one external commitment per quarter that ships regardless. Without that commitment, the function becomes the place where roadmaps wait.

What do two Cs need from their manager?

A real tiebreaker. Not a vote, not a coin flip, not a vague preference; a reasoned call against the criteria they themselves wrote. Two Cs accept reasoned verdicts and reject everything else.