Redesign of “Ditt sykefravær”

Navigating through nav.no can be quite a journey. Despite a robust design system, the absence of clear guidelines has led to noticeable variations across the interface.

Summary

With no one to oversee the visual cohesiveness of NAV´s massive website, small UI variations are bound to arise. The variations have been a source of frustration for designers within the product area Health, though due to various factors it was never prioritized. Following the guidance of a senior product designer, I undertook the redesign of "Ditt sykfravær" and its sub-sites to align with the newly revamped "Min side." While the concept was well received by the other designers, uncertainty about ownership, a lack of resources and shifted focus led to that the project didn’t develop past the high fidelity sketches.

The Root cause

“Ditt sykefravær” is developed by different teams, each responsible for different aspects of the service.

As the old saying goes, “Too many cooks spoil the broth”. While “Ditt sykefravær” and it’s services are seemingly similar at first glance, upon closer inspection visual disparity starts to emerge.

We’re the same, pinky promise!🤞

LAck of cohesiveness with the rest of NAV

NAV’s “Min side” launched a new design, causing “Ditt sykefravær” to look distinctly different. At best people may think that “Ditt sykefravær” is outdated, at worst it may lead to confusion and undermind people’s trust.

Min side

Ditt sykefravær

Process

“Min side”-version

Updating the original design to match “Min side”.

Exploration #1

Explore different layouts and experiment with different information architecture.

Exploration #2

Address potential pain points via design.

Original

Using the original site as a starting site for the redesign.

Pain point #1

Click here for more information about your dialogue meeting

I found the user flow for dialogue meetings a bit redundant. A dialogue meeting can have many different statuses. Regardless of what status a dialogue meeting has, when a user first clicks into the “Dialogue meeting” page, they are greeted with the status of their dialogue meeting. In order to change, confirm or get more information regarding the status or the meeting, they are sent to another page with actions and/or information regarding said meeting. This separation of status and actions creates redundancy by unnecessarily splitting closely related information and extends the navigation process.

Old flow of when a user wants a dialogue meeting

New flow of when a user wants a dialogue meeting

In the new flow, status and action/information are combined on a single page. This integration allows users to access all relevant details in one place. As a result, the flow has been streamlined,

Wireframe of the new version of “Dialogmøter” with status and action/info combined.