Indiana University Health
Style Guide
Style guide creation and implementation for internal data analytics teams. To be implemented using mostly PowerBI.
OVERVIEW
The primary goal of this guide is to ensure that dashboards and data visualizations strive for clarity and simplicity to deliver the best experience for internal customers.
The guide details a design system of elements to ensure consistency and gain efficiency. Establishing a shared vocabulary between customers, data scientists, developers and key stakeholders.
HIGH LEVEL TIMELINE
May 2024-July 2024
MAKE OF THE TEAM
Lead UI/UX- Myself
Supporting UX- Jordan Nash
KEY GOAL
Create a style guide that is an extension of the IU Health Brand Guidelines but sets it apart internally.
MY ROLE
I was the lead UI Designer on this project, working with a supporting designer and a PowerBI Architect to implement the style guide.
I started by referencing the existing IU Health brand guidelines, as we wanted this to be an extension of that, not a deviation. I pulled colors from the brand guide that worked best with data visualization (avoiding the brand's main color, red) focusing on the secondary brand colors and using them as a base to create a broader palette.
We also carried over general brand themes and fonts to keep the brand consistency throughout our data products.
Goals for the Guide
We needed a design system ,guide, and process that would be easy to implement and would improve the visual displays of data, ultimately helping to drive faster understanding and action based on the data displayed in reports and dashboards.
The primary goal of the Enterprise Analytics Guide is to ensure that dashboards and data visualizations strive for clarity and simplicity to deliver the best experience for our internal customers.
The guide details a design system of elements to ensure consistency and gain efficiency. Establishing a shared vocabulary between customers, data scientists, developers and key stakeholders.
Implementation
We needed a way to enforce the proper use of the design system and guide as well as a way to get feedback, iterate, and expand the design system as needed.
Setting up weekly office hours and checkpoints with our PowerBi architect, data analysts, and developers kept the line of communication open for constant feedback and updates on the guide as well as working out custom requests that were outside the scope of the guide.