Pairwise Comparison

Ranking a set of options holistically forces an unstable judgment: "rank these six from best to worst" or "score each from 1 to 10" demands a fixed internal scale and a memory of how earlier items were scored, and that scale wobbles. Pairwise comparison replaces the one hard holistic ranking with a series of isolated two-item judgments. For every pair it asks the single easier question - which of these two is better? - then tallies each item's wins into a matrix and reads the ranking off the tally. The durable move is psychophysical: a person (or an agent) holds a far more stable signal for "A beats B" than for "A is a 7," because the binary judgment needs no absolute scale and no criteria axis. The matrix also exposes its own quality - a cycle (A beats B, B beats C, C beats A) is a visible inconsistency to revisit, not a hidden error.

The output is a binary-vote comparison matrix: every pair judged A-beats-B, the derived ranking (each option's win count, ties broken by head-to-head), and a consistency check that surfaces any cycles. There is deliberately no criteria column and no absolute score. This is the narrow, honest reading of the technique - rank when you cannot score - and it is scoped precisely to the case the weighted-matrix skills disclaim.

When to Use

• Items must be ordered, but no one can defend a 1-to-10 scale and the criteria that would justify a score genuinely cannot be articulated (qualitative artifacts - writing samples, design submissions, shortlisted proposals - where holistic marking is noisy).
• The decision-maker can reliably say "this one beats that one" for any pair, even though they cannot say "this one is a 7."
• The set is small enough to compare every pair by hand (roughly up to 6-8 items; the full set is n(n-1)/2 judgments - 15 for six items, 28 for eight).
• A surfaced cycle (an intransitivity) would be useful information - a prompt to re-examine two judgments - rather than noise to suppress.

When NOT to Use