Layered Leaderboards
Use leaderboards carefully by making comparison specific, filterable, and balanced with personal progress.
In practice: Strava
Layered leaderboards make comparison relevant by splitting rankings across segments, clubs, filters, and timeframes, so users measure themselves against a meaningful field and find a competition they can win. Personal progress sits alongside the ranking.
A relevant comparison set
Segment leaderboards with category filters let users compare on a specific route against a group that feels relevant rather than impossibly broad.
A smaller, winnable arena
A club leaderboard ranks members on aggregate activity, offering a smaller, more winnable arena than a global list.
A concrete benchmark
Challenge progress and its leaderboard show exactly where the user sits, giving a concrete benchmark to improve against.
Ranking with everyday proof
Public activity in the feed adds performance and reactions as context, pairing ranking with everyday social proof.
Why it works
Filters help users compare against a group that feels meaningful, and segmented rankings create multiple ways to succeed. Comparison motivates most when it is specific and fair, and when it is balanced with self-comparison rather than only peer comparison.
How Strava does it
Segmented Rankings
Different routes, timeframes, and communities create multiple ways to succeed.
Clear Benchmark
A ranking gives the user a concrete reference point for improvement.
Behavioral principles
Social Comparison
People use others as signals for how they are doing and what is possible.
Relevant Comparison Set
Filters let users compare against a meaningful group rather than an impossibly broad one.
Status Motivation
Visible rank can motivate extra effort when the user values that arena.
Personal-Best Contrast
Leaderboards work better paired with self-comparison, not only peer comparison.
Design considerations
Offer filters, personal records, and alternative success states so users who will never top a broad ranking still have a way to win. Add integrity checks too, because competitive systems lose trust when they can be gamed.
Implementation prompt
Use the pattern above as the reference, then prototype the same behavior in your own product surface.
I want to use leaderboards carefully in my product. The goal is to make comparison specific and fair enough to motivate, and to keep a way to win for people who will never top a broad ranking. Please suggest how to implement this in the product: • Split rankings by segment, group, timeframe, and filter, so the comparison set feels relevant • Offer smaller, more winnable arenas alongside any global list • Give a concrete benchmark to improve against, not just a position • Pair every ranking with personal-best progress, so self-comparison is always available • Create several distinct ways to succeed rather than one ladder For implementation, propose: • The ranking dimensions and the filters exposed to users • Where leaderboards appear, and where personal progress appears next to them • States for unranked, mid-pack, top, and long-term bottom placement • Alternative success states for users who will never place highly • Integrity checks against gaming, since a competitive system loses trust the moment it can be cheated.