_ Overview
(00)
I inherited a freelancer-created design system that functioned more like a loose style guide than a scalable product foundation.
Typography varied by team, color usage was limited, and components were still in early stages, which created inconsistency for designers and confusion for engineers during implementation.
I streamlined the typography system, expanded the core brand colors into flexible 900-scale palettes, and built out the most relevant components with clear states, styles, tokens, and usage guidance. From there, I partnered with engineers to define a path for coded components in Storybook, helping the team move away from one-off assets and toward a shared library that could support more consistent, efficient product work.
Results
+
33
%
Component Re-use
42
seconds
Less custom styles
+
11
%
Faster Design -> Launch
_ Background
(01)
Which pages act as decision hubs versus dead ends?
Are customers bouncing because of confusion or validation?
How often do people compare Moving and Storage before narrowing intent?
What information is required before a customer feels comfortable getting a quote?