Health at WorkProduct design · V1 delivered · 2023–2024
HAW Design System
One shared system for two products.
HAW and HAH shared many components but used different colors, spacing, and file conventions. I led the first shared design system, built foundation variables, and trained the team to use the library. We delivered V1 for new project work in three months.
Team: Design team, in collaboration with developers
- Role
- Senior Product Designer
- Company
- Health at Work
- Timeline
- Nov 2023 – Jan 2024 · 3 months
- Scope
- Two mobile products

A shared foundation for HAW and HAH.
I led the project as Senior Product Designer, built foundation variables, trained the team, and created file-organization guidelines. With limited resources and three months available, we scoped a first version that the team could maintain and extend.
The problem
Similar products, separate rules.
HAW already used an 8-point grid; HAH lacked consistent spacing rules. Similar components diverged across the two products. Designers and developers also struggled to find screens and follow flows, with much of the domain knowledge held by longer-serving teammates.
Use variables to support both products in one file.
We chose Figma variables so one design-system file could switch product-specific values. While I built the foundations, I asked the team to collect, name, and componentize existing designs. Comparing both products exposed what could be shared.

Shared foundations
Keep product identity while making spacing consistent.
I defined typography, color, spacing, shadows, and corner radius. We retained differences in primary and neutral colors while bringing HAH onto HAW’s 8-point spacing grid.



Build reusable components with understandable properties.
We built mobile components and variants, documented anatomy and properties, and checked variable bindings before using the library. I trained the team on variables and more complex components so they could work with the system.


File organization
Make the flow visible alongside the screens.
I created and presented guidelines for main and smaller flows, use cases, component variations, cross-flow links, and design states. Design and development teammates felt the structure would help them find screens and understand the cases to cover.

Outcome & reflection
What we delivered
A first version ready for new project work.
We delivered V1 and adopted it in a new work file, keeping the old file as a legacy reference. Product-specific variables supported both products within the shared library.
V1 delivery and new-file adoption are the recorded outcomes; no efficiency or time-saving metrics were established.
Reflection
The system needed shared understanding as well as components.
Training and documentation were part of delivery, not follow-up tasks. A shared library only helped if teammates understood its properties and could find the right flows.
Future direction
Connect the token workflow more closely to development.
I considered exporting Figma variables and maintaining tokens with Tokens Studio to connect design and development more closely. This remained a future direction, outside V1.
