UX AGENT

Selected product + website work Available for full-time roles

Here’s the work. More importantly, here’s how I think.

These case studies show how I move from an unclear problem to a working experience: research the context, make the tradeoffs visible, design the path, stay close to the code, and keep learning after launch.

Some started with one broken page. One started with 14+ years of field notes. Every project had to become clearer, more useful, and real.

See all projects View résumé
Have one critical page that is not working? Start with a free UX audit.
Portfolio index Selected work
5 case studies · 1 supporting project
01
Where the Wild Beasts Roam0→1 paid product
Live
02
Whip AroundB2B SaaS acquisition
Live
03
WilderNonprofit platform rebuild
Live
04
Know the DangersStatewide public-health UX
Live
05
Greek Mountain ManEditorial brand + storytelling
Live
06
Get Gambling HelpAccessible public-service UX
Published

All selected work

Every project. One place.

Start with the problem that looks most like yours. Each story shows what I owned, where the constraints were, which decisions mattered, and what made it into the live experience.

0→1 product B2B SaaS Nonprofit platform Public health Editorial brand

What the work proves

The deliverable changes. The responsibility does not.

I am most useful where teams lose momentum between the problem, the interface, and the live build.

01

Frame the real problem

Research, field context, analytics, stakeholder constraints, and user behavior shape the direction before the interface does.

02

Make the tradeoffs visible

Ethics, accessibility, business goals, platform limits, and user needs are named early so the team can make a real decision.

03

Carry the idea into code

Front-end depth keeps responsive behavior, accessibility, content, and design intent connected through implementation and QA.

04

Keep learning after launch

Testing, analytics, support questions, search behavior, and real use become the next release instead of a post-launch report nobody opens.

How I read the work

I do not treat the screenshot as the outcome.

The interface matters. So does the question it answers, the behavior it supports, the code it becomes, and the evidence that tells us whether the decision held up.

One connected process Research → decision → design → build → learn

That connection is what lets me enter at one page or one product problem and still see where the work reaches next.

USER

Can someone understand what this is and what to do next?

Clarity, confidence, accessibility, context, and the effort required to move forward.

BUSINESS

Does the experience support the goal without hiding the cost?

Value, conversion, trust, qualification, operational reality, and the consequences of the design.

BUILD

Can the idea survive real constraints?

Responsive behavior, content systems, accessibility, performance, CMS limits, and front-end implementation.

EVIDENCE

What changed, and what still needs proof?

Testing, analytics, search behavior, support signals, and honest separation between scale and causation.

Available for full-time roles + select projects

Need someone who can own the gap between the idea and the live experience?

I am looking for a senior product design, UX/UI, or design-engineering role where I can own meaningful work from discovery through launch. I also take select projects when one critical page, flow, or product needs focused help.

Talk about a role View résumé Need one page fixed? Start with the free audit →