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.
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 incorporate the Layered Leaderboards approach, inspired by Strava, into my product. The goal is to translate the behavior design principle into a real product flow, not just a standalone UI component. Please suggest how to implement this in the product: • Explain where this pattern should appear in the user journey • Define the behavior it should encourage • Suggest the data, states, and product logic needed to support it • Include user-facing copy that feels calm, respectful, and appropriate for the product context • Identify risks, edge cases, and ways to avoid pressure or manipulation For implementation, propose: • Product flow changes • Required screens or states • Interaction logic • Success and failure states • A lightweight rollout plan for testing whether the pattern improves engagement.