As part of the Enterprise Visual Analytics Team, I engage in a diverse range of data visualization and information design projects. I worked on creating a reporting & dashboard design system to standardize the report development and design process. This has evolved from documenting principles and styles that have proven effective across our projects thus far. Its purpose is to ensure consistency in our work and create a better experience for our users. 
The goal of this design system is to ensure consistency in our analytics products and share best practices, offering valuable insights into data presentation and serving as a helpful reference for other teams in our organization seeking answers to their own data visualization challenges.
My Role & Process
I initiated the creation and development of this design system with our small Data Analytics Design team of 3 (me, UX Design Lead and Co-Op). I worked with my lead to prioritize different aspects of it and I provided guidance to our UX intern on the team who helped me consolidate our current reports for best practices. 
Initial Discovery & UX Research: I conducted a variety of research to establish best practices. A large part of this research was creating a comparative analysis and understanding how our design system fits into BI tools like Power BI and its specific needs. In addition, I conducted stakeholder interviews and collaborated with users who create reports to identify and define product needs.
Product Design: I led the design and socialized our initial drafts with the team and internal stakeholders. 
For phase 1, we created pdf slides that focused on defining data visualization color, typography, icons, and providing a style reference sheet for creators of reports. For phase 2, we created a website to explore the design system and added a components section that shows and explains the style and usage guidelines for different reports.
Identifying the Problem
There were two main problems with the current creation of reports:
1. The core issue we faced was the lack of standardized processes for report creation across teams. Each team was required to develop reports from the ground up, often without access to established data visualization design system references. Additionally, the diverse usage of various Business Intelligence (BI) tools among teams added complexity, leading to inconsistency in the appearance and user experience of the dashboards produced. While creating this design system we had to consider the tools used to develop the dashboard.
2. The organization's current design system, initially developed for customer-facing applications, proved unsuitable for handling the demands of data-intensive applications including reports/dashboards.
HMW unify analytics and provide clear guidelines and best practices for our teams, while delivering a thoughtful user experience?
Solution
Phase 1
For phase 1, we spent most of our time defining our standard colors and typography. 
Phase 2
For Phase 2, we worked on updating our initial design guidelines and started building out a more comprehensive design system with reusable components. One of the first components I worked on were¬†cards. ‚Äč‚Äč‚Äč‚Äč‚Äč‚Äč‚Äč
Conclusion
Our reporting guidelines serve as a valuable reference tool for report creators, streamlining their workflow while simultaneously ensuring a cohesive and polished visual identity across our suite of analytic products for end users. Phase 1 of the design guidelines were handed off to different teams in the organization for them to test on their own applications they were working on and received overall very positive feedback from them saying that it helped them drastically speed up their process for creating reports. We also received feedback from the users of the reports commenting that they've noticed a better standardization in the way the reports look which makes it easier to scan the reports and dashboards. We are continuing to iterate on the standards/guidelines as we receive more feedback and test out different components.

Back to Top