Data Insights Component Library

Design system, strategy, product thinking
Tools
Figma
Duration
01.2023 - 03.2023
3 month
Company & role
Product designer @ Geotab
Project Overview
I transformed my product team into an insights-as-a-service team and built an insights component library that could be used by all teams across the organization. By doing so, we were able to accelerate the delivery of data insights to customers, while ensuring consistency and ease of use.
Team
Lead designer - me
Project manager - Sajad Shiravi
Technical project manager - Kathleen McGarrell
Development lead - Gordana Jekic Dzunic
Context
Solving for simplicity
Geotab's solutions engineering team has done a great job building customized fleet management solutions for each customer's unique needs. However, as the company grew, the product became a "feature farm". 

What does this look like? The reports in the software all served similar functionality but functioned slightly differently. I.e. no consistency in how a user interacts with tables, filters or data visualizations.

This led to a complex and borderline unusable UX, hindering competitiveness in the industry. To improve product usability, the design team embarked on a restructuring effort. Designers are identifying design patterns in MyGeotab and building a robust design system to address the problem.
Problem
Decreasing mental load, increasing speed and consistency
The integration of data insights into MyGeotab was proving to be a challenge. Multiple product teams were developing their own solutions for insights, resulting in inconsistency and confusion for users. Since data insights are a relatively complex part of the product, this approach was taking a significant mental load for each team. A more streamlined approach was needed to ensure that insights were consistent and easy to use across the product.
Users
The main users of the component library will be product managers. It will be designed to serve the needs of product managers and, by proxy, their respective end customers.
Solution
Component focused service team
We restructured my team to create a dedicated insights service team that could create insights for all product managers to use. This approach ensured consistency in the UI and saved time for PMs, allowing them to focus on their core responsibilities - being the experts of that user base.
Decision tree
Optimize for flexibility
The insights component library is documented as a decision tree for the PMs to consume. This enables PMs to start with the job to be done for the page they're building, which then guides them through the decision tree to identify the appropriate component and its placement on the page.

The decision tree approach has numerous benefits:
  1. allows the team to easily add more branches and options as we encounter new use cases, while ensuring that the library remains relevant and adaptable
  2. promotes consistency across the platform, making it easier for PM and their teams to navigate and understand the various component options and best practices