I was the only designer on the team and worked closely with the product manager to define scope and use cases, with the engineering team to ensure smooth delivery and with the end users to understand requirements and te


Background Research
This dashboard was for users within Yahoo that wanted to track video metrics across different channels (Yahoo owned and Yahoo network) to understand the KPI’s revenue numbers. The starting point was an excel sheet compiled by the project manager with a laundry list of all available video metrics and some high level categorization.

Excel sheet with requirements.

Excel sheet with requirements.

Owing to a tight turnaround time, I worked with the project manager and a couple of users to identify what metrics were key to understanding the video business health. We did not have time to consider a more formal study that would have helped us better understand the needs of our users. Another shortcoming of the research phase was the sampling of the end users. We had access to only one user role out of 3-4 that would benefit from a dashboard like this. Not having access to different users also restricted our understanding about how this dashboard may be customized for different roles. 

Keeping these shortcomings in mind, I worked on a couple of design variations that would, according to me, suit the needs of most of our end users.


Design & User Feedback

Working off of the excel sheet and a few user interviews, I recommended a dashboard structure comprised of editable cards to track and compare different video metrics. We had multiple user interviews with a bi-weekly cadence to understand what the shortcomings of the design were and if we have missed any key requirements. 

Some feedback we received after some initial testing was -

+ Users asked for more customization options , especially around the cards they wanted to view. Once created, they wanted the cards and all their other preferences (filters etc) to be sticky. We had this on the long term list of todo's, but the response indicated that we should have prioritized this sooner rather than later. 

+ Although we did have a tutorial when the dashboard was loaded for the first time, a lot of users felt that there should be more inline help on the dashboard. A key shortcoming was to not include explanations for the different metrics and how they were calculated. Even the most experienced users would often leave the dashboard and refer to a wiki page to better understand the metrics. 

+ Exporting and sharing options. Even though we managed to identify and create a dashboard that fit most users' needs, a lot of feedback was centered around the need to share this information with colleagues and in some cases with clients. They also indicated that it would be beneficial to share individual cards (like attach them in an email or a Slack message) to share a particular metric, without the need to provide access to the whole dashboard. Essentially a more functional and feature rich screenshot.