Services

Four ways I’m usually useful.

Most engagements are one of these, sometimes two. If what you need sits between them, say so — that’s usually the interesting version.

Product design

Products people understand the first time.

I work on the ones with real complexity underneath — payments, compliance, multi-role platforms. Most of the job is figuring out what the system is actually made of before anyone opens Figma.

Research
Information architecture
UI design
Design systems
Prototyping
Usability testing

More on this

Web development

Sites that load fast and bring in work.

I build what I design, so nothing gets lost in handoff. Next.js when it needs to be fast, WordPress when your team needs to edit it without calling me.

Marketing sites
Landing pages
Headless CMS
WordPress
SEO
Performance

More on this

Speaking

Sessions your team still uses on Monday.

I talk about how products get structured, why they break at scale, and what designers should actually do about AI. Everything comes from work that shipped, so there's always a real example.

Conference talks
Workshops
Panels
Corporate training

More on this

Mentorship

Designers who can defend their decisions.

I've trained over a thousand people through Women Techsters and Garden Academy, and I mentor one-to-one on ADPList. Most of what I teach is the part nobody covers: how to explain why you made a choice.

1:1 sessions
Portfolio reviews
Mock interviews
Career strategy

More on this

How it goes

The same five steps, whatever the work is.

Discover

Learn the business before the product. Who pays, what breaks, what's already been tried.

Define

Name the actual problem. Usually it isn't the one in the brief.

Design

Map the system, then explore several ways through it. Structure before screens.

Validate

Put it in front of the people who'll use it, early enough that changing it is still cheap.

Deliver

Ship it. I stay through build, because that's where design decisions get quietly reversed.

Not sure which one you need?

That’s normal, and it’s usually a sign the problem hasn’t been named yet. Send me what you’ve got and I’ll tell you what I think it actually is.

Describe the problem