About

I'm a Staff Product Designer focused on enterprise SaaS, currently working on AI-driven legal technology.

People bring me in when things are unclear, risks are high, and the team needs clarity before moving forward. Over 20 years I've worked in complex, fast-moving environments where design is about helping people make good decisions — not just good interfaces.

I don't start by designing screens.

I start by figuring out what decisions need to be made, what trade-offs are involved, and what could go wrong. Then I work with teams to pause, get clear on the problem, agree on guiding principles, and decide together what good looks like.

Most of this happens before we touch UI. It's conversations, decision models, building a shared language for how we judge ideas. When we finally design interfaces, those choices are already clear.

Lately I've been focused on designing AI-assisted workflows for legal and enterprise teams.

The challenge isn't just figuring out what AI can do — it's knowing when it should step in and when it shouldn't. I've led design work where trust, defensibility, and accountability matter more than automating everything.

This means building in clarification steps, requiring evidence before automating, keeping AI outputs separate from human judgment, and helping teams move at the right speed for the problem. My job is often making risk visible so leaders can make smart trade-offs instead of hoping for the best.

I've led design system work across product suites spanning web, Word add-ins, and Outlook — consolidating 25 acquired products into a shared foundation and shipping the first unified product in six months.

This meant architecting token systems from scratch, building component libraries across multiple platforms, and leading migration from one framework to another without blocking delivery. Just as important was helping teams rethink how they reuse, stay flexible, and reduce long-term cost.

The real outcome wasn't a design system. It was teams spending less time re-solving the same problems and more time on the work that actually matters.

As a Staff designer, I bring clarity, help teams get aligned, and make sure decisions are ones they can stand behind.

I don't just go along with everything. I point out tensions, question assumptions, and slow things down when moving too fast would cause problems later. I've learned that a single design voice often isn't enough — finding the right ally, someone whose perspective the room will hear, is part of the work.

I mentor designers to think in systems, see the broader impact, and design with purpose rather than just output.

I'm based in Toronto. I've been writing — as a designer, as a researcher, and for myself — for as long as I've been designing. It's how I think through problems and how I've built this portfolio over 20 years.

The case studies on this site show work where the biggest impact wasn't a new feature, but better decisions and clearer direction. That's the work I find most interesting.