Same Discipline, Three Completely Different Starting Points

A system people can reason about, not just borrow from.

My front-end background means this isn't guesswork. I understand how components need to be structured to hold up in code, and how naming, hierarchy, and relationships need to be organized so a system stays legible as it grows.

In every system I've built, I've gone past just shipping components: patterns, not just components (form patterns, button-grouping patterns, modal patterns), and usage documentation that explains not just how something works but when to use it. That's the difference between a component library and an actual system people can reason about.

Accessible from the start, not retrofitted later.

I led the design and architecture of a scalable, WCAG-compliant Figma component library, with accessibility built in from the start, contrast, focus states, responsive behavior across devices, rather than retrofitted later. My front-end background made this more effective, since I understood not just how a component should look, but how it needed to behave and hold up in code.

Prototypes fast enough to keep the conversation moving.

I brought AI tools directly into the systems workflow, using them to get prototypes functioning close to the intended flow, faster than building every state by hand. Visual variations clearly signaled fidelity level, low-fidelity versus more resolved, specifically to keep stakeholder conversations honest about what was still in flux versus what was closer to final.

No existing system to extend, so I built one.

At Temeda there was no existing system to extend. I had to get one off the ground entirely from zero, as the founding UX person on the product. That meant real build-vs-buy judgment calls: pulling reference patterns from other companies' style guides where it made sense, evaluating whether to adopt an existing system outright rather than build everything by hand, and being deliberate about which parts were worth building custom versus sourcing, so the result wouldn't become an unmaintainable one-off.