Design Systems
Creating design systems that actually make sense and don't drive people crazy
You know what’s worse than having no design system? Having a design system that nobody uses because it’s too complicated. I’m here to fix that. I build systems that actually help people, not confuse them.
What I Actually Do
- Office Floor Plans - Remember that time I helped the office assistant create a whole office floor plan using FigJam? Yeah, sometimes the best design systems are the ones that help people figure out where the coffee machine is.
- Component Libraries - Reusable stuff that developers actually want to use (not just because they have to)
- Design Tokens - Colors and fonts that make sense, not just because they look pretty
- Style Guides - Guidelines that humans can actually follow without getting a headache
My Philosophy
I start by understanding what your team actually needs, not what some design theory says you should have. Every component I create is designed to make life easier, not harder. Think of it like organizing your closet - everything has its place, and you can actually find what you’re looking for.
The Tools I Use
- Figma (obviously)
- FigJam (for those collaborative moments like office planning)
- Storybook (for keeping track of all the components)
- Design Tokens (the organized way)
- Component Documentation (that people actually read)
- Version Control (because nobody likes broken stuff)