NaviStone2022
Iris design system
I was hired into NaviStone's existing (legacy) platform line. The UI was a frankenstein of inherited patterns. Iris gave engineering a shared language fast enough to stop the bleeding and ship product.
Role First designer — built a complete design system in Figma, Vue, and Storybook in about four weeks
- Stack
- Figma, Vue.js, Storybook (no external CSS dependencies)
- Timeline
- Complete system stood up in ~4 weeks
- Platform
- Legacy product line — later exited; not the NXP / Zenith work
What I walked into
When I started, there was no design system—just accumulated UI. Screens drifted. Engineering had no shared components to lean on. As the first designer in the company's history, standing up a coherent system was the first job, not a nice-to-have.
Standing up Iris
I built Iris end to end: tokens and components in Figma, Vue implementations, and Storybook documentation. Roughly four weeks to a complete system—enough coverage that product work could move on shared primitives instead of one-off markup.
What it unlocked: UI bugs dropped to near-zero once teams stopped inventing controls per screen, and the shared language was enough for the team to ship a new product line in about ten weeks.
Scope and what came after
Iris belonged to the old platform I was hired into. That product line was eventually exited. Clear, not tragic—the work did its job while that line was alive.
Iris is not related to Zenith or the NXP multi-tenant platform work. Different era, different stack, different product. The NXP flagship case is here: NaviStone multi-tenant platform.