I created multiple versions of the project dashboard, each with a different emphasis and categorization on key info. Through this approach, I aimed to identify the essential information and its hierarchy. Below are the 2 most valuable ones which later inform the decision-making process for my design:
1. Prioritizing Data + Project Overview
Prioritizing data insights and an overview of the project. My assumption is that this approach would be most beneficial for users who are primarily interested in data detail.
User can easily access project overview with a data explorer serves as a comprehensive landscape for data visualization.
2. Maximizing information
The design offers detailed project info. While aimed to serve various users, it could be overwhelming due to information density.
User can access all project details better than the first version. The extra Impulse section allows user to view model and algorithm details easily.
I worked closely with my product manager and engineers, we refined our approach and ultimately chose Version 2 for two main reasons:
- Key information are covered and categorized correctly.
- Design is flexible and scalable to incorporate variety of projects.
These 2 reasons address the user pain points of inefficient, Indistinguishable. We also address the third pain point by removing the inaccessible tabs.