‹ Work
Design system launch
Design system launch
Design system launch
Centralizing design standards
Centralizing design standards
Centralizing design standards
I led the creation of a scalable, accessible design system that brought cohesion, speed, and clarity across teams.
I led the creation of a scalable, accessible design system that brought cohesion, speed, and clarity across teams.
I led the creation of a scalable, accessible design system that brought cohesion, speed, and clarity across teams.
Company
Company
Company
SimplePractice
SimplePractice
SimplePractice
Skills
Skills
Skills
Content Design Documentation Product Design
Content Design Documentation Product Design
Content Design Documentation Product Design
Category
Category
Category
Design Systems
Design Systems
Design Systems
Date
Date
Date
Launched Feb 2023
Launched Feb 2023
Launched Feb 2023
Challenge
Challenge
Challenge
Very little documentation existed anywhere for design, content, or engineering. This led to huge amounts of design and tech debt, and designers were unsure of what patterns to use and when. Figma components were old and copy/pasted from Sketch files, which led to them being poorly constructed. They were also spread across 5-6 library files. There was no clear "owner" of the design system work, so I decided to take action.
Very little documentation existed anywhere for design, content, or engineering. This led to huge amounts of design and tech debt, and designers were unsure of what patterns to use and when. Figma components were old and copy/pasted from Sketch files, which led to them being poorly constructed. They were also spread across 5-6 library files. There was no clear "owner" of the design system work, so I decided to take action.
Very little documentation existed anywhere for design, content, or engineering. This led to huge amounts of design and tech debt, and designers were unsure of what patterns to use and when. Figma components were old and copy/pasted from Sketch files, which led to them being poorly constructed. They were also spread across 5-6 library files. There was no clear "owner" of the design system work, so I decided to take action.
The impact I made
The impact
I made
I chose a system that matched our team’s needs and scale (Zeroheight). I wrote documentation that was just as thoughtfully designed as the components. I created a versioning system with release notes to keep track of updates. I created a slack channel for front end-engineers and designers ask questions about patterns or components and quickly get answers in a public forum to build tribal knowledge about our standards and guidelines.
I chose a system that matched our team’s needs and scale (Zeroheight). I wrote documentation that was just as thoughtfully designed as the components. I created a versioning system with release notes to keep track of updates. I created a slack channel for front end-engineers and designers ask questions about patterns or components and quickly get answers in a public forum to build tribal knowledge about our standards and guidelines.
I chose a system that matched our team’s needs and scale (Zeroheight). I wrote documentation that was just as thoughtfully designed as the components. I created a versioning system with release notes to keep track of updates. I created a slack channel for front end-engineers and designers ask questions about patterns or components and quickly get answers in a public forum to build tribal knowledge about our standards and guidelines.
Tangible results
Tangible
results
We’ve now done more than 50 releases with new updates. 94% of our teammates said the design system is "Very useful" or "Somewhat useful" in a survey. Visit the public SimplePractice design system at simplepractice.design
We’ve now done more than 50 releases with new updates. 94% of our teammates said the design system is "Very useful" or "Somewhat useful" in a survey. Visit the public SimplePractice design system at simplepractice.design
We’ve now done more than 50 releases with new updates. 94% of our teammates said the design system is "Very useful" or "Somewhat useful" in a survey. Visit the public SimplePractice design system at simplepractice.design