Future Beyond and Neplar Corei — WordPress builds, then front-end development and senior UI design. I learned design and code as one job before the industry decided they were two.
Three years at Protopillar: end-to-end interfaces, journey maps, personas built from primary research, and analytics-driven iteration. The unglamorous reps that make judgment fast later.
A rapid sequence — Vivoiz Healthtech, a design system from scratch on contract at AI Enterprise, a UX audit of a major property platform at CX100 that surfaced 30+ critical gaps, then independent consulting. Different domains, same brief: something is too complex, and people have to use it anyway.
Principal Product Designer at Seanergy Digital. A research-led redesign of core product interfaces — moderated and unmoderated testing cycles, synthesized into changes the engineering team actually shipped.
Staff Product Designer & Design Lead at Alshaya Group. I own design strategy for a multi-brand retail platform ecosystem — and architected the design system that holds it together: 200+ standardized components across 6+ product surfaces. First product shipped within 3 months of joining; adoption rose 35%.
An AI design audit tool built on an agentic architecture in 2025 — before agents were a recognized category. Point it at a screen and an agent walks it the way a reviewer would: a structured critique of hierarchy, consistency, and accessibility. Launched on Product Hunt in August 2025.
prismkit.app ↗A predictive product intelligence platform: real user behavior turned into conversion improvements, smarter experiments, and forecasted outcomes. The most advanced thing I've built — aimed at a niche the big analytics suites fly over, and in active refinement toward it.
signalhq.app ↗Walk into critique armored. Crit prepares product designers for critique sessions: upload your work, get a structured four-section report before anyone else sees it. Auth, schema, and workspace architecture are live; the critique engine is in active build.
thecrit.tools ↗An AI model generator for 3D-printer owners. Sprint 2 validation showed the generation API produced geometry that was shape-wrong, not scale-wrong — a flaw no amount of downstream normalization could fix. I killed it in a week instead of polishing it for a year. Knowing when to stop is a design skill too.
A multi-brand system lives or dies at the token layer. We built a core token set — color, type, spacing, elevation — that brand themes consume and override, so six product surfaces stay coherent without becoming identical. Components reference tokens, never raw values. Change once, propagate everywhere.
Components don't ship themselves. I rebuilt the design-to-development pipeline around explicit handover protocols and design QA checkpoints — the recurring rework loops between design and engineering didn't survive it. The first product shipped through this pipeline went live within three months of my joining; adoption rose 35%.
The system now spans 200+ standardized components across 6+ surfaces — allocation dashboards, replenishment workflows, admin tooling, and the surfaces in between. Duplication went down because the path of least resistance finally pointed at the system instead of away from it.
Every build starts as a written specification: design tokens, motion principles, copy, component structure, definition of done. The spec is the design artifact now — precise enough that an agent can execute it, readable enough that a human can review it. Ambiguity in, garbage out; clarity in, shipped product out.
Agents are fast, tireless, and confidently wrong in ways no junior designer ever was. The craft has moved: from making every artifact by hand to knowing which output is right, which is subtly broken, and which spec needs correcting. You fix the spec, not the output — the same discipline as fixing the design system, not the screen.
The site you’re reading was built exactly this way — a sequence of specification files, an AI agent executing them, checkpoint commits, verified output at every step. The diagrams, the type system, the OG image: all of it specced in writing and built by an agent under direction. I’m not describing a workflow I read about. You’re standing in it.
Design is leaving the screen.
The interfaces I’ve spent twelve years designing assume a human is looking at them.
That assumption is expiring.
AI agents now read, navigate, and act on digital products directly — which means experience design is becoming architecture: structuring systems so that both humans and machines can use them well.
That’s the bet my work is converging on.
I’m not waiting for it to be obvious.