Some stuff I've written

Hire me! I'm an experienced UX/Product Designer and Design System Leader with 20+ years delivering enterprise SaaS solutions, scaling design systems for complex organizations, and driving adoption across distributed teams.

Let's chat about how I can help. You can find out more about me in my CV.

A good token transformer like Style Dictionary will provide good flexibility for however you need to deliver your tokens.

Since it is so easy to create new things in Figma, I had to find a way to communicate how important it is to first use what's available.

Starting work on a new product with a new team has its challenges, for Edge Management, it was understanding the vision of the product manager as well as the capacity of the development team.

I was the first designer hired in the company and I was chosen because of my technical skill and experience in debugging web browser issues.

OMFG naming things is so hard. I've come to the conclusion that the perfect naming convention for design tokens may actually exist, but I'm not smart enough to figure it out, and certainly not with these deadlines.

Defining clear categories for each part of your design system goes along way to help adoption and maintenance. There are many ways to do this, so here is what worked for me.

While working on automating design tokens and thinking about how to scale them, I tried to address the need to keep proper documentation up to date. There was some dead code I found in a Style Dictionary version that was the seed of generating the documentation along with the production tokens with every build process.

A themable subset of white-labelled pages was the starting point, I needed to figure out how to turn it into a proper design system. The requirements were that it that should scale to accommodate other parts of the product, and also be more flexible to accommodate more and more brands.

Theme deployment and maintenance was drastically improved when I moved theme settings to an indepedent repository rather then editing manually. Further process automations provided reduced bug and feature request times.

Designing the right environment for the team to be creative, became just as important as being creative myself. I successfully introduced design sprints into the discovery process of feature development.

The transition from acquired desktop software to a feature of the [AVEVA](https://www.aveva.com/) cloud offering made branding and unified user experience a high priority.

Future Me —

– Past-You

Some stuff I've written