UX/UI for AI-native, workflow-heavy products.

I focus on how work moves through the system, who is involved, where risks appear, and what should be automated or kept human. I model information architecture, states, permissions, decision points, and orchestration rules so the product is clear, auditable, and ready to ship. The design system is where that model becomes reusable across a product instead of solved once per screen.

I consider delivery constraints early, including team capacity and rollout plan, ensuring the design is realistic and ready for future growth. My goal is to improve activation, adoption, and retention — not just usability — and shape systems that remain effective as the product evolves. On Strata, this discipline extended to a B2B2C layer — I designed the checkout and tracking flow for client-facing sales pages, delivered as wireframes and a front-end prototype, with a deterministic customer-facing boundary.

A design system has three layers, and only one of them says anything about how a designer thinks: the primitives are table stakes, the components are a catalogue, and the layer above is where judgment lives — uncertainty, provenance, generation state. That last layer is what I published at /storybook, because it is the one no library ships and the one that decides whether people trust an AI feature.