Redline IT Employee Portal

This was a redesign project for an enterprise-scale healthcare organization with a multiple-part IT platform that served over 80,000 users across several different departments and countries. The names and data have been scrambled to protect confidentiality. 

Problem Statement

Surveys, contextual research, and interviews revealed a deep user dissatisfaction with the IT support platform in its current form, most grievously in its confusing navigability, dated look and feel, and confusing information taxonomy.  

My team and I at Cognizant were enlisted to help discover the root of the issues, and to design and develop a total overhaul of the platform. 

My Role

Design Lead

Team Structure

1x Program Manager
1x Project Manager
1x IT Deparment Head
1x Design Lead
1x UX Designer
1x Developer

Project Length

6 Months

User Personas

Personas are representative archetypes of the groups of users we are designing for, which play a vital role in the design process, acting as the check-points by which all design decisions are made. "What would Sam Support think about this feature?" - for example. 

User Journeys

From Personas we build User Journeys, which attempt to map all interaction points for analysis of problem areas and opportunities to address them with design changes. 

Our client had recently acquired an Israeli company and was struggling to quickly onboard and provide IT service to these new employees. User Journeys helped us to examine the differences in experience between these and other groups within the company, especially those with unique edge cases, for example, interns, and executive assistants.

Current Design Critique

It was clear to our team, from a look at the current design (shown in the below screenshot), and corroborated by negative user reviews, that a redesign was badly needed. Opportunities ranged from "low-hanging fruit" like updating the look and feel, to a fundamental restructuring of the information taxonomy and simplifying the navigation.

Additional Microsurveys

We followed up pre-project surveys with more targeted micro-surveys of our own to learn which features might be most valuable to users in a new portal. For example, we learned that the ability to view and manage current requests was of high importance. 

Collaborative Wireframing

I led multiple remote, collaborative ideation sessions with stakeholders and users, to dive-dive into use cases, examine problem areas, and brainstorm opportunities.

Service Blueprinting

We also used Service Blueprinting which helps shed light on possible gaps between what happens on the backend, between service providers, and what users see on the front end at different times.

Image blurred for confidentiality 

Open Card Sorting

To address the issue of a difficult-to-navigate set of services and categories, we used a tool called "Open Card Sorting" to learn more about how Redline employees think about the associations between services.  

AB Testing

We tested two versions of the user flow to “report an issue”, a “short” single-page interaction vs a “long” wizard-style flow. Because the long flow cost users nearly double the amount of time as the short-flow, the decision was made to keep it short.

High-Fi Prototyping

Our team worked iteratively in review sessions with the client and users to evolve the designs.

First Click Testing

We tested new design prototypes against the original site design, to validate, and measure different UX KPI’s, and ensure users were getting to relevant information or services quickly.

Pilot Launch

The product we launched reflects directly back to user feedback we received; "Request something" is given top priority, the ability to chat is viewable from all screens, taxonomy is improved, and branding conforms to the new style guide, with a ton of new features to improve usability.