Good design and good pasta have the same enemy: being technically correct and still not quite right.
Italian chefs know pasta is al dente by feel, not by the clock. That's how I design: the rules are the foundation, instinct is what makes them work.
About me
↴
In my 6 years of design, one lesson stuck above all: users rarely say what they need, and businesses rarely say what they actually want. My job is translating both.
My design process
↴
Asking "why"
- understand the real problem before touching Figma
- what does the user actually need?
- what does the business actually need?
- what problem are we solving?
Research & discovery
- user interviews and surveys
- competitive analysis
- identify patterns and pain points
Define the problem
- synthesize research into insights
- write clear problem statements
- prioritize what actually matters
Ideate & wireframe
- sketch multiple directions fast
- structure navigation and flows
- validate logic before visual design
UI design
- build on top of a design system
- consistent components and tokens
- design for edge cases, not just happy flow
- (maybe) skip wireframes when the design system is mature enough
Test & iterate
- prototype key interactions
- test with real users
- refine until it feels obvious
This is how I think about design. In practice, steps overlap, loop back, and sometimes happen all at once (and that's fine).