ServiceNow Intranet Design for Employee Experience
An intranet is opened in the middle of something else.
ServiceNow runs the workflows an organization already depends on — requests, approvals, knowledge, HR cases, the service catalog. What an employee meets is the intranet in front of them, and whether it answers in the ninety seconds they have is a research and design question before it is a platform one.
Fourteen critical intranet templates researched and designed for Southcoast Health, covering what a clinician opens an intranet to find — and forming the specification the ServiceNow replatform was built against.
ServiceNow is the system of record for enterprise service: requests and approvals, the knowledge base, HR cases and the service catalog. An intranet is never the task. Someone opens it because they need a policy, an application or a protocol, and they need it while the actual work is waiting — a shift running, a patient in a room, a queue at a counter. That makes time-to-find the measure, and time-to-find is decided by what the templates put in front of someone rather than by how much the platform holds. This is where intranet projects go wrong, and the pattern is consistent enough to name: the platform decision gets made first, the information architecture gets inherited from the org chart, and the result is a system that can answer anything and answers nothing quickly. ServiceNow is a strong place to put the work — the workflows, the catalog, the knowledge base and the HR cases belong in a system of record, and it is one. The question left over is what the employee sees, and that has to be researched against the errands people actually arrive with, then drawn as a set of templates the platform can be built to.
Our Work with ServiceNow
How the Work Splits
The system of record for enterprise service — the service catalog and request workflows, approvals, the knowledge base, HR service delivery and case management, identity and permission handling, the Employee Center and the platform’s own configuration and integration model, all of it maintained by the people who run it.
The layer an employee meets. Research into the errands people actually arrive with and how long they have to complete them, an information architecture organized by task rather than by department, a set of critical templates covering the real jobs, a design system and responsive behaviour that hold up on a phone in a corridor, and accessibility treated as a condition of the design rather than a pass at the end.
An intranet someone can use during the work rather than after it. At Southcoast Health, research established what clinicians open the intranet for — a policy, an application, a protocol — and what else it carries, including recognition for front-line staff and access to HR benefit tools. Fourteen critical templates were designed against those jobs, and they formed the specification the ServiceNow replatform was built against: a shape the platform team could implement without re-deciding what the intranet was for.
The work in practice
Everyone who opens an intranet is already doing something else. The measure that matters is not what the platform holds; it is how few steps sit between arriving and having the one thing you came for.
Where the time goes
The errand is specific and the navigation is general. People arrive looking for a named thing — this policy, that application, the protocol for this situation. A menu built from the organization chart asks them to know which department owns the answer before it will give it to them.
The second errand is nothing like the first. The same intranet carries recognition, benefits and HR tools, and those journeys have different rhythms from a mid-shift lookup. Designing for one and inheriting the other is how a system ends up serving neither well.
Search inherits whatever the content model allows. Retrieval can only be as good as the structure underneath it, so a search box added late is a search box that will disappoint. What gets found quickly is decided when the templates are drawn.
The device is whatever is in the hand. Corridors, floors, counters and vehicles are where this is opened, which puts responsive behaviour in the specification rather than in the polish.
What the layer on top has to do
Name the task, not the owner. If someone can name the thing they want, that name should be in the navigation and the platform should perform it.
Cover the real jobs, and know how many there are. A critical-template set is an argument about what an intranet is for. Getting the count right — and researching it before drawing it — is what stops the build from becoming an open-ended catalogue of pages.
Serve two audiences without either obstructing the other. The person checking a protocol and the person checking their benefits are both entitled to a short path, and the design has to keep both short.
Leave a specification, not a mood. Templates a platform team can implement without re-opening the question of what the intranet is for are the part of a design engagement that keeps paying after the designers leave.
Southcoast Health
A clinician opens the intranet during a shift, not between shifts. Research on the engagement established the three things it is opened for — a policy, an application, a protocol — and that the same platform carries recognition for front-line staff and access to HR benefit tools, so the design had to serve two quite different errands without either getting in the other’s way.
The deliverable was fourteen critical templates, researched before they were drawn, with design systems, responsive behaviour and user research as the disciplines. Those templates formed the basis of the intranet’s replatform onto ServiceNow — the design work set the shape the new platform was built to.
The engagement is written up as Reaching the Right Protocol Mid-Shift.
What this makes possible
The platform keeps the job it is good at — the request, the approval, the article, the case, the roster of who may see what — and none of that has to move for the thing in front of it to get faster.
What changes is what the organization can put in its own navigation. When the templates are drawn from the errands people actually arrive with, the intranet stops describing the organization and starts answering the question someone opened it to ask.