How I work
I work in four simple phases: discover, define, design, and ship — with a lot of questions asked along the way. My job isn't to make something look nice, it's to make something work, and then make it look effortless.
Five years in-house at DigiKey taught me how to move between global campaigns, web pages, brand systems, and product UI without losing the thread. I'm adaptable by default: new tool, new audience, new region — I'll learn it and ship it.
When I solve problems, I zoom out before I zoom in. Understand the context, cut the clutter, design in systems, and test with real people. Clean, breathable layouts aren't a style choice — they're the fastest path to clarity.
Good design is as much about how you think as how it looks.
I believe in:
- Start with the real problem: I don't jump to pixels. I ask questions, map the context, and make sure we're solving the right thing before deciding how it looks. A clear problem statement saves weeks of pretty guessing.
- Keep it simple, always: Clutter is a symptom of unclear thinking. I edit relentlessly so every element earns its place, the hierarchy is obvious, and the user always knows what to do next.
- Design in systems, not one-offs: I build reusable components, consistent patterns, and clear documentation so good design scales past a single screen, campaign, or region — and so the next person can pick it up without me.
- Lead by lifting others: I'm still growing as a leader, and I do it by sharing what I learn, removing blockers when I see them, and giving honest, kind feedback. The best work happens when everyone around you gets better.
My process:
- Discover: Talk to users and stakeholders, dig into the current experience, and find the friction hiding in plain sight.
- Define: Turn insight into a one-sentence problem statement and a goal the whole team can measure.
- Design & test: Clean, breathable layouts that make complex things feel easy. Test early, iterate fast, and kill what doesn't work.
- Ship & learn: Organized, documented handoff — then stay close and refine based on how it actually performs.
I'm early in my leadership journey and treating it like any other design problem: listen first, ask better questions, and iterate on how I show up for the people around me.
Tools I use
A few of the products I rely on to design, prototype, collaborate, and ship work.
