I like messy problems. The ones where nobody's quite sure what the real issue is yet, where the stakes are high and the path forward is not obvious. Most people want to skip past the ambiguity. I've learned that's usually where the real work is.

I think in systems. Not screens, not deliverables, but the underlying logic that holds a product together. The patterns that let teams build faster without painting themselves into corners. I've built pattern libraries from scratch, governed them as they scaled, and watched them outlive the projects that created them. That part never gets old.

I also care deeply about the experience on the other side of the system. The person trying to understand their retirement options, navigate a confusing enrollment flow, or make a financial decision that actually matters to their life. Getting that right is not a nice-to-have. It is the whole point.

I stay close to the problem from framing all the way through to ship. Prototyping, testing, defining edge cases, working directly with engineering until the thing in production matches the thing in Figma. I want to know how something actually behaves, not just how it looks in a deck.

I use AI the way I use any good tool. It handles the tedious stuff so I can spend more time on the decisions that require a human in the room. Lately that means building AI-ready systems, components architected so agents can assemble pages directly without a designer touching every output. That is where things are going. I would rather be building toward it than catching up later.