Designing the logic before the layout.

Eight years building B2B software for teams where getting it wrong has a cost.

What I focus on

Systems, not screens

Most interfaces fail before they look bad. I start with who can do what, when, and what happens when something goes wrong.

Design that ships

Handoff is where most design dies. I work in components, tokens, and code, close enough to engineering that nothing gets lost in production.

Less, on purpose

Most products don't suffer from missing features. They suffer from too many. I spend as much time deciding what not to build as what to build.

Understanding the strategic context—including long-term goals, core values, and insights into priorities—lays essential groundwork for successful feature design and development.

The deciding part

I use AI to generate, prototype, and explore faster. But someone still has to decide which solution is actually right. That part is mine.

Work

Piloting in two radiotherapy departments.

Healthcare Systems

Systems Design

LLM Product Design

Design Systems

Compliance & Safety

RadPass, a safety-critical clinical system, designed from scratch

Radiotherapy departments had no formal model for responsibility, machine state, or audit trail. As founding product designer, I defined the ownership logic, designed two clinical interfaces, and built the design system that holds it together. I prototyped in Bolt, feeding the design system into code to validate workflows before any engineering investment.

Three case-studies, one project

The product

Modelled the ownership logic and mapped every state, handover and edge case before designing a single screen.

Designing responsibility for radiotherapy →

The product

Modelled the ownership logic and mapped every state, handover and edge case before designing a single screen.

Designing responsibility for radiotherapy →

The design system

Built in code, not just Figma. The components in the file are the ones in production, across both interfaces.

One foundation. Two architectures. →

The design system

Built in code, not just Figma. The components in the file are the ones in production, across both interfaces.

One foundation. Two architectures. →

The assistant

Scoped what the LLM could see, tested that boundary myself, then shipped a docked panel that turns questions into charts.

An assistant that only knows what it's allowed to know. →

The assistant

Scoped what the LLM could see, tested that boundary myself, then shipped a docked panel that turns questions into charts.

An assistant that only knows what it's allowed to know. →

Shipped. Used by 125,000 users across Intermedia's customer base.

Product Ownership

Analytics UX

Data Visualisation

Design Systems

Intermedia Analytics, five years scaling a platform used by 125,000 users

A basic reporting tool that couldn't keep up with how customers ran their teams. As Lead UX Designer, I owned the analytics platform from inception, turning it into live wallboards, historical reports, and team dashboards.

Three case-studies, one project

The journey

Five years of deciding what the platform should become next, and what it shouldn't, as it grew from reports to real-time.

Scaling Intermedia Analytics →

The journey

Five years of deciding what the platform should become next, and what it shouldn't, as it grew from reports to real-time.

Scaling Intermedia Analytics →

The platform

Set the patterns, components, and data rules first, so every dashboard after it had a foundation to build on.

Designing the UX foundation for Analytics →

The platform

Set the patterns, components, and data rules first, so every dashboard after it had a foundation to build on.

Designing the UX foundation for Analytics →

Service adoption

Gave managers one view of how their teams actually use Unite, instead of piecing it together from separate reports.

Designing a Usage Insights Dashboard →

Service adoption

Gave managers one view of how their teams actually use Unite, instead of piecing it together from separate reports.

Designing a Usage Insights Dashboard →

Live · catchmetrics.io

Information Architecture

Data Visualisation

Design Systems

B2B SaaS

CatchMetrics, a Core Web Vitals platform anyone can read

Web performance tools were built for developers. CatchMetrics wanted the same data to make sense to everyone else. As founding product designer, I designed the full product: the information architecture, plain-language entry points, and a modular system that goes from "is my site slow?" down to debugging detail.

View Case Study

Chrome Extension · Shipped, live

Exploratory Research

Digital Security

Cryptography

Post-Quantum Security. 2026

"Who Runs Your Web" — a privacy scanner I designed, built, and shipped.

Scans your own browsing for third-party trackers and infrastructure concentration. 500 sites scanned to date, with an AI-powered pattern analysis feature. Built solo, end to end.

Try it / See how it works →

Designing the logic before the layout.