1. Agree the purpose and the period
Choose whether you want regular encouragement, a shared focus or friendly competition. Set a start and end that participants can plan around. A challenge should be understandable without a long explanation.
2. Choose a supported measure and a counting rule
Use a system metric supported by Challenges. A period total and a single-session result measure different things. For example, adding walking distance across a period is different from comparing one longest walk.
Agree the unit and aggregation rule. Personal user-defined metrics are for suitable Repeating Targets, not the curated Challenge metric list.
3. Check the example before inviting people
Planning example: a small group chooses a fixed two-week window and a supported walking or steps metric. Before starting, they agree what counts and check that their devices record the relevant information. The example does not prescribe a target amount.
Discuss differences in schedules and data recording. A missing day of data and a day with no activity should not automatically be interpreted in the same way.
4. Keep progress and the next action connected
Invite people you know using the supported sharing flow. Review progress during the period and plan the activities that contribute to it. Keep encouragement proportionate to each person’s circumstances.
At the end, review the objective and the experience. Decide whether to repeat, change the metric or return to a personal habit. Shared Challenges are not a substitute for race timing or an open public leaderboard.
Questions
Can a challenge count a total rather than the best session?
Yes. Yural supports total-of-measurements and single-measurement aggregation. Choose the rule that matches the objective.
Is this an organized race platform?
Yural Challenges support fixed-period goals and shared motivation with people you know. Yural Challenges are designed for fixed-period goals with people you know, rather than event timing or public race rankings.