Condorcet Paradox

You're seeing it when a board prefers Strategy A over B, Strategy B over C, and Strategy C over A — cycling through options without converging because the voting order determines the winner, not the underlying preferences.

You're seeing it when a product team can't reach consensus on feature priorities because every proposed ranking loses to another in pairwise comparison — the group's preferences form a loop rather than a list.

You're seeing it when legislative outcomes depend on the order in which amendments are voted on, with savvy politicians engineering the agenda to produce their preferred result from an otherwise cyclical set of preferences.

When your leadership team keeps revisiting the same strategic debate without resolution, the Condorcet Paradox may be operating. Rather than holding another vote, either narrow the options to two, assign a single decision-maker, or use a scoring system that avoids pairwise traps.

Franklin navigated the Constitutional Convention of 1787, where delegates' preferences on representation, slavery, and federal power formed exactly the kind of cyclical conflicts the Condorcet Paradox describes. No simple majority vote could have resolved the competing priorities. Franklin's contribution was recognizing that procedural design — committees, compromises, bundled proposals — mattered as much as the substance. He brokered the Great Compromise not by finding a majority-preferred option but by restructuring the choice architecture to break the cycle. For founders facing teams that can't converge on a decision, Franklin's lesson is clear: when preferences cycle, change the process, not the people.