top of page

Design systems

I've led the creation and implementation of 3 design systems in my career, building each from the ground up, pairing with developers and other designers.

Each system I've worked on has deepened my understanding of what it means to design at scale. I view design systems as more than just a set of components, but a way to communicate and consider how design and FE decisions get made and those impacts on users.

 

I'm still refining how to balance guidance and governance in a system, but I believe design systems are and will continue to remain relevant.

Sample of Pathzero's system, Terra

April 2022 -- Present

​

Key takeaways​​

  • Take the time to thoughtfully architect the visual and token system you're starting from -- it will save you time later

  • Lay down contribution processes early

  • Establish strong working groups and collaboration sessions to spur adoption and help the system grow 

Sample of OpenForm's system

July 2018 -- November 2021

​

Key takeaways​​

  • Create tokens for all atomic design units (color, spacing, text)

  • Don't build what you don't need

  • Implement quickly, refine thoughtfully

  • Don't reinvent the wheel - certain components don't need innovation

  • Continue to question the patterns you've established; they may not always remain relevant

Sample of PayIt's system

October 2016 -- June 2018

​

Key takeaways​

  • Don't over-engineer a component in its early days

  • Don't rely on a design system to implement for you

  • Lay some base rules for color usage early on

  • Document your decisions and create processes for new developers

bottom of page