On this page

The UX design process is the sequence a team follows to turn what it learns about users into a product they can use. In practice it has six stages: research, define, ideate, prototype, test and hand off to developers. The stages loop, so when a test shows a problem you go back before you build.

This guide walks through each stage, compares it with the Double Diamond, and gives a 20-point handoff checklist. If every screen in your product was designed by whoever built it, SaaS design services is where we take a product from user flows and wireframes to developer handoff.

What is the UX design process?

The UX design process is a repeatable set of stages for designing a product around the people who use it. User experience (UX) design covers what the product does for a user and how each task flows. The process exists so that decisions rest on evidence about users, not on the opinion of the last person in the room.

The international reference is ISO 9241-210:2019, the International Organization for Standardization's standard for human-centred design of interactive systems. ISO lists it as Edition 2, last reviewed and confirmed in 2025. Its abstract says it gives requirements and recommendations for human-centred design principles and activities throughout the life cycle of computer-based interactive systems. The last part matters: design is not a phase that ends when development starts.

Sources count the stages differently. You will see five, six or eight steps for the same work. The count matters less than two rules of order: understand the problem before you design, and test the design before you build it.

The UX design process steps, stage by stage

The process has six steps: research, define, ideate, prototype, test and handoff. Each stage produces an output that supports one decision, and each has a typical price when a team skips it. The table gives the short version.

The six stages: the output of each, the decision it supports and the risk of skipping it
StageOutputDecision it supportsRisk of skipping
ResearchEvidence about users and tasksWhich problem is worth solvingA product built on a guess
DefineProblem statement and user flowsWhat is in scopeScope that grows every week
IdeateSeveral sketched optionsWhich approach to prototypeThe first idea ships untested
PrototypeWireframes, then a clickable modelWhat to put in front of usersProblems found only in code
TestObserved results on real tasksBuild, change or dropCustomers find the flaws
HandoffSpecified screens and statesWhat engineering buildsEngineers invent the gaps

1. Research

Research collects evidence about who the users are, what they are trying to do and where they struggle today. Interviews, observation, support tickets and product analytics all count. The output is a short list of findings the team agrees on. A user persona template is one way to keep those findings in front of the team.

2. Define

Define turns the findings into a problem statement and a set of user flows: the steps a user takes to finish each task. This is where scope is set. A flow that does not serve the problem statement is cut here, while cutting is still cheap.

3. Ideate

Ideate produces several rough answers to the same problem before the team commits to one. Sketches on paper are enough. The point is comparison: a team that draws three options and picks one knows why it chose, and a team that draws one does not.

4. Prototype

Prototype builds the chosen option as wireframes, then as a clickable model. Keep the fidelity as low as the question allows. The GOV.UK Service Manual is the UK government's guidance for digital teams. It makes the same point about its alpha phase: you do not have to prototype everything a user will do, only enough to test your riskiest assumptions.

5. Test

Test puts the prototype in front of real users and watches them attempt real tasks. The output is what they did, not what they said they liked. Our guide to usability testing questions covers what to ask, and usability testing services is the page for having the sessions run for you.

6. Handoff

Handoff gives engineering everything needed to build the design without guessing. It is the easiest stage to cut short, and it has its own section below.

The UX design process and the Double Diamond

The Double Diamond describes the same process as two diamonds: the first finds the right problem, and the second finds the right solution. The UK's Design Council launched it in 2004. Its page on the Double Diamond names four phases: discover, define, develop and deliver.

Each diamond opens and then closes. Discover and develop widen the options, while define and deliver narrow them. The six stages in this guide fit inside the four phases, and they also line up with the delivery phases in the GOV.UK Service Manual. The mapping below is approximate, because each model cuts the same work at different points.

An approximate mapping of the six stages to the Double Diamond phases and the GOV.UK Service Manual phases
StageDouble DiamondGOV.UK phase
ResearchDiscoverDiscovery
DefineDefineDiscovery
IdeateDevelopAlpha
PrototypeDevelopAlpha
TestDeliverAlpha, then beta
HandoffDeliverBeta

None of the three models is a straight line. The Design Council notes that teams often learn something that sends them back to the beginning, and that no idea is ever finished. The GOV.UK live phase is about continuing to iterate and improve the service.

Where UI fits in the UI UX design process

User interface (UI) design is the visual layer added once the flow works: layout, type, colour, spacing and components. UX decides what the screen must do. UI decides how it looks and behaves while doing it.

The order matters. Polished screens invite comments on colour, when the question at the prototype stage is whether users can finish the task. So test the flow in plain wireframes first, then apply the visual design. If the team has no shared components yet, our guide on how to create a design system shows the smallest kit worth building.

Developer handoff: a 20-point checklist

Developer handoff is complete when an engineer can build every screen without inventing anything. Whatever the design leaves out, engineering fills in under deadline, one developer at a time, and the product can end up with several different error messages for the same failure.

