What it is and what it's for#
A journey is a path with a beginning and an end that you set out for a group of people: an induction, the rollout of a new store model, a safety campaign. It is the unit in which progress is counted.
Inside a journey, the content is organised on two levels:
- 1
Challenge groups
Thematic blocks that order the path. For example Welcome aboard, Discover the new model, Put it into practice.
- 2
Challenges
The specific tasks the person completes. They are the only thing that awards points.
The full hierarchy is: Project → Journey → Challenge group → Challenge.
An employee can be on several journeys at once. Their challenge wall is the sum of the challenges from all the journeys that apply to them.
How to set it up#
1. Create the journey#
| Field | What it does |
|---|---|
| Name | Title visible in the app. Filled in for each language active on the project. |
| Description | Explains the aim of the path. Appears in the journey header. |
| Image | Journey cover. 1200×600 px recommended. |
| Order | Position of the journey relative to the others. |
| Active | If it is switched off, the journey and all its challenges disappear from the app. |
2. Create the challenge groups#
Each group hangs off a journey and only needs a name, a description and an order. They are there to give the path a rhythm: if a journey has more than 8-10 challenges, it is worth splitting it into groups.
3. Create the challenges#
This is where all the detail is. The essential fields:
Content
Name, description (accepts formatted text), header image or video and, optionally, an external link if the challenge is completed in another tool.
Points
The points the person earns on completing the challenge. It is the only field that feeds the leaderboard and the store balance.
Completion method
Determines how the challenge is accepted as done. See the table below.
Dates
Start date and deadline, fixed or dynamic. See Fixed or dynamic dates.
Segmentation
Lets you restrict the challenge to a location, a unit of the organisational structure, a tribe or an eligibility group. If left empty, the challenge reaches everyone on the project.
Prerequisites
One or more challenges that have to be completed before this one unlocks.
Ways to complete a challenge#
The Completion method field decides how a challenge is accepted as done. There are ten options, and the form only shows you the fields you need to fill in for each case.
| Completion method | What the person has to do | When to use it |
|---|---|---|
| Mark as complete | Press a button and the challenge is approved instantly. | Low-risk, high-volume challenges: filling in the profile, downloading the app, reading something. |
| Approval | Sends it for review and it stays pending until their manager decides. | When there is evidence to assess, or the challenge is the visible part of real behaviour. |
| Admin | Nothing: they see no button. An administrator marks it from the record detail. | Recognising something that happens outside the app and is on record by other means. |
| Finish video | Watch the video to the end. | Short training and management communications. |
| Test | Pass the pass mark of the associated test. | When comprehension has to be evidenced, not just exposure. |
| Password | Type a code that you provide. | Attendance at something in person: you give the code in the room and only those who were there have it. |
| External link | Press the button that opens the link. | Driving traffic to another tool: intranet, form, training platform. |
| Shared challenge | Publish their contribution, with a comment and attachments. A moderator approves or rejects it. | When what matters is what they contribute and that the others see it. |
| Signature | Press a button labelled Sign. | Placing on record an agreement: a code of ethics, a policy that has been read. |
| Bio | Fill in their personal details in Preferences. | Completing the profile at the start of the programme. |
Three warnings about how they actually behave:
External link marks the challenge as complete on the click, not on what happens afterwards. It opens the link and awards the points: it does not check that the person reaches the destination, or that they do anything there. If you need a record that something was completed on the other side, this method does not give it to you.
Signature captures no signature. It is the same one-click button as Mark as complete, only labelled Sign: nothing is drawn on screen and no stroke is saved. It works as a gesture of agreement, not as documentary proof. If your legal team needs a signature with evidential value, this is not it.
With Approval, if nobody approves, the challenge stays pending for ever and awards no points. Before launching a journey with a lot of challenges of this type, warn the managers that they are going to get a queue. See Approvals and moderation.
Some methods add fields of their own: Password asks for the code, External link for the address, and Test for the pass mark and whether a retry is allowed after a fail.
Chosen well, the method does almost all the work. It is the decision that changes the outcome of a challenge the most, and the one most often taken by inertia. Sending something for review that could validate itself creates a queue nobody attends to; self-validating something that really matters turns the challenge into a button.
Fixed or dynamic dates#
There are two ways of deciding when a challenge goes live and when it expires:
A start day and a deadline that are the same for everyone.
This is what suits campaigns: a rollout, a safety week, a launch. Everyone moves at the same time.
The dates are calculated from a milestone specific to each person (normally their start date), with an offset in days. For example: it goes live on day 0 and expires after 7 days.
This is what suits continuous processes, above all induction: every new joiner walks the same path from their own start date.
Prerequisites#
A prerequisite keeps a challenge locked until another one is completed. It is there to force a real order, not just a visual one: watch the video before taking the quiz, sign before operating.
The order of the groups and the challenges already suggests a sequence. Use prerequisites only when skipping the order is a genuine problem; otherwise they create blocks that end up as support tickets.
What the employee sees#
- On their challenge wall, the challenges that apply to them today, grouped by journey and ordered by group.
- On each challenge: the description, the points it is worth, the deadline and what they have to do to complete it.
- Challenges locked by a prerequisite are visible, but state what is missing to unlock them.
- On completion, the points are added to their balance and the journey progress moves on.
- If the method is manager approval, the challenge goes to awaiting approval and the points are not credited until it is approved.
Frequently asked questions#
Can I add challenges to a journey that has already launched?
Yes. The new challenge appears on the wall of everyone it applies to, without affecting their previous progress. Bear in mind that the journey's completion percentage will drop, because the total number of challenges goes up.
What happens if I change the points of a challenge that has already been completed?
Points already credited are not recalculated. The change only affects whoever completes it from that moment on.
Can I delete a challenge?
It is not advisable if it already has progress: you would lose the history. Deactivate or archive it instead; it stops being shown and the history is kept.
Can a rejected challenge be attempted again?
Yes. On rejecting it, the manager states the reason and the challenge goes back to the person's wall.
Can I make a challenge reach only one store or one department?
Yes, with the segmentation fields. If you combine several (for example location and tribe), the person has to meet all of them to receive it.
Limits and warnings#
- Deactivating a journey withdraws its challenges from the app, including the ones that were half done. The progress is kept and reappears if you switch it back on.
- Dynamic dates depend on each person's start date being correct. If users are imported without that data, their challenges will not go live when they should.
- Prerequisites cannot form a cycle. If A depends on B and B on A, both are permanently locked.
- Segmentation is evaluated continuously: if a person changes store or tribe, their challenge wall changes with them.
- Each language active on the project needs its own text. An untranslated field is shown empty to anyone using that language, it does not fall back to the default language.