Rivian

Rivian

Rivian

Faced with an overwhelming 10,000+ disorganized dashboards on SharePoint, Rivian struggled with inconsistent data and leadership's inability to efficiently access crucial analytics. To tackle this, I led the 4-month design and development of a new BI portal. This project aimed to create a centralized platform for consistently designed dashboards, developed in partnership with a senior architect, a Rivian engineer, and Rivian stakeholders.

Oct 4, 2023

CLIENT

Rivian

CLIENT

Rivian

CLIENT

Rivian

Role

UX Designer

Role

UX Designer

Role

UX Designer

Service

Business Intelligence Portal Design

Service

Business Intelligence Portal Design

Service

Business Intelligence Portal Design

Rivian
Rivian
Rivian

Objectives

Objectives

Objectives

After learning about their existing process and gathering the requirements from stakeholders, I organized all the information into four main objectives we would need to tackle to build out our solution:

  1. To organize 10,000+ dashboards of varying file types into one portal

  2. To design for different users with varying levels of access

  3. To create a seamless, consistent experience throughout the portal

  4. To allow easier and deeper engagement with the portal

After learning about their existing process and gathering the requirements from stakeholders, I organized all the information into four main objectives we would need to tackle to build out our solution:

  1. To organize 10,000+ dashboards of varying file types into one portal

  2. To design for different users with varying levels of access

  3. To create a seamless, consistent experience throughout the portal

  4. To allow easier and deeper engagement with the portal

After learning about their existing process and gathering the requirements from stakeholders, I organized all the information into four main objectives we would need to tackle to build out our solution:

  1. To organize 10,000+ dashboards of varying file types into one portal

  2. To design for different users with varying levels of access

  3. To create a seamless, consistent experience throughout the portal

  4. To allow easier and deeper engagement with the portal

Process

Process

Process

The following is a high-level overview of my approach when designing the portal. Specific design decisions are not included in this abridged version of the case study.

The following is a high-level overview of my approach when designing the portal. Specific design decisions are not included in this abridged version of the case study.

The following is a high-level overview of my approach when designing the portal. Specific design decisions are not included in this abridged version of the case study.

Research

Information Architecture

Wireframes and Concept Testing

UI Design and Branding

Prototype and User Testing

Research

Information Architecture

Wireframes and Concept Testing

UI Design and Branding

Prototype and User Testing

Research

Information Architecture

Wireframes and Concept Testing

UI Design and Branding

Prototype and User Testing

Features

Features

Features

The following are the highlighted features in the solution, that made a significant impact to the functionality of the platform and directly targeted our high-level objectives.


Navigation

The navigation was an important feature that communicated to users the overall architecture of the portal.


Global Search

To equip users with the ability to always find what they were looking for, we implemented a global search into which users could type any prompt.


Notifications

Notifications allowed users to see recent changes made to dashboards, as well as new dashboards being added to the portal.


Comments

We employed a tool bar at the top of each dashboard to help users interact with dashboards easily and consistently, and added a commenting feature, allowing users to communicate with other viewers of the dashboard directly on the portal.


User Access Control

There was a need to consider different user journeys depending on the user type (e.g., manager vs general user), as restrictions to confidential dashboards was an important requirement.


Personalization

We incorporated a bookmarking feature that allowed users to pin their most viewed dashboards to the top of their home page.


The following are the highlighted features in the solution, that made a significant impact to the functionality of the platform and directly targeted our high-level objectives.


Navigation

The navigation was an important feature that communicated to users the overall architecture of the portal.


Global Search

To equip users with the ability to always find what they were looking for, we implemented a global search into which users could type any prompt.


Notifications

Notifications allowed users to see recent changes made to dashboards, as well as new dashboards being added to the portal.


Comments

We employed a tool bar at the top of each dashboard to help users interact with dashboards easily and consistently, and added a commenting feature, allowing users to communicate with other viewers of the dashboard directly on the portal.


User Access Control

There was a need to consider different user journeys depending on the user type (e.g., manager vs general user), as restrictions to confidential dashboards was an important requirement.


Personalization

We incorporated a bookmarking feature that allowed users to pin their most viewed dashboards to the top of their home page.


The following are the highlighted features in the solution, that made a significant impact to the functionality of the platform and directly targeted our high-level objectives.


Navigation

The navigation was an important feature that communicated to users the overall architecture of the portal.


Global Search

To equip users with the ability to always find what they were looking for, we implemented a global search into which users could type any prompt.


Notifications

Notifications allowed users to see recent changes made to dashboards, as well as new dashboards being added to the portal.


Comments

We employed a tool bar at the top of each dashboard to help users interact with dashboards easily and consistently, and added a commenting feature, allowing users to communicate with other viewers of the dashboard directly on the portal.


User Access Control

There was a need to consider different user journeys depending on the user type (e.g., manager vs general user), as restrictions to confidential dashboards was an important requirement.


Personalization

We incorporated a bookmarking feature that allowed users to pin their most viewed dashboards to the top of their home page.


Design Guide

Design Guide

Design Guide

After handing off the final design, I created a design guide for future dashboards on the portal, which would help to maintain the visual consistency of dashboards being created.

After handing off the final design, I created a design guide for future dashboards on the portal, which would help to maintain the visual consistency of dashboards being created.

After handing off the final design, I created a design guide for future dashboards on the portal, which would help to maintain the visual consistency of dashboards being created.

Final Product

Final Product

Final Product

To honour my non-disclosure agreements, the final product is not available on this site. Please contact me if you would like a walkthrough!

To honour my non-disclosure agreements, the final product is not available on this site. Please contact me if you would like a walkthrough!

To honour my non-disclosure agreements, the final product is not available on this site. Please contact me if you would like a walkthrough!