DESIGN
PROCESS
MY
(THE) WORK
I spend my days solving problems through design. Sometimes that means sketching on paper for hours. Other times it means watching people struggle with bad software until I understand why.
(A) RESEARCH
I spend time with users in their environment. A doctor rushing between patients. A team lead managing complex workflows. An employee navigating benefits. I document their challenges, note workarounds, and spot broken patterns. No assumptions, just facts.
(B) THINK
I jump between paper sketches and digital tools throughout my process. Fast ideation on paper, refined iterations in Figma. Each medium serves its purpose until the right solution takes shape.
(C) BUILD
First as rough prototypes. Ugly but working. I put them in front of real people and watch them break. Each failure shows me what to fix next. This cycle continues until using it feels natural. Like it’s been there all along.
(D) POLISH
The final stage is all details. How the buttons respond to touch. The way information reveals itself. The subtle cues that guide without getting in the way. Small things that make the whole experience feel considered.
(E) DELIVER
Being a self-taught front-end developer gives me an edge in design. I understand what’s possible and how to build it. I write clear documentation, provide clean code specs. No gap between design and implementation.
Design isn’t about making things look good – though that matters. It’s about making things work beautifully. Every project teaches me something new about how people think, work, and live. These insights shape everything I create.
