I'm a product designer drawn to the structural work underneath an interface — the information architecture, the flows, the decisions about what a thing should even be. Get that right and the screens almost design themselves.
My instinct is to slow down and look at the actual work before drawing anything.
The tasks, the steps, the things people do all day — that's where good structure comes from. Structure that's grounded in real work holds up under pressure; structure you guess at falls apart the first time someone uses it for something you didn't anticipate.
That belief shaped my most recent project, Control Tower 2.0 — a full redesign of the internal operations platform every Ritchie Bros. support team relies on. I audited 51 real support actions before sketching a single screen, derived the whole architecture from how that work actually flows, and owned both the product definition and the design without a PM to lean on.
I like to prototype in HTML so I can test a flow before I make it pretty, and I log my reasoning as I go — because on a small team, the why behind a decision is as valuable as the decision itself. And I'm relentless about plain language: if a stakeholder in any role can't read the interface and understand it, it isn't finished.
When the architecture is right, people stop noticing the tool and just get their work done. That's the goal — not a clever screen, a quiet one.
Clear language is part of the interface, not a layer on top of it. I'd rather a label be obvious than impressive.
The most useful work often happens before the design — figuring out what the thing should be. I want to be in that part of the conversation.
Every real decision has a tradeoff behind it. I keep those visible, so the team can challenge the logic instead of just reacting to the result.
Led the redesign of Control Tower 2.0, the internal support & operations platform — migrating from Retool to React, grounding a six-section architecture in a 51-action SOP audit, and owning product definition alongside design on a two-person team.
Led the 2022 redesign of the mobile claims journey — cutting the questions from 30 to 20 and rebuilding the flow into focused, finishable steps for customers filing on a bad day.
Redesigned credit offer selection at checkout to support a third financing option, and built the end-to-end credit map that enabled a cost-saving code migration.
Titles and dates are placeholders — fill them in from your LinkedIn. Add any earlier roles in the same format.
[ Degree ]
[ School ] · [ Year ]
Add education, certifications, or relevant training from your profile. Remove this section if you'd rather lead with work.