Design that makes itto production.
design philosophy_
My workflow has one goal: fewer steps between a problem and a decision. I sketch before I prototype, research before I wireframe, and write before I polish. Speed comes from removing the unnecessary, not from rushing the necessary.
The tools, rhythm, and principles behind how I work
Hover over any tool to see when and how it fits.
Figma · FigJam · Make
DESIGN + SYSTEMSVS Code
FRONT-END + CODEClaude + MCPs
CORE WORKFLOWMaze
RESEARCH + TESTINGNotion
DOCUMENTATIONGit / Vercel
DEPLOY + REVIEWThe rest of my stack
sprint rhythm_
A week in my workflow
Not every project looks like this but most should
Align & plan
Review sprint goals, reread research notes from the previous week, sync with the team. Write a rough brief before touching any design file. Surface risks early, before they cost a sprint.
Concept & structure
Stitch for IA sketches and early flows. Sometimes generate an HTML preview to align with engineering before I open Figma. Gets the interaction model right first.
Design & system work
Deep Figma sessions. Token audits, component states, pattern consistency. If something doesn't fit the system, I fix the system before I ship the exception.
Prototype & validate
Build interactive prototypes, test with real users or internal stakeholders. Deploy to Vercel for async review. No meeting required to get feedback.
Handoff & document
Write the dev handoff spec. Document decisions, not just outcomes. Capture what changed and why so the next sprint starts with context, not confusion.
principles_
How I think about work
Guidelines I work by and my non-negotiables
Research before pixels
Talk to users before opening Figma. A bad assumption costs a sprint. A good interview costs an hour.
Own the handoff
A design that breaks in development was never finished. I stay close to the build, write specs teams use, and treat the gap between Figma and production as my problem.
Fix the system, not the instance
When something doesn't fit the token structure, I fix the structure. Shipping exceptions compounds debt faster than shipping late.
Write before you wireframe
Words clarify thinking faster than shapes do. I draft copy, labels, and error states before I touch layout.
Defaults are commitments
Most users never change settings. Whatever ships first becomes permanent for them. Choose defaults like you mean them.
Keep AI in the loop, not in charge
Claude and MCPs accelerate exploration and documentation. Every final decision is mine. So is the responsibility for what ships.
Slow down at the start
The fastest way to design the wrong thing is to skip the listening phase. I spend more time in research than most. It narrows the space of bad decisions before any pixels move.