Expert Participation

In practice: Strava

Expert participation threads elite and creator activity into the same feed as everyday users, so aspiration feels authentic and connected to the core behavior. Users get someone to chase and a concrete reason to keep showing up.

The same kind of record

An elite athlete's profile shows follower count, weekly activity, and proof of participation, the same kind of record any user creates, which makes the expertise credible.

The work behind performance

An event participant profile with trophy case, clubs, and gear details reveals the work behind performance, making improvement feel less mythical.

Endorsement tied to use

Brand club content pairs product storytelling with community comments, so endorsement is tied to actual use rather than a staged placement.

Experts beside your progress

Feed examples show personal records, races, and peer kudos, placing expert efforts beside the user's own progress.

Aspiration in the everyday feed

Feeds mix virtual training, trail runs, and social response, so aspirational content sits naturally alongside ordinary activity.

Why it works

Expert activity appears as the same kind of record users create themselves, so influence feels less staged than conventional promotion. Seeing the work behind performance lets users borrow a future-facing identity and learn what is possible from more advanced peers.

Behavioral principles

Design considerations

Expert content should inspire without making everyday participation feel inferior, and sponsored or brand-linked activity should be clearly disclosed to preserve trust.

Implementation prompt

Use the pattern above as the reference, then prototype the same behavior in your own product surface.

I want to incorporate the Expert Participation 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.