When consistency breaks at scale
i audited 5 products, scored 100+ components on how much they were used, and left behind docs that designers and developers could use on their own.
five products had the same problem, and it kept growing.
stackup's apps grew faster than its design decisions. button states drifted, spacing wandered, and people rebuilt components because nobody knew which version was the real one. we had flowbite, but no system holding it together.
i audited and documented while deciding what to fix first.
i pitched a modular structure before writing any docs.
every section stands on its own, so people find what they need without reading the rest.
a foundation the team could grow into.
after i left they'd need a clear structure, a reusable template, and a ranked list of where to start.
one template, so whoever came next didn't start from zero.
where i had the most opinions.
then the components, starting with the most used.
Through her meticulous approach, she uncovered a range of inconsistencies that had crept into our applications over time. Shantini's design system wasn't merely a style guide; it became a foundational tool that brought clarity and cohesiveness across a suite of apps.