The Hidden Cost of Making Employees Navigate Multiple Internal Systems

Most organizations believe they have an information problem, but they really have a content experience fragmentation problem.

Employees struggle because finding and acting on content requires moving across multiple internal systems, each with its own logic, language, and expectations.

To illustrate this point, we’ll use benefits as an example.

A FAMILIAR (AND FRUSTRATING) EMPLOYEE JOURNEY

Here’s a common scenario:

• An employee receives an email indicating the start of benefits season, so they may start on the benefits site to understand coverage options.

• They have questions, so they’re directed to ServiceNow to read a knowledge article. They may submit a request as well.

• Tto make any changes, they’re sent to Workday to complete the transaction.

From an organizational perspective, this seems logical:

• Benefits content lives with HR

• Requests live in ServiceNow

• Transactions live in Workday

From an employee perspective, this is cognitive whiplash because every handoff introduces friction:

• New interfaces

• Different terminology

• Redundant explanations

• Increased likelihood of error or abandonment

Here’s something to think about: task completion suffers when users must traverse multiple systems to achieve a single goal.

WHY THIS EXPERIENCE BREAKS DOWN

Cognitive Load Increases with Every Platform Switch

Cognitive Load Theory explains that humans have limited working memory. When employees must re-orient to new interfaces, re-interpret instructions, or re-confirm what step they’re on, they expend mental energy on navigation instead of action.

Multiple internal sites don’t just slow people down. They increase error rates, particularly for complex tasks like benefits enrollment or life-event changes.

Employees Don’t Think in Systems. They Think in Tasks

Users form mental models based on goals, not organizational structures.

In practice, employees don’t ask where content lives or which platform owns the process, but rather what they need to do, are they doing it correctly, and what happens next.

When content is organized by platform instead of employee intent, trust erodes and confusion grows.

Knowledge Is Separated from Action

Many internal systems are good at explaining things or processing things, but not both:

• Benefits sites explain policies

• ServiceNow explains procedures

• Workday executes transactions

This separation violates a key principle of usability: users should not have to remember information from one part of a system to use another.

Every time an employee must recall instructions from one system and apply them in another, friction increases and confidence decreases.

Friction Reduces Adoption and Trust

When employees struggle to complete basic tasks:

• They lose confidence in HR systems

• They question whether information is up to date

• They bypass official channels altogether

This leads to increased HR tickets, shadow processes, inconsistent outcomes, and lower trust in internal communications - all outcomes that you’re likely familiar with.

WHAT A LOWER-FRICTION CONTENT EXPERIENCE LOOKS LIKE

Reducing friction doesn’t mean replacing every platform, but designing the experience across platforms.

Here’s what research and practice consistently support:

Design Around Employee Journeys, Not Platforms

Start by mapping end-to-end employee journeys, such as:

• “Change my benefits after a life event”

• “Understand my healthcare options”

• “Add a dependent”

Then design content flows that:

• Anticipate the next step

• Reduce unnecessary decisions

• Provide reassurance and confirmation

Employees should feel guided, not handed off.

Use One System as the Experience Anchor

While multiple systems may be required, one system should act as the primary experience layer.

Often, this happens in ServiceNow because it sits between explanation and execution.

Best-in-class organizations use ServiceNow to:

• Contextualize benefits content

• Surface relevant Workday actions

• Preserve user intent across steps

The goal isn’t to duplicate content, but connect it meaningfully.

Move From Content Pages to Task-Based Experiences

Information foraging, as identified by Pirolli & Card (1999), is when users seek:

• Clear cues

• Predictable paths

• Minimal effort

Instead of static benefits pages, design:

• “If this applies to you…” pathways

• Decision-support content

• Clear CTAs tied to actions

Employees shouldn’t wonder:

“Do I do this here, or somewhere else?”

Reduce Re-Explanation Across Systems

Content repetition across platforms often feels safer, but it creates inconsistency.

Instead:

• Centralize core explanations

• Reference them contextually

• Keep language and framing consistent

When an employee moves from a benefits explanation to a ServiceNow article to a Workday task, it should feel like one conversation, not three.

Measure Experience, Not Just Usage

Traditional metrics focus on:

• Page views

• Ticket volume

• Completion rates

But a focus on digital experience emphasizes measuring:

• Time to resolution

• Drop-off points

• Repeat visits for the same task

• Employee confidence and satisfaction

If employees repeatedly search for the same benefits information, that’s not engagement.

It’s friction.

THE STRATEGIC OPPORTUNITY

This isn’t just a UX issue, but an organizational capability issue.

Organizations that design low-friction content experiences:

• Reduce operational load on HR

• Increase employee trust

• Improve adoption of systems like ServiceNow and Workday

• Strengthen internal credibility

More importantly, they acknowledge a critical truth: employees don’t experience their organization in a silo. They experience it as a single system - or a broken one.

Is your content ecosystem healthy - or just heavy?

Reading the strategy is the first step. Measuring your impact is the next. Take the Content Experience IQ Test to benchmark your organization's maturity across behavioral science, governance, and agentic AI readiness.