Recurring Challenges happen again and again on a predictable schedule. They are ideal for weekly, monthly, or daily competitions.
By default, Managers cannot create Competitions.
If you desire for all Managers, specific Managers, or even end Users to Create, Edit, and Delete Competitions, ensure the Permission
Competitions: All Access has been assigned!
Have questions about updating Permissions? Learn more here.
Create a Recurring Challenge
1. Create a recurring challenge through the quick actions button, Motivate and Recognize > Competition, or through the left-hand navigation, Competitions > Create.
2. Click the green Create button on the Challenge tile.
3. Complete the Create Challenge Form. Fill out the following fields:
1. Name & Time Frame
Note: If you wish to compete on Objective Score you can only do so if the Challenge time frame matches the time frame of your Objective Score (weekly, monthly, quarterly).
Be mindful that a single-day or power hour Challenge won't be very impactful if your Metric data is pushed over every night at midnight.
Name: We recommend a name which explicitly includes Metric and time frame.
Challenges can either take place once, or on a recurring basis. In this article, we'll discuss Recurring Challenges.
For one-off Challenges, check out How do I create a Challenge?
For Recurring Challenges, move the selector to Recurring
Like to see some examples of Recurring Challenges?
Establish the Initial Event
Start Date, Start Time and Time Zone
While one-off Challenges can start and end in 30 minute intervals, at the current time Recurring Challenges must begin and end on the hour.
Set the Start Date, Start Time and Time Zone, establishing the start of the Initial Challenge
Note: Retroactive, or Challenges with a Start Date in the past, will default to have a Start Time of 12:00AM
End Date and End Time
Set the End Date and End Time of the first Challenge, establishing the Challenge duration. The same Time Zone will be used.
The duration, or period between Start Date/Time and End Date/Time of this competition will be used for all future recurrences of this Challenge
Things to Note when Creating a Recurring Challenge that Starts in the Past
When creating a Recurring Challenge that features a “Start Date and Time” that occurred in the past, the scoring will begin at the Challenge's creation time and not the actual start date for the first occurrence.
You created a Recurring Challenge on Wednesday at 11:00 AM with a start time of Monday at 8:00 AM.
- For the first occurrence, the Challenge's scoring will begin at the time you created the Challenge (Wednesday at 11:00 AM).
- For the second occurrence and all additional occurrences, the Challenge's scoring will begin at the specified start time (Monday at 8:00 AM).
This behavior occurs because Ambition does not track hourly deltas.
If it is necessary to create a Recurring Challenge in the middle of the week that starts on a previous day of the same week, we suggest following these steps:
- Create a one-off Challenge to account for the first occurrence of the Challenge.
- Create a Recurring Challenge that has a start time of the second occurrence. (i.e. Your weekly Challenge starts on Monday and ends on Friday. Set the start time to the following Monday).
Performing this configuration will provide accurate data for the first occurrence and all additional occurrences of your competition.
Establish Frequency of Each Recurring Event
The frequency of recurrence determines how often this Challenge will repeat. In the example above, we've configured the challenge to repeat once a month, starting on the 1st day of the month and ending on the last day of the month.
The flexibility of this interface enables recurring schedules such as:
- Every Day or Week
- Once per Month
- 2nd Monday of Every Quarter
- First Day of the Month to the Last Day of the Month (Note: this selection picks the first and final day of the month, not the first and final business day.)
Establish When The Recurrence Ends
Recurring events will continue on forever, unless an end is defined. Recurring Challenges can end after a certain # of occurrences or on a specific date.
Select which Hierarchy Level to compete at. Read more about Ambition Hierarchy Levels here.
If a Custom or Within grouping is selected, pick specific Users / Groups to compete in the Challenge.
This is the KPI or Metrics that will be used to calculate "points" for this Challenge. It's important to keep in mind the frequency with which your data is pushed to Ambition (hopefully real-time), in relation to the competition. Competitions can be both multi-metric and points-based.
Multi-Metric Competitions cannot exceed combining 5 metrics.
The same Metric cannot be utilized more than once in a single Challenge. ie. Cannot utilize both points and value scoring for the same metric.
If you wish to compete over Objective Score, ensure the Challenge's time frame matches your Objective Score time frame.
Ex. Weekly Objective Score = Challenge starts on Monday @12am. Monthly Objective Score = Challenge starts on the 1st of the month @12am.
Click the purple Add Score Parameter button to begin compiling your competition Metrics.
Select a Metric from the Metric drop down.
Select the Scoring Type
If Points is selected as the Scoring Type, complete adjust the Points Per Value selections to fit your needs.
At this time, points are required to be whole numbers.
Example above showcases where 5 points will be given per 1 Appointment Set
Determine and set options for the Scoring Parameter.
|Use Per-User Average||
Recommended for when competing groups are not the same size.
Since Activity and Objective Scores are inherently averaged, they will already utilize a Per-User Average. This toggle will have no additional impact towards either Activity or Objective Score.
If toggled off, the metric Value will be used:
This setting will use the value of the metric associated with an entity to generate the score.
Example: If a user/team creates 10 new leads every day for 1 work week, their value is 50.
If toggled on, the Average value will be used:
If the entity being scored is a super entity (or team) use the average metric value of each sub entity (users) to generate the score.
Example: Team A has two team members. Respectively, they each have activity scores of 80 and 100 for the week, so their average score is 90 [(80+100)/2].
|Sum Daily Averages||Recommended for long durations where affecting the average becomes increasingly difficult.||
For competitions that last longer than a day and contain more than one metric value (Monday's value, Tuesday's values, etc) we must determine how to aggregate these values together, for example, summing or averaging:
If toggled off, Default scoring applies = This will depend on the metric being scored. If the metric is an average metric, the value will be averaged across the time span of the competition. If the value is summed, the value will be summed.
Note: Activity Score and Objective Score are Average metrics
If toggled on, Sum scoring applies = Ignore the metric type and always sum the daily values together
Do not include weekends in the scoring calculation.
Only applicable for Competitions spanning over the weekend days, Saturday or Sunday
If toggled on = all weekend values will be ignored. If the user generates metrics over the weekend, they will not be counted towards the competition’s score.
Do not include users who are out for sick days, PTO, etc from bringing down a team's score.
If toggled on = metric values generated on days where the user is "benched" will be ignored.
A "pay to play" setup. One must cross a threshold before generating a score.
The floor that must be reached before score contribution is made.
Note: After the threshold is crossed, a user's score will be representative of the threshold's value and not starting from 0.
Ex. A User crosses a min value of $10,000 Revenue, and their score will reflect their $10,500 metric value. NOT from starting $0 once the threshold is crossed.
A "cap" on the amount of contribution a user can receive from a single metric.
Prevent inflation of score from a single metric.
The ceiling at which no additional score contribution is made.
*Note about Thresholds and Multi-day Challenges
A minimum or maximum threshold will be applicable to the Challenge's duration as a whole.
Repeat the above steps for each desired Score Parameter.
Multi-Metric Competitions can combine up to 5 different metrics.
4. Prizes (optional)
Prizes are not required, but if appropriate can be granted based on Rank (1st, 2nd, 3rd...up to 10th) And/Or based on Threshold (everyone at or above x Score gets y prize)
Note: Threshold applies to the overall score. If multiple metrics or average scoring is being used, we would advise careful projections before stating the thresholds.
A combination of Rank and Threshold prizes can be used!
To include a Rank based Prize:
1. Select Rank from the Type dropdown.
2. Select which Rank (options for 1st-10th) you'd like to input a prize for in the Place dropdown.
3. Fill in the Prize that will be awarded in the Description field.
4. Click the blue + Add button.
To include a Threshold based Prize:
1. Select Threshold from the Type dropdown.
2. Input the respective threshold value to be reached
Again note that thresholds are for the overall score. If utilizing a multi-metric Challenge or averages, we would advise careful projections before stating the thresholds.
3. Fill in the Prize that will be awarded in the Description field.
4. Click the blue + Add button.
Learn more about Prize thresholds here.
5. Add to TV (optional)
Optionally display your Challenge on an Ambition TV.
Select the respective TV(s) you'd like your Challenge to appear on from the Available list.
Optionally select a Start and End Date from the respective dropdown if you'd like the slide to being being displayed and/or stop being displayed at a specific point in time.
4. Once you've completed the Challenge Form, click the green Create Challenge button in the bottom right.
Participants will be notified via email before the Challenge begins, and track progress via Dashboards. Don't forget to include this Challenge on a TV slide for added visibility and competition.
If at any time you notice a black Preview badge listed alongside a Challenge's name in the Manage Competitions interface, that Challenge was created by a member of the Ambition team.
If you've been working with Ambition Support or your CSM regarding a Challenge's setup or scoring, a member of the Ambition team can create a challenge in Preview mode that allows you to "test drive" the Challenge's setup and scoring configurations without directly notifying your users.
The Challenge can be viewed, edited, and deleted like a normal Ambition Challenge but is hidden from any user without Admin Permissions in Ambition.
Preview Challenges cannot be created in Ambition by end-users, no matter the permission set. If you have any questions about a Preview Challenge in your instance, reach out to firstname.lastname@example.org.