How I think. How I work.

Understand — Research & Context

Every project begins with building a genuine understanding of the problem space. This means going beyond briefs and requirements - speaking directly with users and stakeholders, mapping existing processes, and understanding the technical and organisational constraints that will shape what's possible.

The depth of this phase directly determines the quality of everything that follows. I don't treat research as a box to tick. I treat it as the foundation everything else is built on - and I invest in it accordingly.

Define — Synthesis & Principles

Raw research becomes meaningful only once it's synthesised into a clear picture of user needs, organisational goals, and design constraints. I translate complex findings into user archetypes, process flows, and experience documentation - and distil these into a set of UX principles that guide every subsequent decision.

These principles are not decorative. They're working tools - used to assess trade-offs, resolve stakeholder conflicts, and keep the team aligned as scope evolves.

Design — Flows, Wireframes & Prototypes

With context established and principles defined, design decisions become clear rather than arbitrary. I work from low-fidelity concept sketches through to build-ready high-fidelity wireframes - moving at a pace appropriate to the project's needs and always keeping feasibility front of mind.

The work spans end-to-end user flows, interaction models, mobile-first wireframes, and interactive prototypes.

With the rise of AI, using it to accelerate this work has become imperative - but always with appropriate guardrails and validation. For now I lean on it for idea generation and exploratory work, where it widens the range of options quickly, rather than for final designs, where judgement and craft still have to be mine.

Validate — Testing & Stakeholder Alignment

Design without validation is speculation. I build validation into every phase - not just as a formal testing exercise, but as a continuous practice of checking assumptions, surfacing risks early, and iterating with confidence. This includes moderated usability testing, stakeholder workshops, focus groups, and rapid feedback loops.

The goal isn't sign-off. It's genuine alignment - the kind that holds when the project gets difficult, scope shifts, or teams change.

Deliver — Handover & Enablement

Design that's communicated badly breeds ambiguity, and ambiguity leaves room for the experience to be translated incorrectly. So I treat handover as collaboration rather than a document drop - working closely with developers through the build to make sure they have everything they need to build the product as intended, and the context to make sound calls when something doesn't translate cleanly.

Feasibility is a big part of this. Sometimes a strong design has to change to be built well, and I'd rather have that conversation early and openly with the build and delivery teams than discover the gap late. Less documentation for its own sake; more shared understanding, with design and engineering working from the same picture.