Start with what users do, not the screen
Every decision traces back to understanding what people are trying to do, where they get stuck, and what success actually looks like for them.
Design focused on people, clarity, and real-world use
From understanding the problem to delivering usable interfaces.
I didn’t come into design through a straight-line tech path. My background is in the music business, where working with people, pressure, and real deadlines was part of the job. That experience shaped how I communicate, collaborate, and stay focused on outcomes long before I ever worked in design.
Being close to creative work in high-pressure environments taught me that good results don’t come from theory alone. They come from listening, iteration, and making clear decisions under constraints. That perspective carries directly into how I approach design — prioritizing usability, clarity, and real-world impact over surface-level polish.
Today, I bring that mindset into product and UX work by understanding the problem, asking the right questions, and delivering interfaces that are clear and usable. I’m interested in design that holds up in real conditions — not just in ideal scenarios.
Good design is the result of clear problem definition.
The interface is just the final expression of that work.
Process
Research first, then design with purpose
I start with real user needs rather than visual ideas. That means asking clear questions early, validating assumptions quickly, and making decisions based on how people actually use products — not how they look in a design file. The goal is simple: build interfaces that work in real conditions and hold up over time.
Test early, iterate often
I prefer learning through use rather than debate. Early feedback helps catch issues fast and builds confidence before things scale.
Design systems that scale
I think beyond single screens. Consistency, structure, and shared patterns help teams move faster and keep products understandable as they grow.
Work closely with others
Good products are built collaboratively. Design, product, and engineering work best when decisions are shared and communication stays honest.
Skills
Tools, methods, and process
Tools and methods that help me solve problems and communicate ideas clearly to teams and stakeholders.
Design tools and workflows
I use tools like Figma to design interfaces, explore ideas quickly, and communicate intent clearly across web and mobile products.
UI Design
User Research
Prototyping
Wireframing
Usability Testing
Design Systems
I enjoy working on problems that aren’t fully defined yet — the messy middle where priorities shift, constraints appear, and clarity has to be earned. I care about making thoughtful decisions, communicating clearly, and building work that teams can stand behind and users can rely on.