Case 01 · Design Systems · 2025
Indee Design System
Consolidating hundreds of fragmented components into one source of truth — and cutting the team's design-to-dev handoff from days to hours.
Overview
One system to replace the many that had quietly grown.
Indee's product had grown fast, and its interface had grown with it — [hundreds of components, several near-identical button styles, the same modal rebuilt more than once]. I set out to consolidate all of it into a single, documented design system that design and engineering could both trust.
[Replace with the one-breath version: what state things were in, the system you built, and what it changed for the team.]
The Problem
Fragmentation was quietly taxing the whole team.
Duplicated components and subtle visual drift meant designers rebuilt things that already existed, engineers guessed at spacing and states, and every handoff took extra rounds. Describe the specific friction — [the four button variants, the review cycles, the bugs that slipped through] — and who felt it.
[Add the cost: time lost, inconsistency shipped, trust eroded.]
Approach
Audit, consolidate, document, adopt.
Walk through how you worked it: auditing what existed, defining tokens and foundations, collapsing the component sprawl into a canonical set, and documenting each piece so it could actually be used. Note the judgment calls and the tradeoffs behind them.
Outcome
Handoff dropped from days to hours.
Close with the impact — the faster handoff, the adoption across the team, and any metric or qualitative shift you can point to. [Add specifics: components covered, teams using it, time saved.]
[End with a short reflection on what you'd carry forward.]