Follow these tips and tricks to run a successful Team Leaderboard challenge.
The Team Leaderboard module runs in a leaderboard fashion scored on average total steps. Therefore, the team with the highest average of total steps, distance, or active minutes moves to the top of the leaderboard. Participants will have full visibility into team rankings as well as individual members' standing within a given team. Users can also switch the viewing metric to see standings based on totals or averages for steps, active minutes, and distance.
Team Leaderboard Module Best Practice Tips
Create a general participant team
For larger public initiatives we recommend creating a general participant team. Not all users may have a team to join, but they still want to participate and see stats. We suggest having one general participant team that users can join! Should you create a general participant team make sure to share the team name through communications so these individuals can easily join!
For example: No team? No problem. Join the general participant team called _______ to participate and see stats!
Enforce a Team minimum
It's typical for teams to be made up with an uneven amount of participants. One team may have six users while another will have fifteen. Something to be mindful of is enforcing a minimum number of users on each team. Teams with only one individual will solely reflect that users average- giving an unfair advantage. The last thing we want is a team of 1 who happens to be a high stepper.
Once you've decided this minimum (we suggest 3-4 as a minimum) make sure to include this in your initial communications, along with the detail on how you'll handle a team that does not meet the minimum requirement. It's very important to set the precedent in the initial communications.
For example: Should your team have less than the minimum of 3 users by X date we will delete your team and move all members to the general participant team.
How to handle non-syncing users
Users who aren't syncing and who subsequently have 0's will affect their team's score. This can bring team morale down. If sync reminder push notifications are on users who have not synced at 3 and then 7 total days will get a push notification reminding them to come into the app to sync.
As syncing is important to the overall success of the challenge we highly suggest using the content or chat features to also remind everyone to sync their steps to MoveSpring.
It will be beneficial to implement a rule for how you'll handle users who never sync. Include this in your initial communications and reminders to help users remember to sync.
For example: Users who have not synced after X days from the challenge beginning will be removed from the challenge.
How to handle users who have not joined a team
When users join the challenge they will see a prompt to select and join a team. This step is required for users to participate in the team challenge. While this is prominently shown in the user experience you may still encounter users who join the challenge, but do not join a team.
To monitor this you'll pull a Team Roster report from the Reporting section of the admin center. Pull this before the challenge begins and any user with a blank team field still needs to join a team. From here you have two options: to manually place them on a team or send out a targeted email to these users reminding them they must join a team.
Sample Communication Schedule
A challenge with a team leaderboard module may require increased communications than a typical challenge. This is because of the ideas outlined above. Below we've put together a suggested communication schedule based on these factors.
Before the Challenge Begins
1. Users who have joined the challenge, but not yet joined a team
How you find your recipients: Team Roster Report. Users who appear on this report, but have a blank Team Name field.
2. Users who have not connected a device
How you find your recipients: User Report. Filter by All Groups. Remove all users not in this challenge. Filter by device type: None.
First week of challenge
1. Teams who have not reached minimum number of participants
How you find your recipients: Team Rank Report. Filter by Team Member Count.
2. Users who do not have a device connected
How you find your recipients: Team Individual Member Report. Filter by device type: None.
If you have any questions around team leaderboard best practice tips, please reach out to your client success manager or contact the MoveSpring support team.