A Journey is a milestone-based program assigned to an employee. Journeys require the Journey capability (platform.journey), which is included on Basic/Starter and above and in Careersome Light.
The four program types Journeys are built from a fixed catalog of four program types; companies cannot invent new types:
- Onboarding
- Growth
- Retention
- Performance
Each Journey is made of milestones (checkpoints) with due dates. As checkpoints are completed, the employee's progress advances.
Templates and primitives
- Journeys are built from reusable building blocks ("primitives") and shipped templates for each program type. These primitives connect to real existing features rather than being empty checklist items, a milestone can be wired to activities tracking, a Stories pulse check, an actual probation review, or a manager checkpoint, so completing a Journey milestone can mean something is genuinely happening elsewhere in the product, not just a box being ticked.
- Admin/HR can view the primitive catalog and the standard templates
- A template can be forked to create a company-customized copy, which can then be edited for your organization. Each system template allows up to 3 company forks, so you can maintain a few variations (say, one per department) without the fork list growing unbounded.
Where you see it (role-filtered)
- Admin / HR: a company-wide snapshot of today's due items and active Journeys across the organization
- Manager: due items for their direct reports (manager-only risk flags and AI signals are shown here, not on the employee's own view)
- Employee: their own Journey progress (which checkpoint they are on, how far through the program they are). Risk/AI signals about the Journey are not shown to the employee about themselves.
Working with Journeys Admin/HR browse templates, fork and customize them, assign a Journey to an employee (which creates the dated milestones), and track or cancel assignments. Employees complete their own checkpoints as they reach them. Managers and Admin/HR can view assignment detail for people in their scope. See "Assigning and Tracking a Journey" for the step-by-step.