Journeys explained

Using an Atomicwork journey, HR and IT teams can bring order and clarity to key employee moments and projects like onboarding, offboarding, promotions, learning, or compliance journeys.

Teams can use a journey to:

organize their work through stages and actions
define relevant tasks and assign them to owners with a due date
automatically execute actions like scheduling an email, posting a Slack message, adding a user to Okta, adding an Azure user, or ordering a Checkr background check

Journeys can be triggered by a time-based trigger like the joining date or an event like a new user is added to your HRIS. You can also manually assign a journey to an employee, like offboarding.

We’ve created a sample onboarding journey titled “New employee onboarding journey” in your account if you’d like a reference.

Create a journey

Go to Settings >** Journey templates > Create a journey**
The first stage is created for you automatically, so just go ahead and add actions to your first stage. You can organize actions by stage for clarity, even if the tasks and events are not separated by time. This will help your teammates understand what’s coming up next without making anyone feel overwhelmed.
Create a second stage by clicking on the Add stage button.Choose whether journey assignees will move to this stage automatically after all the actions in the first stage have been completed or whether they should move on a certain date field relative to a date field like “Start date”.
Add collaborators, if you have any, to the journey. Collaborators are teammates who get visibility into a journey, like a hiring manager during a new hire’s onboarding journey. They can see and add new actions to a journey. You can add multiple collaborators to a journey.

Journey status

A journey can have three statuses:

Published. This means that this journey can be assigned to employees either manually, through a time-based event, or through an action-based event. You can add collaborators to published journeys only.
Unpublished. This journey cannot be assigned to anyone until it is published.
Published with a draft. For ease of use, we preserve any changes you make to a published journey as a draft. This means that when you publish changes to a published journey, all new employees who are assigned the journey will be assigned the new updated journey.

Journeys tips and best practices:

A journey’s changes/additions will not be auto-saved. Please make sure to save your work.
Organise actions into stages for clarity, even if the events aren’t separated by time. For example, onboarding can be divided into a “Preboarding” stage, “Day 1” stage, and “Week 1” stages or a “HR actions” and “IT actions” stage. This will help your teammates understand what’s coming up for them next but will not make them feel overwhelmed.
You can rename a journey or rewrite its description at any point by clicking on the pencil icon that appears when you hover next to the journey name. We’d recommend you have a rule of thumb for journey names and use the description field to describe the use case and the actors.
We create the first stage for you automatically, which you can rename by clicking the pencil icon.
The first stage always begins when the journey is assigned to an employee.
The actions will be executed in the order they’ve been created in a stage. Currently, you cannot reorder actions in a stage.
Actions cannot be dependent actions. If you want to have two actions, A and B, but want B to be executed only when A is executed, that cannot be done in Atomicwork right now.

Create a journey

Go to Settings >** Journey templates > Create a journey**

The first stage is created for you automatically, so just go ahead and add actions to your first stage. You can organize actions by stage for clarity, even if the tasks and events are not separated by time. This will help your teammates understand what’s coming up next without making anyone feel overwhelmed.

Create a second stage by clicking on the Add stage button.Choose whether journey assignees will move to this stage automatically after all the actions in the first stage have been completed or whether they should move on a certain date field relative to a date field like “Start date”.

Add collaborators, if you have any, to the journey. Collaborators are teammates who get visibility into a journey, like a hiring manager during a new hire’s onboarding journey. They can see and add new actions to a journey. You can add multiple collaborators to a journey.

Journey status

A journey can have three statuses:

Published. This means that this journey can be assigned to employees either manually, through a time-based event, or through an action-based event. You can add collaborators to published journeys only.

Unpublished. This journey cannot be assigned to anyone until it is published.

Published with a draft. For ease of use, we preserve any changes you make to a published journey as a draft. This means that when you publish changes to a published journey, all new employees who are assigned the journey will be assigned the new updated journey.

Journeys tips and best practices:

A journey’s changes/additions will not be auto-saved. Please make sure to save your work.

Organise actions into stages for clarity, even if the events aren’t separated by time. For example, onboarding can be divided into a “Preboarding” stage, “Day 1” stage, and “Week 1” stages or a “HR actions” and “IT actions” stage. This will help your teammates understand what’s coming up for them next but will not make them feel overwhelmed.

You can rename a journey or rewrite its description at any point by clicking on the pencil icon that appears when you hover next to the journey name. We’d recommend you have a rule of thumb for journey names and use the description field to describe the use case and the actors.

We create the first stage for you automatically, which you can rename by clicking the pencil icon.

The first stage always begins when the journey is assigned to an employee.

The actions will be executed in the order they’ve been created in a stage. Currently, you cannot reorder actions in a stage.

Actions cannot be dependent actions. If you want to have two actions, A and B, but want B to be executed only when A is executed, that cannot be done in Atomicwork right now.