Skip to content
Tutorials Center
My learning

Topics

Lesson 34 of 36 ยท Projects and Practice

Project: Redesign a Checkout Flow

A guided UX project: audit a weak checkout, define problems, map the flow, wireframe a better version, test it and measure the improvement, with runnable tools.

In this project you take a clumsy checkout and improve it using the whole process: audit, problem definition, flow mapping, wireframing, prototype, test and measurement. You can do it on paper, in any design tool, or with the small code stand-ins here. The product is fictional; all numbers are invented for practice.

The brief

Shop "Northpeak" sells outdoor gear. Its checkout has a 38 percent completion rate among people who start it. Support receives many messages such as "I could not find the promo code box" and "It asked me to create an account". Goal: raise completion without hurting order accuracy or increasing refunds.

Step 1: Audit the current checkout

Run a heuristic review of the current flow. A sample of findings:

  • Forced account creation before checkout (flexibility, user control).
  • Six pages, with no progress indicator (visibility of status).
  • Shipping cost appears only on the last page (match with the real world; trust).
  • Form errors appear at the top of the page after submit, without pointing to the field.
  • Promo code field is hidden behind a tiny link.
  • Fields are small on phones; the numeric keyboard is not used for card numbers.
Python Rank the problems

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Step 2: Define the problem and success

Turn the top issues into a problem statement and measurable goals:

Shoppers who want to buy abandon checkout because it asks for too much too early and hides total cost. We will make the full cost visible early and allow guest checkout, so completion rises from 38 percent to at least 50 percent.

Choose a primary metric (checkout completion rate) and guardrails (refund rate, payment failures, page load time).

Step 2b: Map the new flow

flowchart LR
  C["Cart<br/>(shows total with shipping)"] --> A["Contact + shipping<br/>(guest allowed)"]
  A --> P["Payment"]
  P --> R["Review and place order"]
  R --> OK(["Confirmation<br/>+ optional account"])
  P -. "card declined" .-> P

Figure: three steps with a visible progress indicator, guest checkout and an optional account created after purchase.

Make decisions explicit: estimate shipping from a postcode in the cart, offer address autocomplete, save card details only with consent, and offer account creation on the confirmation page.

Step 3: Wireframe the key screens

Sketch mobile first. Required elements per screen: progress indicator, order summary, one primary button, clear back path, inline validation and an error state. Annotate the behavior (for example "Pay button disabled until the form is valid; shows spinner while processing").

Inline-validated payment form

This is a stand-in for a payment screen: it takes no real card data and does not submit anywhere. Never put a real card number in a prototype.

Step 4: Test it

Write three tasks as scenarios (see test planning): "Buy the jacket as a guest and use code WELCOME10", "Change the shipping address after reaching payment", and "Recover when your card is declined". Test with five participants on the prototype, moderate neutrally, record success and errors, and fix severity 3 to 4 issues before another round.

Step 5: Measure

If you ship, run an A/B test of old versus new. Watch completion rate and guardrails. Report the result with a confidence interval.

Python Compare before and after

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

The intervals do not overlap, a good sign. Remember these numbers are practice data, not real results.

Deliverables checklist

  • Audit and ranked issues.
  • Problem statement and metrics.
  • New flow diagram with error paths.
  • Annotated mobile wireframes with states.
  • Test plan and a findings table.
  • Before and after metrics, plus lessons learned.

Check your understanding

Quick check ยท 3 questions

of 3 answered You scored / 3 ยท perfect!

  1. 1. Which change most directly addresses 'shipping cost surprises users on the last page'?

    Showing the full cost early builds trust and prevents late abandonment.
  2. 2. Why include guardrail metrics?

    A win on one metric can hide harm elsewhere.
  3. 3. Why not use a real card number in a prototype?

    Use fake or clearly marked test values in all prototypes and test sessions.

Summary

  • Audit first, then rank issues and write a measurable problem statement.
  • Map the new flow with error paths; design mobile first with inline validation and visible costs.
  • Test with scenarios, fix the severe issues, and verify with metrics and guardrails.
  • Keep a deliverables checklist so the work can go into a portfolio.

Next: Project: Build a Portfolio Case Study