Home / Blog / Website design and development

The UI/UX design process, step by step

By MarketAlong teamPublished 14 November 20266 min read

Two colleagues planning on a whiteboard covered in sticky notes

From the outside, website design can look like one step: someone draws a nice page and someone else builds it. Inside the best studios it is a sequence, and each step removes a specific risk, such as solving the wrong problem or discovering on launch day that people cannot find the button. This guide walks through the five core stages and shows how they fit into a complete website project.

In short

  • Good design is a sequence: research, define, ideate, design and prototype, then test and iterate.
  • Each step removes a risk, from solving the wrong problem to launching something people cannot use.
  • A complete project adds content, build, testing, search readiness, launch and ongoing care.
  • Your input matters most at the start, at the wireframe stage and just before launch.
A designer working on a layout on a desktop computer

UX and UI: two halves of one job

UX, user experience, is how something works: whether people can find, understand and complete what they came for. UI, user interface, is how it looks and feels. Good UI with poor UX is attractive and frustrating; good UX with poor UI works but fails to earn trust. The process treats them as one piece of work.

Two colleagues leaning over printed pages at a table

Step 1: Research

Research replaces guesses with evidence: who the visitors are, what they are trying to do and what gets in their way. Short interviews, surveys, watching people use the current site and reading analytics all count. Design based on intuition alone tends to serve the people in the room, not the people who will use the site.

Your part. Introduce the designers to real customers, share the questions people ask your team and open your analytics.

Step 2: Define

The research becomes a clear statement of the problem: who the site is for, what they need to achieve and what success looks like. Short personas, journey maps and a list of requirements keep everyone aligned and stop the project building features nobody asked for.

Four colleagues gathered around a laptop in a bright room

Step 3: Ideate

The team explores many possible answers before choosing one: sketches, user flows and quick layouts. The common mistake here is falling in love with the first idea, which is rarely the best.

Step 4: Design and prototype

Structure comes first: the site map, user flows and simple grey wireframes that fix what goes where. Visual design then adds brand, type, colour and imagery. A clickable prototype lets people try the site before it is built, which is the easiest moment to find and fix problems.

Two colleagues discussing a website shown on a desktop computer

Step 5: Test and iterate

Real people try the prototype while the team watches where they hesitate or give up. Findings lead to changes, and changes are tested again. It is a loop, not a straight line.

How the steps fit into a whole project

A complete website project wraps those five stages in the work that takes a tested design live and keeps it healthy:

StageWhat happens
MissionPurpose, audience and a few measurable goals are agreed
RoadmapThe site map, key pages and reusable components are planned
Wireframes and prototypeLayouts are fixed, tested, then given their visual design
ContentClear, useful words are written for each page
BuildDevelopers create the working site, watching speed from the start
TestingLinks, forms, speed and accessibility are checked on phones and computers
LaunchThe site goes live with analytics and a way to roll back if needed
CareFixes and improvements continue based on real use
A presenter pointing at charts on a large screen while colleagues watch

Where projects most often go wrong

  • No agreed definition of success
  • Planning single pages instead of the system behind them
  • Writing content last, which delays launch
  • Treating speed and accessibility as extras
  • Treating launch as the finish line

Your part as the client

Your input matters most at three moments: at the start, when you share what you know about customers; at the wireframe stage, when structure is still easy to change; and before launch, when you check every form, number and promise on the site.

Changes are easiest on paper, harder in a prototype and hardest once the site is built. Give your biggest feedback early.

Common questions

Two questions people ask before their first project.

Do small websites need the whole process?

They need every step, but each step can be small. A short conversation with a few customers is still research.

What should I look for in a design partner's process?

Evidence that they research before they design, test before they build and keep improving after launch. Our guide to choosing a web design company lists the questions to ask, and web design principles shows what good work should achieve.

This guide is for general education. To see how MarketAlong runs a project, read about our website development service. Once your site is live, our guide to search engine optimisation for small business explains how customers find it.

Need help with website development?

Tell us what you want to improve in a few lines. A person replies by email with questions or a recommended scope. No call is required.

Get a website project scope