Community Building
Build community by giving individual actions a shared place to be seen and discussed.
In practice: Strava
Community features give individual effort a shared place to be seen and discussed. By surrounding a tracked activity with clubs, events, feeds, and kudos, the product turns solo progress into a social object, and belonging becomes a reason to keep going.
A shared space
A club page and activity feed give members a shared space where individual activities become something others can see and react to.
Real-world plans
Club events show attendee counts and join actions, turning the group into concrete plans rather than a passive list.
Finding your group
Club search and discovery, filtered by location and sport, help users find a group that makes the network feel relevant to them.
An audience for effort
A marathon club page and event post gather community response around a shared goal, giving effort an audience.
Activity as a story
A club post turns a ride into a personal story with route and kudos, making a completed activity worth remembering and discussing.
Collective achievement
A club leaderboard shows collective activity and ranked members, so individual effort adds up to a shared achievement.
Why it works
A completed activity becomes something others can react to, discuss, and remember. Clubs make the network feel relevant by connecting users around place and interest, and lightweight kudos create social contact without demanding heavy conversation.
Behavioral principles
Activity As Social Object
A completed activity becomes something others can react to, discuss, and remember.
Network Effects
The product becomes more valuable as more relevant people participate.
Social Identity
Clubs help users see themselves as part of a group with shared norms.
Relatedness
Community features meet the need to feel connected while pursuing individual goals.
Design considerations
Community value should not require exposing sensitive location or routine patterns by default, and the social layer should amplify the core behavior rather than bury it.
Implementation prompt
Use the pattern above as the reference, then prototype the same behavior in your own product surface.
I want to incorporate the Community Building 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.