Break 'everything is priority 1' paralysis with pairwise…
When a category contains more than 7-9 items all claiming equal priority, force binary pairwise comparisons asking 'if I could only accomplish one in the next 90 days, which one?' to produce ordinal ranking.
When This Fires
- When a priority list has 7+ items all marked as "high priority"
- When inability to rank produces paralysis or random task selection
- When strategic planning produces a wish list rather than a priority stack
- Complements Rank values through pairwise comparison — 'If I could only… (pairwise comparison for values) with the task-priority application
Common Failure Mode
Consensus-based equal priority: "The team agrees all 10 initiatives are equally important." They're not — the team just didn't do the hard work of comparing and ranking. Pairwise comparison forces the work: "Marketing launch or product reliability — if we can only advance one in Q2, which?" The discomfort of the comparison is the ranking process doing its job.
The Protocol
(1) When 7+ items claim equal priority, don't attempt global ranking. (2) Use pairwise comparison: take every unique pair (for N items, that's N×(N-1)/2 comparisons) and ask: "If I could only accomplish one of these two in the next 90 days, which?" (3) For each comparison, the winner gets a point. (4) Rank by total points: the item with the most wins is genuinely the highest priority. (5) The 90-day time horizon forces temporal specificity that prevents abstract "both are equally important" responses — you can only do one in 90 days, which? (6) Accept that some comparisons are genuinely close. Record close calls for review. But the final ranking, even imperfect, is dramatically more useful than "everything is #1."