Product thinking · 9 min
How I turn complex data into a product people can understand
How 40 Medicare conversations became themes, decision questions, and a self-service comparison concept.
Read article →
About
Eligibility forms. Checkout steps. The third page of a catering flow.
These are the places products quietly lose people, and they're my favorite places to work. The constraints are real, the stakes are measurable, and good design shows up in the numbers.
I've worked in-house and with small teams across Medicare enrollment, financial media, home services, and hospitality. Regulated, high-consequence flows feel like home, and playful consumer products are how I stay sharp.
A few things worth knowing
The short version
- 01
I start in the support tickets
Before the brief, I read what people are already complaining about. It's the fastest research there is.
- 02
I design in English and Spanish
I write and test in both languages, which is how a lot of my localization work found me in the first place.
- 03
I build the prototype, not just the screens
Coded prototypes mean teams click through a real thing and test it on a phone instead of imagining it.
- 04
I stay for the numbers
I read the funnel after launch and I'm comfortable saying when something didn't do what we hoped.
Essays from the work
How I work, in writing
Research leadership · 10 min
How I lead research from a messy question to a clear direction
How I frame a study, choose methods, synthesize evidence, and carry findings into product decisions.
Read article →
Responsible design · 8 min
How I design to trust
What healthcare and recovery work taught me about clarity, control, dignity, and human help.
Read article →
AI & prototyping · 7 min
How I use AI in my work
How I accelerate synthesis, exploration, and coded prototypes while keeping decisions grounded in evidence.
Read article →
01 / 04
How I collaborate
- With PMsI bring the flow, the edge cases, and the trade-off list, and I like talking through scope with evidence.
- With engineersAnnotated specs, documented states, and components named to match the codebase.
- With researchIf there's a researcher, I partner. If there isn't, I run it: interviews, unmoderated tests, ticket synthesis.
- With stakeholdersI show work early and often, in the language of the metric they care about.
Toolkit
What I reach for
Design
- Figma
- Design systems
- Component libraries
- Prototyping
- Brand systems
- Illustration
Research & strategy
- User interviews
- Journey mapping
- Information architecture
- A/B test design
- Competitive audits
- Funnel analysis
AI & prototyping
- AI prototyping in Lovable
- AI research synthesis
- Coded prototypes
- React & Tailwind
- Usability testing on real builds