The fix is a checklist run on every screen before it leaves design. Ours has 20 checks in six groups.

  • States (6). Empty, loading, error, partial data, no permission and success. Draw the error state first: it is the one a user meets at the worst moment.
  • Data (3). The longest name the field allows, zero items, and thousands of items.
  • Layout (3). The smallest supported screen, the largest, and text enlarged by the user.
  • Access (3). Keyboard order through the screen, a visible focus indicator, and a text name for every control. The W3C's Web Content Accessibility Guidelines are the reference.
  • Copy (3). Final button labels, error messages that say what to do next, and the text for the empty state.
  • Tracking (2). Event names for the key actions, and the measure that will show the design worked.

For a software-as-a-service (SaaS) product, the states group carries the most weight. A dashboard is empty on day one, half-loaded on a slow connection, and partly hidden for a user without the right role. A design that shows only the full, happy screen covers one of the six states.

Handoff also needs a shared definition of done. Acceptance criteria written beside each flow give design, engineering and testing one statement to check against. Our user stories examples show the format.

When to loop back to an earlier stage

Loop back when the evidence contradicts the stage you are in, and go back only as far as the evidence points. The signal tells you where to return.

Four signals that send a team back to an earlier stage of the process, the stage to return to and the reason
SignalGo back toWhy
Users cannot finish the core taskPrototypeThe flow is wrong, not the idea
Users finish it but do not want itResearchThe problem was misread
A state cannot be built as drawnPrototypeRedesign it with engineering
Usage drops at one step after launchTestWatch users at that step

Looping back is the process working as intended. A flaw found at the prototype stage costs a redrawn screen. The same flaw found after launch can cost a release, a data fix and some of your users' patience.

How much process a small team needs

Scale the process to the risk of the change. A label change needs none of it. A new onboarding flow deserves all six stages, even in a compressed form: a handful of interviews, one page of flows, sketches, a clickable prototype, a round of tests and the handoff checklist. What a small team should not do is skip straight from an idea to production code on anything a customer will depend on.

How we run UX design with your team

We work with product teams whose engineers keep asking what happens in the edge cases, and with founders whose product grew one screen at a time. We start from your users and your existing product, then take the work from user flows and wireframes through tested prototypes to a handoff that passes the checklist above. That is the core of our SaaS product design work.

If the product is live and you want to know where it loses people before redesigning anything, UX audit services is the better first step. Every engagement is under an NDA, and the IP is always yours. Each project is different, so we quote it after a short call.

Frequently asked questions

What are the steps in the UX design process?

There are six steps: research, define, ideate, prototype, test and handoff. Research and define establish the problem. Ideate and prototype produce a possible solution. Test checks it with real users, and handoff specifies it for engineering. Some sources merge or split steps, so you will also see five-step and eight-step versions of the same work.

What is the UX design process Double Diamond?

The Double Diamond is a model of the design process launched by the UK's Design Council in 2004. It has four phases: discover, define, develop and deliver. The first diamond explores and then narrows the problem. The second explores and then narrows the solution. It describes the same work as the six stages, grouped differently.

How is UI design different from UX design?

UX design decides what a product does for the user and how each task flows from start to finish. UI design decides how each screen looks and responds: layout, type, colour and components. When the two are combined, the UX work comes first, because a good-looking screen cannot rescue a flow that users cannot complete.

Is the UX design process linear?

No. The stages run in order the first time, but any stage can send you back. A failed usability test returns the team to the prototype, and a finding that users do not want the feature returns it to research. The Design Council says of its own model that no idea is ever finished.

What should a UX design process diagram show?

The diagram should show the stages in order, the output of each, and the arrows that lead back to earlier stages. A straight line of boxes is the common mistake, because it hides the loops. If the diagram is for your own team, add who owns each stage and what decision ends it.

What does a developer handoff include?

A developer handoff includes every screen in every state, the rules for extreme data, the layout at each supported size, keyboard and focus behaviour, final copy and the tracking events. It also names the acceptance criteria for each flow. The test is simple: an engineer should be able to build the feature without asking what happens next.

Sources and update history

  1. ISO 9241-210:2019, Ergonomics of human-system interaction, Part 210: Human-centred design for interactive systems (catalogue page)iso.orgCHECKED 20 NOV 2026
  2. Design Council, The Double Diamonddesigncouncil.org.ukCHECKED 20 NOV 2026
  3. Design Council, Framework for Innovationdesigncouncil.org.ukCHECKED 20 NOV 2026
  4. GOV.UK Service Manual, Agile deliverygov.ukCHECKED 20 NOV 2026
  5. GOV.UK Service Manual, How the alpha phase worksgov.ukCHECKED 20 NOV 2026
  6. GOV.UK Service Manual, How the beta phase worksgov.ukCHECKED 20 NOV 2026
  7. GOV.UK Service Manual, How the live phase worksgov.ukCHECKED 20 NOV 2026
Update history
  1. First published.