Research first
Talk to users before touching Figma.
I research the problem. Design the solution. Write the code. Most designers do one of those. I do all three.
I'm based in Vancouver. Before I open Figma I talk to users. Before I ship I read the code review. Four years of that has made me useful in rooms where most designers go quiet.
I've shipped e-commerce, SaaS dashboards, and service platforms. The brief is always wrong about something. Finding what before the build starts is the job.
I run AI agents for research synthesis, prototype generation, and production code. Not because it's faster. Because it lets me work at a scale that used to take a team.

Talk to users before touching Figma.
I know what's painful to build.
Components and tokens, not one-off screens.
I run agents. I don't just use tools.
Each one is a full story from research through to a live product.



Step 01
I feed raw interview transcripts into pipelines I've built. Themes and patterns surface in minutes. The judgment on what matters is still mine.
Step 02
I describe interaction logic and get working prototypes back. I review, redirect, and refine. The thinking layer is mine. The production layer is delegated.
Step 03
Components, copy, accessibility audits. Agent workflows handle the repeatable work. I decide what gets built. Not how many hours it takes.
Tools I direct
Listen before everything. Interviews, audits, recordings. The actual problem is rarely in the brief.
Turn raw research into a problem statement. Get alignment before opening Figma. Saves most of the revision cycles.
Lo-fi first, always. Sketch, test early, find the gaps. By the time something looks polished it has been validated multiple times.
Clean specs, real handoffs, and code when it matters. When I build it I stay close until it's live.