Operational Dashboard Usability

Features and micro interactions to improve speed of identifying necessary information

A dashboard to monitor, measure and manage Tesla battery operations with a time scale of seconds

Original (old) Dashboard

Identifying Issues & User Studies

I began this project with little to no familiarity with the product. I partnered with the Product Manager to pinpoint subject matter experts and schedule user research sessions.

User research formats:

  • In person user interviews with various groups of users

  • Sessions with individual users

  • Sessions with subject matter experts

Themes of recurring pain points

  • Information overload (users are usually looking at one portfolio at a time)

  • Buried information (even power users were hunting for information)

  • Difficulty identifying event statuses (active vs inactive, start/end times, length)

Functional vs Visual Solutions

I approached the design improvements through 2 ways:

  1. practical, function based features to allow for better information delivery

  2. visual, micro-interaction type features to allow for information distinction

Functional Designs

Cumbersome "Filters"

Current "filters" are not only cumbersome but doesn't give the right level of information that users need.

Lack of Hourly Information

An accordion table allowed detailed information to be viewed and compared across different events all in one page.

This required building a new component in the design system and I consulted with Dev Ops. We decided this was an important asset not only for this page and product but would be very useful for the other products in the company.

Visual Designs

Lack of visual hierarchy & loud indicators

💡 Using color, shape to indicate event status

💡 Text styling to indicate priority

💡 Addition of tooltips to specify technical terms and metrics

There was a disconnect between how engineering and users defined metrics. No one party was incorrect but there was a lot of bloat around industry jargon.

Design Review

Bigger picture

Results & Next Steps

Tasks at hand

Information overload - existing "filters" were cumbersome & lacking in controls

Buried information - detailed information was hidden in several click throughs

Difficulty identifying event statuses - at a glance view provides too little/much contrast


Visual Features: implemented to provide at least some relief

Functional Features: placed in backlog due to changing resources


Partner with Platform Analytics team to analyze behaviors

Look into secondary use cases and continue user interviews

If I could change something...

There was some conflicting ideas between the different types of users during the group sessions that created tension.