I work at the intersection of complex systems and real human behavior — turning dense workflows into something people don't need a manual for. Currently at Deloitte. Previously built from 0→1 at Buzo.
The tool had the right framework but the wrong experience. Redesigned the end-to-end review flow to reduce cognitive load, support novice and expert users simultaneously, and make decisions feel guided — not grueling.
Sales reps don't live in dashboards. Designed a mobile-first CRM that fits into field workflows, not against them.
Accountants were drowning in manual reconciliation. Redesigned the core data entry and review flow to cut errors and time per session.
First-time parents are overwhelmed. Designed a calm, trustworthy tracking experience that reduces noise and surfaces what actually matters.
How Marvel built MVPs, validated retention loops, and scaled a franchise like a product manager's dream over 15 years. A thinking piece — not a design case.
View Case Study
I feed AI everything — research docs, interview notes, brand assets, product briefs — before writing a single prompt. Context is what separates useful output from generic output. What I do with that output is where the design happens.
Pattern-finding across qualitative data. Problem framing drafts.
Competitor mapping, feature matrices, idea stress-testing.
Colour, type, wireframe starts, screen variations, component scaffolding.
Specs, annotations, interaction docs. Wrong AI output here creates production debt.
Accessibility checks, usability simulation, friction flagging before dev.
The output is always mine to accept, modify, or reject.
I’ve worked across teams, timelines, and expectations
