Skip to content
UxerProof
UxerProofDemo data

Circuit report

Guest checkout — single item

A first-time visitor on mobile attempts to buy one item without creating an account. The journey completed, but three friction points cost more than a minute of hesitation and one of them changes the price after the address form.

Project
Northwind Storefront
Environment
Production · verified
AI User
Maya · First-time buyer · mobile
Run
run_4821 · 214s · 1 credit

1. What works

The item was added, delivery details were accepted and the order completed with a recoverable reference. These statements come from the recorded journey below.

Circuit Canvas

run_4821 · Guest checkout — single item

  1. 01

    Land on storefront

    Completed

    Product and price were visible without scrolling.

    Maya · 2.4s

  2. 02

    Choose size

    Friction

    Sold-out sizes look identical to available ones until tapped. Maya tried two unavailable options first.

    Maya · 18.6s

  3. 03

    Add to bag

    Completed

    Bag count updated and a toast confirmed the addition.

    Maya · 1.9s

  4. 04

    Guest or account

    Friction

    Guest checkout is a text link below a full-width 'Create account' button. Maya hesitated before finding it.

    Maya · 22.4s

  5. 05

    Enter delivery details

    Friction

    Postcode validation failed twice with the message 'Invalid input' and no indication of expected format.

    Maya · 46.2s

  6. 06

    Review total

    Friction

    A delivery surcharge appeared for the first time on this step.

    Maya · 12.8s

  7. 07

    Confirm order

    Completed

    Order reference displayed and copied successfully.

    Maya · 5.1s

Outcome: Journey completed with friction

214s · 1 credit

78Proof

Proof Score

Every assessed point is traceable to evidence in the Run; unassessed dimensions remain visible.

  • Completion100/100

    Did the AI User reach the intended outcome of the journey?

  • Friction61/100

    How much hesitation, backtracking and repeated effort occurred?

  • Clarity70/100

    Were labels, states and system responses understandable in context?

  • Accessibility74/100

    Keyboard reachability, focus order, naming and contrast along the path.

  • Consistency85/100

    Did patterns behave the same way across steps and roles?

2. Where users struggle (3)

Each finding names the step where the behaviour occurred, what the AI User experienced and the smallest change that would remove the friction.

highClarityopenfnd_1

Sold-out sizes are visually identical to available sizes

at step · Choose size

Unavailable variants use the same border, colour and hit area as available ones. The AI User selected two unavailable sizes before succeeding.

Recommendation

Mark unavailable variants with a non-colour indicator, disable the control and expose the state to assistive technology.

mediumFrictionopenfnd_2

Guest checkout is visually subordinate to account creation

at step · Guest or account

The guest path is a small text link under a full-width primary button, adding 22 seconds of hesitation at the highest-intent step.

Recommendation

Give both paths equal visual weight, or lead with guest checkout and offer an account after purchase.

criticalClarityacknowledgedfnd_3

Delivery surcharge disclosed only at the review step

at step · Review total

A delivery surcharge appears for the first time after the address form, changing the expected total.

Recommendation

Disclose delivery cost, or an explicit range, on the product and bag steps.

Evidence-backed

3

Validate-first hypotheses

0

Selected for next release

2

Ranked by observed impact, implementation effort and evidence confidence. Expected outcomes remain estimates until a comparable rerun validates them.

What the experience could become

Every recommendation below resolves to retained evidence from this exact Run.

Journey: Guest checkout — single item
PossibilityTrust Reassurance

Show the delivery range before the address form

Selected

The final total changed only after the address form. The AI User returned to the bag to check whether a cost had been missed.

What it could become

Show a destination-aware estimate in the bag, then explain any final adjustment before the address is submitted.

Expected outcome

Users may reach review with greater price confidence; a comparable rerun must verify the change.

Impact
High
Effort
Medium
Confidence
High
Implementation and validation

Direction

Add a delivery estimate beside the bag total with an explicit explanation of what can still change.

Validation criteria

  • Rerun the same mobile guest-checkout Circuit.
  • Confirm the AI User sees the delivery range before submitting the address.
  • Confirm no unexpected price change causes backtracking at review.
View evidence
PossibilityTime To Value Wow moment

Let visitors experience checkout before asking for an account

Proposed

The AI User paused for 22 seconds because the guest path appeared beneath the account-creation action.

What it could become

Lead with guest checkout and offer account creation after the order is confirmed, with the entered details carried forward.

Expected outcome

Users may reach checkout value sooner and feel less commitment pressure; this is an estimate until rerun.

Impact
High
Effort
Medium
Confidence
High
Implementation and validation

Direction

Promote guest checkout to the primary path and move optional account creation to the confirmation step.

Validation criteria

  • Rerun with the same first-time mobile persona and success criteria.
  • Confirm guest checkout is found without backtracking or a prolonged pause.
View evidence
PossibilityAccessibility

Make every available size obvious on the first attempt

Selected

The AI User selected two unavailable sizes because available and sold-out controls looked identical.

What it could become

Unavailable sizes are disabled, visibly labelled and announced, while available sizes remain easy to compare.

Expected outcome

Users can select an available size without the two failed attempts observed in this Run.

Impact
High
Effort
Low
Confidence
High
Classification
Quick win
Implementation and validation

