Interfaces that look excellent — and prove it.
Twenty years at the seam between design and engineering. Not just polished in Figma — built correctly in code, coherent as a system, and tuned to perform for the business.
- 20 yrs in production UI
- WCAG 2.2, keyboard & screen-reader tested
- Tokens & docs that scale
- Tuned to convert & to rank
Excellent, correct, systematic — and good for business.
Most of the work lives in the gap between an idea and a shipped interface: designs that look great in Figma but drift in code, components nobody knows how to reuse, accessibility raised late, performance and search left to chance. I close that gap on four axes at once.
It looks excellent
Type, spacing, motion, and restraint that read as deliberate — the polish you're looking at right now. The same eye goes into brand-grade UI for teams like America's Test Kitchen, NASCAR, and the NFL.
It's built correctly
Semantic HTML, WCAG 2.2 accessibility, keyboard and screen-reader testing, and a real eye on performance. Built the way it looks — production-grade, not a pretty shell over brittle markup.
It scales as a system
Tokens, components, and documentation so one decision lands on every surface at once. The backbone behind Rudiment UI and the multi-brand component library at America's Test Kitchen.
It moves the business
Interfaces tuned for conversion and retention, technical SEO that helps pages rank, and campaign and landing surfaces marketing can actually move — like the design system that unblocked campaigns at Berxi.
Receipts, not adjectives
fewer support calls
IVFCRYO — clearer, recoverable flows
fewer shipping errors
IVFCRYO — accessible forms at the source
brands, one library
America's Test Kitchen — divergence lives in tokens
-
A button label can reduce confusion.
-
A form pattern can prevent errors.
-
A focus state can make a workflow usable.
-
One system decision can save dozens of teams from re-solving the same problem.
The interface is where strategy becomes real.
A product can have a smart roadmap, strong research, and talented teams — but users only experience what makes it to the screen. The screen is where trust is won, where a flow converts or stalls, where a page earns its ranking. Small details, real consequences.
So I treat the interface as a business surface, not just a canvas — the place where craft, correctness, and system decisions show up as outcomes.
Design that has to perform, not just please.
The interface is where conversion, retention, and search visibility actually happen. I build the surfaces the business leans on — and the front-end quality that makes them fast, findable, and easy for marketing to move.
Technical SEO
Semantic HTML, clean document structure, structured data, and the Core Web Vitals performance that helps pages rank. The same correctness that serves screen readers serves search engines.
I care about the space between people, patterns, and code.
I started as a designer who learned to code. Over time, that turned into 20 years of building interfaces, component libraries, and design systems for real product teams.
That background taught me something important: experience problems are rarely just design problems or engineering problems. They usually live in the handoff, the assumptions, the missing details, the unclear patterns — the places where teams think they agree but don't.
I like working in that space.
-
Is this interaction clear to the user?
-
Does the interface behave the way people expect?
-
Can teams reuse this pattern without misusing it?
-
Are we solving the actual experience problem, or only making the screen look better?
-
Will this still make sense when another team has to build on it six months from now?
That's the work I want to keep doing.
A shift to precision work
Writing about UX engineering, accessibility, and design systems.
I write about the parts of front-end work that sit closest to the user: accessible components, design systems, interface patterns, AI-assisted development, and the changing role of front-end developers.
Practical, reflective, and grounded in real work. I'm interested in how teams make better decisions, not just which tools they choose.
Read the blogTools that show how I think.
Three interactive pieces, free to use — and a quick way to see how I approach systems work. Each one is accessible by construction and token-driven.
Want the full set? Explore all the tools .
Designer by origin. Engineer by practice. Experience-focused by choice.
I've spent my career working between design and engineering — building conversion-focused marketing sites, product interfaces, design systems, component libraries, and internal tools across a range of teams and industries.
The common thread is simple: I care about making interfaces clearer, more accessible, and easier for teams to use well. I'm not interested in complexity for its own sake — I'm interested in the kind of structure that helps people move through software with more confidence and less friction.
Teams I've worked with
Need an interface that looks right, works right, and pulls its weight?
Hiring for design systems or UX engineering, shipping a product or marketing surface that has to convert, or want a second pair of eyes on a component library — send a note. I reply within one business day.