FAQ About meA few things people usually ask
The honest answers, straight from me.
-
I'm a product designer with 10+ years in SaaS, growth, and enterprise UX. Most of my work lives in the messy middle: complex dashboards, ops tools, e-commerce flows, and the design systems that hold it all together. I also take on visual and brand work when the project is the right fit. The throughline in everything I do is making sure design actually moves a number, whether that's conversion, retention, or time on task.
-
Figma is home base for everything from early wireframes to full prototypes and component libraries. I get my hands into HTML and CSS when I need to prototype something Figma can't quite capture. On the CMS side I'm familiar with Prismic, Storyblok, Squarespace, and headless website builders, so I design with content structure in mind rather than handing off something that breaks the moment it hits a real CMS. I also use AI tools, primarily Claude, woven into my daily workflow for copy iteration, design critique, and moving faster on research.
-
I try to understand the business goal before I touch a single frame. That means mapping flows, digging into any analytics that exist, and asking the questions nobody wants to ask early. Then I move fast: rough concepts out the door, real feedback, iterate. I'd rather show something imperfect on day three than disappear and resurface with a polished surprise two weeks later. That approach has consistently helped teams ship faster and reduce expensive late-stage rework.
-
Yes, and I genuinely enjoy it. I've built systems from scratch across multiple products, including component libraries, typography tokens, and Figma Variables. What I care about most is that the system actually gets used, which means it has to make sense to developers too, not just look good in a Figma file nobody opens. A well-adopted system tends to cut design QA time significantly and gives the whole team more confidence shipping quickly.
-
Selectively, yes. I work best with remote teams who need someone senior enough to own a problem end to end without a lot of hand-holding. If you have a real design challenge and want a collaborator who actually gives a damn about the outcome, let's talk.
-
Yes. I've worked on checkout and purchase flows that lifted conversion, redesigned internal ops tools that meaningfully reduced support team workload, and built CRO-focused landing pages that improved lead quality. I approach every project thinking about what success looks like in a metric, not just how the design looks. The case studies on this site go into the specifics.
-
The contact form on this site is the most reliable. I check it regularly and try to respond within a day or two. If you found me through Upwork, you can reach out there too.
How I workWhat you can count on from me
Not a list of buzzwords. Just how I actually show up.
I have a strong bias toward getting things done. I don't wait for perfect conditions or a fully defined brief. I move, make something real, and refine from there. Teams I've worked with know they can hand me something half-formed and it'll come back finished.
I own my work completely. If something I designed isn't landing, I want to know and I'll fix it. I don't deflect, I don't disappear, and I don't blame the brief. The outcome is my responsibility as much as anyone's.
Good design doesn't happen in isolation. I bring people in early, share work before it's ready, and actively want pushback from engineers, PMs, and anyone close to the problem. The best ideas in the room rarely start with me.
I'm not here to make things pretty. I'm here to figure out what's actually broken and design the clearest path through it. I ask uncomfortable questions early so we're not discovering the real problem in the last week of the project.
I've been a Design Director and I've been a solo IC. I'm equally comfortable in both and I don't need credit to stay motivated. What matters is that the product ships and the team feels good about it.
Most of my best work has been in industries I knew nothing about walking in. I get up to speed fast, ask the right questions, and bring a perspective the team can't give itself because they've been too close to the problem for too long.
Still have a question? Just send me a message and I'll get back to you.