Process
How I work
The interesting problems are rarely “make this screen prettier.” They’re usually about making complicated things easier to understand, operate and scale.
I like the difficult parts.
- Complex workflows
- Dense information
- Legacy interfaces
- Design systems
- Conversion problems
- B2B products
- Fintech
- Responsive products
- Cross-functional teams
Steps
Eight steps, every project
Understand the problem
Map the complexity
Define the experience
Design the system
Prototype the critical parts
Collaborate with engineering
QA the real product
Learn from what ships
Systems
I don’t want to design the same button twice.
Good design systems turn individual decisions into reusable product infrastructure.
- Token
- Component
- Pattern
- Flow
- Product
Implementation
The design doesn’t end in Figma.
Understanding implementation makes the design better — because decisions are made with reality in mind.
- Figma
- Tokens
- Components
- Responsive logic
- Code
- QA
- Production
Designed to be built
I don’t treat handoff as the moment the design ends. The goal is to make sure the intended experience survives contact with real code.
- Design tokens
- Responsive behaviour
- Component states
- Edge cases
- Developer specs
- Interaction details
- QA
Have a difficult product problem?
I’m most useful when the problem isn’t completely solved yet.