Case studies you can click

Most portfolio case studies are a long scroll of mockups with a paragraph of process on top. Hiring managers skim them in under a minute. I wanted mine to answer the question they're actually asking: how does this person think?

So I rebuilt every case study on this site around three things you can use, not just read.

1. Screen anatomy

Each project opens one real screen and splits it into zones. Every zone answers a question someone arrives with, like "where do I start?" or "is this the store or the company?", with a close-up and the principle behind it.

It forces me to explain decisions in the user's words instead of mine. If I can't name the question a zone answers, the zone probably shouldn't be there.

2. UX cases

Next, a short list of real questions, in the user's voice. Pick one and the screen that answers it swaps in, with a one-line answer. For Durham Region: "Did anything happen?" leads to the tracker that sits above the catalogue.

Under that sit three concepts of my own: ideas for gaps the shipped product still has, built as small working mock-ups. They're clearly tagged "not shipped". Mixing your own ideas into shipped work without saying so is the fastest way to lose a reviewer's trust.

3. A design system you can open

Every project now has an interactive design system explorer: tokens, colours, type, components and page templates, in that product's own brand. You can search it, copy a token, and click through templates.

The colours are sampled from the real screens, and anything I added for the library is labelled as an addition. Where a real colour failed contrast, the explorer uses a darker one and shows the failing pair on its accessibility page.

What I cut

Building this meant deleting a lot: long process paragraphs, adjective-only outcomes, numbers I couldn't source. Each case study now says what shipped, what was and wasn't measured, and the call I'd revisit.

It's still a portfolio, so it's still selective. But every claim on it is something I can show you.