Direction

Use native disabled state, a non-colour sold-out marker and an accessible description per variant.

Validation criteria

  • Repeat the size-selection step with the same viewport.
  • Confirm unavailable controls cannot be selected and expose their state without colour alone.
View evidence

Evidence-backed comparison

Current journey → potential journey

This is a proposed path, not a measured improvement. Validate it by rerunning the same conditions and success criteria.

Current observed journey

  1. Land on storefront

    Product and price were visible without scrolling.

  2. Choose size

    Sold-out sizes look identical to available ones until tapped. Maya tried two unavailable options first.

  3. Add to bag

    Bag count updated and a toast confirmed the addition.

  4. Guest or account

    Guest checkout is a text link below a full-width 'Create account' button. Maya hesitated before finding it.

  5. Enter delivery details

    Postcode validation failed twice with the message 'Invalid input' and no indication of expected format.

  6. Review total

    A delivery surcharge appeared for the first time on this step.

  7. Confirm order

    Order reference displayed and copied successfully.

Proposed potential journey

  1. Land on storefront

    Keep this verified step.

  2. Choose size

    Unavailable sizes are disabled, visibly labelled and announced, while available sizes remain easy to compare.

  3. Add to bag

    Keep this verified step.

  4. Guest or account

    Lead with guest checkout and offer account creation after the order is confirmed, with the entered details carried forward.

  5. Enter delivery details

    Keep this verified step.

  6. Review total

    Show a destination-aware estimate in the bag, then explain any final adjustment before the address is submitted.

  7. Confirm order

    Keep this verified step.

Intended value moment

See a confirmed order with a recoverable reference.

Wow Moment Finder

  • Let visitors experience checkout before asking for an account

    Lead with guest checkout and offer account creation after the order is confirmed, with the entered details carried forward.

    Inspect supporting evidence

What to build next

A lightweight release decision—not a replacement for your delivery system.

Quick wins (1)

High-value changes with lower implementation effort.

  • Make every available size obvious on the first attempt

    Selected
    Evidence

Strategic improvements (1)

Material journey changes that deserve deliberate delivery.

  • Show the delivery range before the address form

    Selected
    Evidence

Validate first (0)

Hypotheses or assumptions to test before committing deeply.

Nothing selected.

Before/after proof

No comparable rerun has been evaluated yet. Mark a selected improvement ready to validate, rerun the same Circuit, then compare the retained evidence here.

Evidence

Retained evidence only. Raw artefacts from this Run were deleted 24 hours after synthesis.

Evidence Timeline

Ordered by capture time. Raw artefacts are encrypted and auto-deleted within 24 hours of report generation.

  1. 00:00
    Screenshot

    Storefront above the fold

    Viewport 390×844. Product title, price and primary action captured.

    step 01 · raw artefact expires in 24h

  2. 00:01
    Timing

    First meaningful paint

    1.24s on a simulated 4G connection.

    step 01

  3. 00:04
    Issue

    Unavailable variants indistinguishable

    Sold-out sizes share the same border, text colour and hit area as available sizes.

    step 02

  4. 00:23
    Observation

    Add-to-bag confirmed

    Bag counter incremented and a toast persisted for 4 seconds.

    step 03

  5. 00:26
    Screenshot

    Guest checkout decision point

    Guest path rendered as a 13px text link beneath a full-width account button.

    step 04 · raw artefact expires in 24h

  6. 00:51
    Response

    Validation response

    Redacted

    Form returned status 422 with the body summarised as: field 'postcode' rejected.

    step 05 · raw artefact expires in 24h

  7. 00:58
    Issue

    Unhelpful validation message

    'Invalid input' shown twice with no expected format and no inline recovery guidance.

    step 05

  8. 01:32
    Issue

    Late fee disclosure

    A £4.95 delivery surcharge appeared only at the review step.

    step 06

  9. 01:58
    Screenshot

    Order confirmation

    Redacted

    Order reference visible, copy control present and labelled.

    step 07 · raw artefact expires in 24h

Role Handoff Map

1 role · 0 handoffs in this Circuit

MayaParticipant
  1. Land on storefront
  2. Choose size
  3. Add to bag
  4. Guest or account
  5. Enter delivery details
  6. Review total
  7. Confirm order

This Circuit runs with a single role. Role Circuits add reviewer and approver handoffs.

Against the Baseline

This Run is compared with the approved Baseline for the same Circuit.

Before / After Proof

Guest checkout — single item

Baseline

Baseline — Checkout v3

run_4602

71

Proof Score

Candidate

Candidate — build 1184

run_4821

78

Proof Score

Dimension comparison between baseline and candidate
DimensionBaselineCandidateChange
Completion1001000
Friction4861+13
Clarity5870+12
Accessibility7174+3
Consistency8085+5
Journey duration301s214s-87
Open findings63-3

Resolved

  • Postcode format now shown inline
  • Bag confirmation persists on mobile

Regressed

  • Delivery surcharge moved one step later in the flow

Possibilities validated

  • Postcode guidance prevented the earlier validation loop

Possibilities disproved

  • The earlier price disclosure change did not prevent backtracking

This report is fictional. Yours would not be.

Northwind Labs is an invented company and no real website was tested to produce this page.

Run a Proof Circuit