Recurring Challenges

Recurring Challenges happen again and again on a predictable schedule. They are ideal for weekly, monthly, or daily competitions.

 

We recommend walking through the entire article if this is the first Recurring Challenge you've created. If you need to navigate to a specific step of Recurring Challenge creation, select the appropriate step:

How do I access the Create Challenge form?

Step 1. Name and Time Frame

Step 2. Competitors

Step 3. Scoring

Step 4. Prizes

Step 5. Add to TV

Why do I see "Preview" next to the Challenge's name?

 

Create a Recurring Challenge

1. Create a recurring challenge through the Quick Actions button, Motivate and Recognize > Competition, or through the left navigation, Competitions > Create.

 

2. Click the Create button on the Challenge tile.

 

3. Complete the Create Challenge Form.

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 to Ambition once a day, every night at midnight, etc. Only data that Ambition receives during the competition's time frame will contribute toward's the competition's score.

Competition 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

 

 

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.

 

2. Competitors

Hierarchy Level:

What style of competition do you want to create?

• User vs User? --> Select User as the Hierarchy Level
• Team vs Team? --> Select Team or corresponding Group Type within your instance (Manager Team, Pods, etc)

Learn more about Ambition's Hierarchy Levels and see Challenge Hierarchy examples here.

 

Competitor Selection:

Select whether all of the chosen hierarchy or just specific members of User / Groups will compete in the Challenge.

If a Custom or Within grouping is selected, pick specific Users / Groups to compete in the Challenge.

In the example below, the Atlanta office will be competing against the Chicago office. No User vs User competition, but rather the Atalanta Location as a whole vs the Chicago Location as a whole.

 

3. Scoring 

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.

Be mindful that a single-day or power hour Challenge won't be very impactful if your Metric data is pushed to Ambition once a day, every night at midnight, etc. Only data that Ambition receives during the competition's time frame will contribute toward's the competition's score.

For summed metrics (calls for example) only data that Ambition receives during the competition's time frame will contribute toward's the competition's score. This supports an hour-long competition for individual users or teams.

If the scoring configuration is set to use a daily average, the competition may contribute data received outside of the competition's time frame. For example, if the competition begins mid day, but it is built off of an averaged metric like Activity Score, the competition score will include the entire day's data for the daily average calculation.

 

Competitions can be both multi-metric and points-based.

Note:

Multi-Metric Competitions cannot exceed combining 5 metrics.

The same Metric cannot be used more than once in a single Challenge. ie. Cannot use 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 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.

Option	Recommended Use	Behavior
Use Per-User Average (Value Method)	Recommended for when competing groups are not the same size, and the challenge time frame is at least 1 day. If an hour long or half-day challenge is using averages, the full day's average will be used in the score calculation.   Since Activity and Objective Scores are inherently averaged, they will already be calculated based on 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 (Aggregation Method)	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
Exclude Weekends	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. If you are using a Monthly Objective Score scoring parameter and desire the competition score to match the Groups's Dashboard, ensure this is toggled Off.
Bench Out-of-Office Players	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 marked Out of Office will be ignored.
Min Value*	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.
Max Value*	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.   Value Scoring Ex. If value scoring (1:1) is being used and a max value of 20 is set for Calls, the max points you could receive in the competition for Calls is 20. Points Scoring Ex. If Calls are worth 2 points a piece and a max value of 20 is set, the max points you could receive in the competition for Calls is 40.

*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 + 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 using 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 + Add button.

Learn more about Prize thresholds here.

 

 

5. Add to TV (optional)

Optionally display your Challenge on an Ambition TV.

A countdown timer will be displayed on the slide if the competition has not yet started.

For Recurring Challenges, a countdown timer will displayed only before the first occurrence. For subsequent occurrences, the results of the previous competition will be displayed on the slide until the next competition begins.

 

To Add Recurring Challenge to TV:

1. Select the respective TV(s) you'd like your Recurring Challenge to appear on from the Available list.

2. 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.

 

 

Finishing up

4. Once you've completed the Challenge Form, click the Create Challenge button.

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.

 

 

Preview Badge

If at any time you notice a 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 by users with Admin permissions 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 gethelp@ambition.com.