Interface design where every state is designed, not left to chance

Interface design is where decisions meet users

Everything upstream - research, information architecture, flows, prototypes - eventually becomes a screen someone uses. Interface design is the work of making those screens clear, consistent, accessible and buildable: choosing layouts, components, hierarchy, words and every state a screen can be in.

In complex products, the difference between a good and a mediocre interface is rarely in the headline screens. It is in the details that get skipped: the empty state, the loading state, the error message, the table with 400 rows, the long name that breaks the layout, the disabled button that doesn't say why.

What I design

Designing for dense, data-heavy products

Many of the products I design - enterprise SaaS, AI tools, healthcare operations platforms - are data-heavy. Density is not the enemy; disorder is. Principles I apply:

• Lead with what needs attention - exceptions, changes and actions before routine data.
• Summary first, detail on demand - progressive disclosure rather than cramming.
• One accent colour for action - so users learn what is clickable; status uses its own tested colours with text and icons.
• Disciplined tables - sticky headers, aligned numbers, units in headers, sensible default sorting, density options.
• Honest trust signals in AI products - sources, confidence and edit controls. See UX/UI design for data-heavy AI interfaces.

Accessibility is part of the interface, not an audit

Interfaces are where most accessibility failures are created - and where they are cheapest to prevent. WebAIM's 2026 analysis of the top million home pages found low-contrast text on 83.9% of them and missing form labels on 51%. Every interface I design meets WCAG 2.1 AA contrast for text, includes visible focus states and labelled form fields, and never relies on colour alone for meaning. For the method, see WCAG contrast testing for AI product UIs.

Consistency: design once, use everywhere

Interface design is most efficient when it builds a system as it goes. Each new component is designed with its states and rules so it can be reused, rather than redrawn per screen. Figma's research found designers with a design system completed a task 34% faster than without one - and engineers benefit in the same way. On products without a design system, I start one; on products with one, I work within it and extend it properly. See design systems & accessibility.

What you get