// how I work

Problem first. Foundation second. Flows that leave no gaps.

A repeatable four-step process, refined across enterprise, healthcare, and AI products — designed so even a fully outsourced dev team can build the work without a single logical gap.

↑ hover the grid
01

Understand the problem

Problems arrive from everywhere — market data, stakeholder needs, user research. My first job is to actually understand them. I'm most comfortable when the problem is unknown or badly defined, because that's where most of my projects start.

Stakeholder sessions Market research User interviews
02

Build the foundation

Before the screens, I architect a token-based design system — light and dark, accessible, and built to scale — so every screen after it is faster to make and consistent by default. It's the structure that holds the product as it grows.

Semantic tokens Light + dark, day one WCAG-calibrated color Component libraries
03

Design the flows

End-to-end user flows with airtight logic — designed in step with the development cycle, so even fully outsourced dev teams can implement them without ambiguity. Every state is specified: error, empty, loading, and edge cases.

End-to-end flows Every state specified Dev-ready handoff
04

Lead and deliver

I research a feature, ideate fast, then either finalize it solo or hand structured tasks to designers on my team. I mentor, review, and stay accountable for the final quality all the way through launch.

Fast ideation Structured delegation Review & mentorship Accountable to launch
// the throughline
The signature move: turning complex, ambiguous systems into simple flows so logically complete that the team building them never has to guess.
// let's talk

Have a problem that isn't clear yet?

That's exactly where I like to start. Tell me what you're building.