Good design doesn't come from inspiration.
It comes from method.
Every project I take on follows a consistent thread - not because I'm rigid, but because I've learned what actually produces results. Here's how I work.
Before I open Figma, I need to understand the domain. I read documentation, sit in on team calls, map out existing workflows, and ask uncomfortable questions. Most design problems are actually communication problems or process problems wearing a UI costume.
I bring structure to what I've learned. Problem statements. User personas grounded in real data, not assumptions. Jobs-to-be-done. This phase is where I separate what users say they want from what they actually need.
Sketches. Lots of them. I deliberately make bad ideas on paper before I make good ideas in Figma. Exploration is fast and cheap here, so I don't skip it. I typically develop 3–5 conceptual directions before converging.
Wireframes → Prototypes → High-Fidelity. I design in systems, not screens - components, tokens, and patterns that scale. Every handoff I give an engineering team is documentation, not decoration.
I test with real users wherever possible. I treat feedback as data, not criticism. The design isn't done when it's shipped - it's done when it works.
What It's Like to Work With Me
I ask a lot of questions early so I don't ask the wrong ones late.
I document my thinking so decisions aren't lost when teams change.
I work closely with engineers because a design that can't be built isn't a design - it's a sketch.
I push back when I need to - respectfully, with reasoning, and always in service of the user.
"The process is only as good as the learning behind it. Here's what I've been studying."