I start every project by understanding what already exists: the history, the constraints, who is talking to whom. Only then do I propose anything. In large organizations, that step saves more time than any shortcut later.

From there, I make ideas tangible early, so engineers, business owners, and users can react to something real instead of debating abstractions. A prototype or a component is not a deliverable for me. It is how a team gets aligned.

I've applied this on sales tools, internal platforms, and enterprise AI, across markets and regulated environments. The through line is the same: a design system that people actually adopt, because they helped shape it.

Outside of work, I make photobooks and explore sequential image. That practice lives on Labs.