Design impact beyond UI
Design is often seen as “making things pretty”. I challenge that view by taking initiatives that shape systems, empower teams, and deliver tangible impact, ultimately influencing strategy and elevating the role of design.
I introduced a structured component deprecation process with staged reminders at 3 months, 1 month, 1 week, and 1 day before removal, giving teams time to migrate and surface issues
I presented the process to two design teams (product design and delivery design) to ensure shared understanding and alignment before rollout
Reduced risk during system changes, supported natural iteration of the design system, and prevented surprise migrations.
I defined a standard for writing component guidelines, covering how to document usage context, variant rationale, and do-and-don’t guidance
The standard is used to guide other designers in authoring component guidelines, helping them engage more deeply with design rationale
Although only one new component was created by other designers, multiple designers cleaned up existing component sets by:
reducing redundant variants
adding usage descriptions to Figma components
This behavior shift contributed to a significant drop in component detach rate, improving system consistency.
I developed a project debrief deck template to capture:
change log
assets and constraints
final solutions
rationale for decisions
I introduced a file structure standard that places the debrief deck at the top of each Figma file, making project context easy to find and reference
New designers and product teams can understand what was done, why decisions were made, and what constraints existed without digging through old files or messy sketches.
