So what was the approach?
When determining how to build Raven’s design system, it was important to consider what their business is and what environments their products would live in. As a company focused on contextualized time, Raven's products are used primarily in 2 distinct types of environments.
The corporate environment (Tier 1)
Raven Flight™️ handles data visualizations and communicates contextualized time. This will be used primarily by plant managers and executives in office environments.
The warehouse environment (Tier 2)
Raven Sense™️ collects data and assist manufacturing/shipping operators. This will be use primarily in warehouses that could be grimey, poorly lit, and where users may be wearing equipment when interactive with screens.
Understanding this, a 2 tiered design system structure felt appropriate. Tier 1 would host components and guidelines designed for the office environment, and this would be the “standard” collection of assets. Tier 2 would contain modified components and guidelines from tier 1. Modifications would aim to optimize product usability in the warehouse environment. This meant UIs with bigger interactive elements, higher contrast, and simplified interactions.