Skip to content
Tutorials Center
My learning

Topics

Lesson 3 of 36 ยท Getting Started

The UX Design Process

Walk through the stages of a UX design process, from research and definition to ideas, prototypes, testing and launch, and learn why the loop repeats instead of running once.

Designers rarely jump straight to screens. They follow a process that reduces risk: learn first, decide second, build third, check at every step. The process has many names and diagrams, but the stages are consistent across teams. This lesson gives you a map you can adapt.

The main stages

  1. Understand. Gather what the business wants, what users need, what already exists and what constraints apply. Methods: stakeholder talks, interviews, analytics, competitor review.
  2. Define. Turn what you learned into a clear problem statement and goals. Without this, a team can solve the wrong problem very well.
  3. Ideate. Generate many options: sketches, flows, wild ideas. Quantity first, selection later.
  4. Prototype. Make a cheap, testable version: paper, a clickable mock-up, or a coded demo.
  5. Test. Put it in front of real users, watch, and learn what fails.
  6. Build and launch. Hand over to development with clear specs, then measure.
  7. Learn and iterate. Real usage produces new questions. Go round again.
flowchart LR
  A["Understand"] --> B["Define"]
  B --> C["Ideate"]
  C --> D["Prototype"]
  D --> E["Test"]
  E --> F["Build and launch"]
  F --> G["Measure and learn"]
  E -. "found problems" .-> C
  G -. "new questions" .-> A

The dotted arrows are the point: the process is a loop, not a straight line.

It is not strictly linear

Diagrams show tidy arrows, but real projects jump around. A usability test may send you back to ideation. A technical limit discovered in build may change the definition. That is normal. The goal of the process is to find mistakes while they are cheap. A flaw found on a paper sketch costs minutes; the same flaw found after launch costs weeks and trust.

A problem statement

Defining the problem is the step beginners skip. A good problem statement names the user, the need and the insight, without sneaking in a solution.

  • Weak: "We need a better dashboard."
  • Better: "Busy shop owners need to see today's orders at a glance because they check the screen between serving customers, and the current dashboard takes four taps to show them."

The better version tells you who, what, why and the evidence. It also gives you something to test: can the owner see today's orders in one glance?

Scale the process to the project

You do not run every method on every project. A tiny tweak, such as renaming a button, might need one quick test. A new product might need weeks of research. A helpful rule: the more it costs to be wrong, the more you check first.

Teams also differ in how they sequence work. Some run in Agile sprints, where design stays a sprint or two ahead of development. Others use Lean UX, which prefers hypotheses and fast experiments to long documents. The underlying loop of learn, make, check is the same.

A stand-in: tracking where a project is

The snippet is a stand-in that models the loop as data. It records which stage a project is in and what happens when a test finds problems. It is not a project-management tool; it shows that the process can move backwards.

JS The process as a loop (stand-in)

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Notice the path visits ideate, prototype and test twice. That is a healthy project, not a failed one.

Outputs at each stage

Each stage leaves behind something the team can use. These are called deliverables, and you will meet most of them in this course.

Stage Typical outputs
Understand Interview notes, research summary, competitor review
Define Problem statement, personas, journey map
Ideate Sketches, user flows, concept comparisons
Prototype Wireframes, clickable prototype
Test Findings list, prioritized issues
Launch Design specs, metrics dashboard

Common mistakes

  • Skipping research because "we already know our users". You often do not.
  • Falling in love with the first idea and using testing only to confirm it.
  • Testing too late, when the code is written and changes are expensive.
  • Treating the process as paperwork. Documents serve decisions; if nobody uses one, stop making it.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Why is the UX process drawn as a loop?

    Learning from tests and real use feeds new ideas and questions.
  2. 2. Which of these is a good problem statement?

    It names the user, need and reason without prescribing the solution.
  3. 3. What is the main benefit of prototyping and testing early?

    Changing a sketch costs minutes; changing shipped software costs far more.
  4. 4. Which rule scales the process to a project?

    Match the effort of research and testing to the risk.

Summary

  • The process: understand, define, ideate, prototype, test, launch, learn.
  • It loops; going backwards after a test is normal and healthy.
  • A clear problem statement keeps the team solving the right thing.
  • Scale effort to risk, and produce only deliverables that people will use.

Next: Design Thinking and the Double Diamond