The human in the loop, on paper too.

I started in graphic design and moved into product design because I cared more about how something works than how it looks. Since then I've built a design system from scratch for a live SaaS product, led a small creative team on a physical/digital product in San Francisco, run a full discovery practice at an edtech platform, taken a hotel chain's voice assistant from zero to production, and, most recently, designed the human-in-the-loop layer of an AI-agentic product.

I've worked solo more often than not, usually alongside two or three engineers with no dedicated PM or researcher. That means I do the research, the design, and the pushing back on scope myself, often in the same week. It's made me practical: I care more about shipping something complete than about defending one deliverable.

Over the last two years, my work has come back to one thing: confirmation before action. As AI agents started doing real things inside products, like sending something or changing a record, I kept running into the same question in user research: does the person on the other end get to see what's about to happen before it happens? My case studies come out of that research. I was asking that question before "human-in-the-loop" became a phrase people throw around for AI products.

Designing for an agent that can act on its own has also changed how I think about a "user journey." Before, I could map clear stations, before, during, after, and design each one. With AI, there's no fixed sequence anymore, the agent can end up almost anywhere depending on what someone asks, so the work is more iterative: shape a direction, test it in motion, adjust. I felt the first version of this on Meliá's voice assistant years ago; with an agent that can act, not just answer, it's impossible to ignore.

I also use AI in my own process, daily: Claude for research synthesis, documentation, and increasingly for building working prototypes I can put in front of people instead of static mockups. Most of the interactive demos on this site were built that way.