PC Upgrade Process Portal

PC Upgrade Process Portal

Revamped the PC upgrade portal that helps employees transition to a new PC.

Reducing Email correspondances and decressing ticket numbers by 20%

My Contribution

User Research

User Flow

Iteration with stakeholders

Final Designs

Tools

Figma

Microsoft Teams

Miro

Fig Jam

Jira

Balsamiq

Timeline

11 Months

Background

Northrop grumman

Northrop Grumman Corporation is a leading American aerospace and defense technology company headquartered in Falls Church, Virginia. With approximately 97,000 employees and annual revenues exceeding $40 billion, it ranks among the world's largest defense contractors.

What is the problem?

Employees often exchange multiple emails with technical teams, resulting in prolonged PC onboarding processes that cost NG a significant amount of money over time.

What did Northrop grumman want to achieve?

Northrop Grumman experienced an increase in software usage and sought to introduce self-service portals for their employees. Thus, the initiative to enhance the PC Upgrade program began. The aim was to introduce a new method for employees to participate in the PC upgrade process and to improve communication with them regarding their participation.

How might we design a self-service portal that reduces support tickets, and improve communication with the employees on the PC Upgrade program?

Disclaimer: This is not a real email from NG; it is a prototype email designed to illustrate what the email would look like.

Image of the Old PC Upgrade Process

Final Design

MVP PC Upgrade process

A website portal onboarding experience that allows employees to decline participation, edit shipping addresses, and return old PCs.

Image of the New PC Upgrade Process

User Interview

To initiate this project, I collaborated with the project's PM to interview a small number of employees to understand their pain points when participating in the PC upgrade program.

Why do some employees talk to technical teams when transitioning to a new PC?

Interviews Key Takeaways:

PC upgrade process is tedious.

Current experience requires existing employees to go through up to 10+ corresponding emails with the technical teams to change, decline, or return their old PCs and stay up to date on the PC transition.

Time- consuming.

Employees expect the transitions to take up to 2 weeks, while in reality it takes on average 1 month to complete.

Lack of communication

Employees received an email about the PC replacement process and delivery date but did not receive details on how to change their address or cancel their participation.

What employees are feeling

"Dealing with the constant back-and-forth email ticket responses to the technical team is overwhelming."

— Employee 1

"Lack of clear communication makes the entire PC upgrade process confusing and frustrating to be a part of."

— Employee 2

— Employee 2

I expected the process to take 2 weeks, but it took so long that I almost forgot I was part of it.

— Employee 3

— Employee 3

User Flow

Finding Key Moments in the Journey

We held a collaborative workshop session with the PC refresh team to work together and figure out what we can do to solve the pain points that employees had.

We held a collaborative workshop session with the PC refresh team to work together and figure out what we can do to solve the pain points that employees had.

What I discovered:

I discovered with the PM and PC refresh team that the onboarding process does not involve employees until the pick-up and return phases. To include them at all times, I worked with the PC refresh team to create a new process involving them. 

I discovered with the PM and PC refresh team that the onboarding process does not involve employees until the pick-up and return phases. To include them at all times, I worked with the PC refresh team to create a new process involving them. 

Image of the high-level User flow

Due to NDAs, I can't show the full user flow that was made. However, I can show the high- level user flow of the main interactions.

Design Guide

Style Guide made in collaboration with the compliance team

As the sole designer of the project, I created the designs using the established NG guidelines. I developed colors and existing typography to improve the PC upgrade process experience. Following this guideline was essential, as the compliance team had to approve the final design of the new process experience.

Image of a UI Kit

Final Design

MVP PC Upgrade process

After completing the research and collaborating with the PC upgrade technical team, I worked closely with the PM and engineers to design begin impletmenting the design using Jira.

After completing the research and collaborating with the PC upgrade technical team, I worked closely with the PM and engineers to design begin impletmenting the design using Jira.

Image of the Home Dashboard

Image of the Ticket Home

Image of the 1st stage of the process

Due to NDAs, not all of the new onboarding process can be shared publicly. However, I'd be happy to discuss the project in depth—feel free to reach out.

Impact

After rolling out the first three months, we saw a positive increase in using this self-service solution.

After passing my design solution to the developer, we initiated a small-scale beta testing phase with a smaller group of employees before eventually launching it to the entire employee audience. Even after the initial launch, we concluded that we would continue to iterate on the solution, improving it over time with new interactions. When we fully rolled out the new process to 53K employees, the metrics below are what we found out in the first two months:

After passing my design solution to the developer, we initiated a small-scale beta testing phase with a smaller group of employees before eventually launching it to the entire employee audience. Even after the initial launch, we concluded that we would continue to iterate on the solution, improving it over time with new interactions. When we fully rolled out the new process to 53K employees, the metrics below are what we found out in the first two months:

20%

Ticket Numbers Decreased

25%

increase in cost saving

15%

CSAT Increased by

Reflections

Reflections

This was my inaugural project at Atos and an enjoyable experience. It provided me with insights into the dynamics of an actual company project. Initially, I was concerned about being unable to solve the problem due to limited employee access. However, it taught me the importance of overcoming obstacles and finding alternative solutions. As a result, I engaged directly with the individuals involved in the PC refresh process, which proved to be a precious asset.

Here are some of my other case studies

Premium UX Template for Framer
Premium UX Template for Framer
Premium UX Template for Framer

PC Upgrade Program Dashboard

Shipped | UX Design | Enterprise | Dashboard

Introduced a dashboard that allows executives to monitor over 53K employees' PC upgrade process.

30%

Increase in Cost Saving

90%

Visibility Increase

Swift Care

Personal Project | UX Design | Health App

Created a mobile portal to help raise awareness of priority levels within urgent care.

Let's Connect

b.a.iadegboye@gmail.com

Let's Connect

b.a.iadegboye@gmail.com

Let's Connect

b.a.iadegboye@gmail.com

Check it out on the desktop version

Hi there. If you want to view more information about this case study. Please View on a Desktop 🖥️ 🙂

Desktop Viewing

Impact

After rolling out the first three months, we saw a positive increase in using this self-service solution.

After passing my design solution to the developer, we initiated a small-scale beta testing phase with a smaller group of employees before eventually launching it to the entire employee audience. Even after the initial launch, we concluded that we would continue to iterate on the solution, improving it over time with new interactions. When we fully rolled out the new process to 53K employees, the metrics below are what we found out in the first two months:

After passing my design solution to the developer, we initiated a small-scale beta testing phase with a smaller group of employees before eventually launching it to the entire employee audience. Even after the initial launch, we concluded that we would continue to iterate on the solution, improving it over time with new interactions. When we fully rolled out the new process to 53K employees, the metrics below are what we found out in the first two months:

20%

Ticket Numbers Decreased

20%

increase in cost saving

15%

CSAT Increased by