Getting started with Employee Journey Management: Implementation guide
If you have an Employee Journey Management (EJM) license but haven't started implementation, this article is your starting point. It's opinionated on sequencing—because the most common reason implementations stall is starting in the wrong place—and it focuses on getting one Journey live rather than configuring everything at once.
Plan on two to four weeks to reach your first go-live if your prerequisites are in order and you have an HR admin who can dedicate focused time to configuration. That timeline assumes one Journey type, one audience segment, and minimal customization. Every additional scope item adds time.
Understand the EJM building blocks first
Before you configure anything, get clear on the three components that make up every Journey. They work together, and confusing them is the most common source of implementation confusion.
Journey designer is the top-level application. It's where administrators create Journey configurations (templates), manage Journey types, define permissions, and access dashboards. Think of it as the framework that holds everything together.
Lifecycle Events drives the automated, HR-managed side of a Journey—things like provisioning accounts, sending notifications, triggering approvals, and managing cross-departmental tasks. Lifecycle Events activities run in the background and are case-managed through HR Service Delivery.
Journey Accelerator drives the manager- and employee-facing side—stages, to-do tasks, and the interactive plan that employees and managers see in the Employee Center. This is where personalization happens at the individual journey level.
When you build a Journey, you're combining a Lifecycle Events plan (for enterprise tasks) with a Journey Accelerator plan (for team level tasks) under a single Journey configuration in Journey designer. The Journey designer admin console is where you manage all three from one place.
Step 1: Confirm your prerequisites
Do not touch Journey designer configuration until you've verified all of the following. This step is not optional—skipping it is why most teams lose one to two weeks before they've built anything.
Platform release: You must be on latest family release. Journey designer cannot be installed on Vancouver and earlier releases.
Dependent plugins and applications: Journey designer (sn_jny) has four hard dependencies that must be installed and active:
- Human Resources Scoped App: Core (com.sn_hr_core)
- Human Resources Scoped App: Lifecycle Events for Enterprise (com.sn_hr_lifecycle_ent)
- Employee Center Pro (sn_ex_sp_pro)
- Journey Accelerator (sn_ja)
Note that when you install Journey designer from the ServiceNow Store, it installs Journey Accelerator automatically. You don't need to install Journey Accelerator separately unless you're managing versions independently.
Roles: Your implementation admin needs the admin role to install and configure Journey designer. Post-installation, the sn_jny.admin role governs most ongoing configuration tasks. Managers interacting with journeys in the Employee Center need the manager role.
HR Core is live and populated: Journey designer depends on HR Core for employee data, HR profiles, and HR Service Delivery case management. If HR Core isn't configured and populated with employee records, Lifecycle Events won't trigger correctly and journeys won't have a subject to run against. A partially configured HR Core is worse than no HR Core—it produces silent failures that are hard to diagnose.
Employee Center is active: Employees and managers interact with journeys through the Employee Center. Confirm sn_ex_sp_pro is installed and your Employee Center portal is accessible.
HR catalog has content: Journeys surface catalog items to employees as tasks. If your HR service catalog is empty or unpublished, employees completing journey tasks will hit dead ends. Even five to 10 active catalog items are enough to start.
Step 2: Install Journey Designer
Once your prerequisites are confirmed, install Journey designer from the ServiceNow Store.
- Navigate to All > ServiceNow Store and search for Journey designer (sn_jny).
- Select the version appropriate for your release and select Install.
- Review the installation details dialog—it lists the dependencies that will be installed alongside the application.
- If you're installing on a development or test instance, select the Load demo data check box. Demo data provides sample onboarding journeys and cases that are useful for understanding the configuration model before you build your own. Load it on dev/test only, never on production.
- Select Install.
After installation, fix any Restricted Caller Access (RCA) approval requests before you start configuration. Navigate to All > System Application > Application Restricted Caller Access, filter for requests in the Requested state, and update each to Allowed. If you have many requests, use KB1432208 to run a bulk update script.
Journey designer guided setup
Once Journey designer is installed, use the built-in guided setup before you start manual configuration. Navigate to All > Journey designer > Administration > Journeys Guided Setup. It walks you through the initial configuration steps in sequence — creating Journey configurations, Lifecycle Events plans, and Journey Accelerator plan configurations — and surfaces the Journey designer Admin Console, which includes an introductory video explaining the relationship between Journey designer, Journey Accelerator, and Lifecycle Events. The guided setup doesn't replace the steps in this article, but running through it first gives you a working mental model of how the components connect before you start building. Role required: [sn_jny.admin].
Step 3: Choose your first Journey Type
Start with new hire onboarding. This is the right first Journey for almost every organization because it has a defined trigger (employment start date), a clear audience (new hires), measurable outcomes (task completion rate, time to productivity), and—critically—most HR teams already have some process documentation for it.
Resist the pressure to build offboarding or leave of absence as your first Journey, even if those feel like higher business priorities. Those journey types involve more complex triggering conditions, more stakeholders across legal and benefits, and more edge cases to handle. Get one Journey live and validated before expanding.
If your organization needs to engage employees before their first day—during the applicant-to-employee transition—note that the Pre-hire experience requires additional setup:
- Journey designer
- Explicit Roles plugin (com.glide.explicit_roles) installed and active
- Journey Accelerator sn_ja
- Instance on Zurich release Patch 1 or later
For a first implementation, scope the Pre-hire experience as phase two. Start with day-one onboarding to keep the initial build manageable.
If your organization plans to use agentic AI for onboarding — such as the out-of-the-box ramp-up plan generation workflow — your Journey Accelerator plan configuration needs to be structured to support it. See Agentic AI for EJM before finalizing your Journey architecture if this is on your roadmap.
Step 4: Configure your Journey in Journey Designer
The basic configuration sequence in Journey designer follows four steps. The admin console at All > Journey designer > Administration is your starting point for all of them.
4a. Create a Journey type
A Journey type is the top-level classification that groups Journey configurations. It defines header views for different user roles (manager, employee, mentor) and controls which quick links are available.
- Navigate to All > Journey designer > Manage Journey Types.
- Select New.
- Enter a meaningful title—for example, "New hire onboarding."
- Optionally configure header views for manager, employee, and mentor roles. These control what information each user sees at the top of their journey view in the Employee Center.
- Select Submit.
4b. Create and configure the Journey configuration
A Journey configuration is the template that drives individual journeys. It defines whether the Journey uses Lifecycle Events, Journey Accelerator, or both, and it controls permissions for journey owners and mentors.
- Navigate to All > Journey designer > Manage Journey Configurations.
- Select New.
- Fill in the Journey configuration fields, including the Journey type you created in step 4a.
- On the Journey owner permissions and Mentor permissions tabs, configure what actions owners and mentors can take—such as adding tasks, adding quick links, or adding recommended learning.
- Select Submit.
4c. Configure your Lifecycle Events plan
Lifecycle Events handles the automated, case-managed side of onboarding. For a new hire journey, you need at least one Lifecycle Events type (typically "Onboarding") with activity sets that represent the phases of onboarding—Pre-hire, Day 1, Week 1, and so on—each containing activities that trigger specific actions.
Navigate to All > Lifecycle Events > Administration > Manage Lifecycle Events to review the out-of-the-box Onboarding (Demo) lifecycle event and its activity sets. For most first implementations, the demo lifecycle event is a useful starting template—clone it and modify the activity sets rather than building from scratch.
One requirement to get right before you activate: any Journey configuration that includes a Lifecycle Events component needs an associated HR service with the Journey fulfilment type. Either update an existing HR service or create a new one.
4d. Create your Journey Accelerator plan configuration
The Journey Accelerator plan is what managers and employees interact with in the Employee Center—stages and tasks within each stage.
- Navigate to All > Journey designer > Administration > Manage Plan Configurations.
- Select New and fill in the form. Key fields: title, audience (the group of users who can access this plan), and the Journey Accelerator plan type.
- After creating the plan configuration, add stages by opening the record and selecting New in the Journey Accelerator Stage Configurations section.
- Set stage names—"Week 1," "Day 1," and so on—and set stage order in multiples of 100.
- Use Manage Task Templates to create the to-do tasks that appear within each stage. Tasks can be assigned to the employee, manager, or mentor, and can be catalog item submissions, approvals, or standard to-dos.
Once your plan has at least one active stage, you can set the plan configuration to Active.
Step 5: Assign owners and approvers
Journey designer supports a delegated ownership model where administrators assign plan configuration owners and approvers. This is optional but strongly recommended for long-term maintainability—it lets the HR team members who own the onboarding content update task templates without needing admin-level platform access.
Navigate to the plan configuration, open the Plan Config Owners and Approvers tab, and assign owners. Approvers are optional: if no approver is assigned, plan configuration updates publish immediately when submitted. If an approver is assigned, only one approval is needed to publish.
Step 6: Test before you go live
Before you publish any journey to real employees, run a full test against a dummy employee record:
- Trigger a test journey and walk through every task as both the manager and the employee.
- Confirm that Lifecycle Events activities fire in the correct sequence and that cases are created in HR Service Delivery as expected.
- Confirm that Journey Accelerator stages and tasks appear correctly in the Employee Center.
- Verify that catalog items referenced in tasks are active and visible to the test user.
Common issues caught at this stage: catalog items not visible due to audience restrictions, the HR service missing the Journey fulfilment type, and Lifecycle Events activities firing out of order because stage ordering wasn't set in multiples of 100.
Step 7: Plan your phase-2 enhancements
Once your first Journey is live and validated, these are the natural next additions, in order of implementation effort.
Now Assist journey generation: Enable the Journey generation skill in Now Assist for HRSD so managers can use AI to generate personalized journey plans. Navigate to All > Now Assist Admin > Skills > Employee > HRSD and activate the Journey Generation for Managers skill. Requires the sn_jny.admin and sn_nowassist_admin.nsa_admin roles.
Team tasks: Enable team tasks on your Journey configuration to allow managers—and AI agents—to add ad-hoc tasks to Lifecycle Events activity sets from within the Employee Center. Off by default. Enable it by selecting the LE activity sets can be personalized check box in the Journey configuration record.
Pre-hire experience: If you need to engage new hires before their first day, enable the Pre-hire experience as a follow-on to your standard onboarding Journey. Review the prerequisites listed in step 3.
Manager Hub integration: Integrate Manager Hub (sn_mh) to surface journey tasks and cross-functional activities in a unified manager dashboard.
Agentic workflows for EJM: Once you have your major journeys implemented and stable, EJM includes two out-of-the-box agentic workflows that extend what managers and HR teams can do without manual effort:
- Onboarding ramp-up plan generation — an AI agent that generates a personalized onboarding ramp-up plan for new hires, curated based on role and context.
- Offboarding knowledge transfer plan — an AI agent that supports structured knowledge capture and handoff when an employee exits.
To use them, you need to duplicate the agentic workflow, activate the agents within it, and activate the trigger. For full setup and configuration guidance, see Agentic AI for EJM and product docs.
What not to do on your first implementation
Don't scope multiple Journey types for your first release. Every Journey type multiplies your Lifecycle Events configuration, task templates, and testing surface. One Journey type, one audience, one release.
Don't skip demo data on your dev instance. Even if you won't use the demo content in production, loading it is the fastest way to understand how the components connect before you build your own.
Don't configure Journey Accelerator stages and Lifecycle Events activities in isolation. They need to be sequenced together. Map the full end-to-end employee experience on paper first, then configure.
Don't activate a plan configuration before it has at least one active stage. This is a platform constraint—a plan without stages can't be activated.
Don't push journeys to employees before completing a manager walkthrough in your test instance. Journey tasks that reach real employees with broken catalog items or missing approvals require administrative cleanup to recover from.
Where to go next
Once your first Journey is live, the recommended next steps are:
- Review journey completion rates and outstanding tasks from the Journey designer dashboards (All > Journey designer > Dashboards).
- Expand your task template library based on what managers are adding ad-hoc.
- Plan your second Journey type using the same configuration structure—it goes significantly faster the second time.
For detailed field references, role definitions, and advanced configuration options, see the Journey designer documentation in the ServiceNow product docs. The Journey designer admin console also links to guided setup resources and in-product video walkthroughs.
Questions about your implementation or ran into a blocker? Drop it in the comments—the community is here to help.
