The Good Faith Exam
Rebuilding a one-tap approve/decline into a structured, defensible clinical review.
Read case study →I make complex, regulated software clear enough to trust and simple enough to use.
Rebuilding a one-tap approve/decline into a structured, defensible clinical review.
Read case study →An internal tool I scoped, built with Claude Code, and shipped org-wide, turning calls into signal.
Read case study →A design-led, net-new feature: plans that evolve across a client's course of care.
Read case study →Bringing each school's spreadsheet into the product as typed, governed data.
Read case study →Self-serve reporting and live visualization that ended weekly BI exports.
Read case study →Building the team is as much my craft as the product itself.
I founded Moxie's design practice as its only designer and grew it to four. I set the quality bar and the direction; my designers own their execution. The proof is in what ships under that model:
A high-quality system, built and maintained independently — the foundation the entire product draws on.
Executed almost entirely end-to-end by one designer, against the standard I hold.
Designed and shipped independently, with my feedback and bar-holding throughout.
One designer is a true purist — unwilling to compromise on the right pattern, UX, or interaction, whatever the scope. I didn't want him to lower that bar; I coached him to carry it differently: to communicate and collaborate through scope decisions, and do his best work within real constraints instead of fighting them.
A junior designer shipped beautiful screens that felt clunky in motion — one forced every user through an inventory feature most didn't need just to reach checkout. I pushed him to prototype, not just draw screens, around a principle now central to how we design: functionality should unfold for the users who want it, never block the ones who don't. Serving practices of every size, that's the heart of it.
The best operational software fits seamlessly into the user's workflow and feels invisible.
I'm the Senior Lead Product Designer at Moxie and its founding designer, leading end-to-end design across the operating system for aesthetic practices: EMR, scheduling, payments, and compliance in one place. Working with product and engineering, I find the best solution and the most logical path to build it. Alongside that, I've built out and now lead our design team.
I care about precision: the right word in an interface, the right default, the contraindication that can't be allowed to slip through. I like to start a layer beneath the screen, where clarity or chaos really comes from, so before a pixel moves I know what's actually broken.
Before design, I spent years as a teacher in under-resourced schools. That's still the through-line: meet people where they are, and make the hard thing usable.