it's me
Starting with why, not what
Before jumping into wireframes, I want to understand what problem we're actually solving. Sometimes the thing people ask for isn't the thing they need. My favorite projects start with good questions and end with solutions that feel obvious in hindsight.
think first, draw later.
no perfect world here!
Designing for real constraints
Perfect conditions don't exist. Budgets are tight, timelines are aggressive, legacy systems are messy, and sometimes you just can't talk to users directly. I'm comfortable making smart decisions with imperfect information and finding creative solutions within real limitations.
Collaboration over hero design
The best work happens when designers, engineers, and product folks are actually talking to each other, not throwing things over the wall. I genuinely enjoy the back-and-forth of figuring out what's possible, what's practical, and what's going to create the most value.
we, not me.
details build trust.
Making the invisible visible
Some of the most impactful design work isn't flashy, it's the progress indicator that keeps people oriented, the auto-save that prevents panic, the validation message that actually helps instead of just saying 'error.' These details build trust.