← Selected Work

Case Study 03Monki

Ten friction points. Five revenue risks. One research brief that moved the needle.

A moderated usability test of Monki.com for a client — 5 recruited participants, 4 tasks, benchmarked head-to-head against PrettyLittleThing across 8 metrics, delivered as a prioritised roadmap. Five of ten recommendations were implemented.

Client
Monki (via agency)
Role
Solo UX Researcher & Designer
Study
Dec 2022 · 4 tasks × 2 platforms
Participants
5 recruited · moderated · think-aloud
Methods
A/B Usability Testing · SUS · NPS · CSAT · Paired T-Test · Card Sorting · Accessibility Audit
41.5
SUS — the "Poor" band, vs the competitor's 82.5 "Excellent"
30%
Task completion on Monki, vs 95% on the competitor
p=.003
Paired t-test — the gap was statistically significant
5/10
Recommendations implemented by the client

The short version

Four lines, the whole story

  • A client-commissioned, moderated usability test of Monki.com — benchmarked task-for-task against PrettyLittleThing.
  • 5 recruited participants ran 4 realistic shopping tasks on both sites, measured across 8 metrics.
  • Monki landed in the SUS Poor band with most tasks failed; the gap was statistically significant, not opinion.
  • Findings became a prioritised, costed roadmap — five high-priority recommendations shipped.

The question

Is Monki.com as usable as it is beautiful?

Monki: a Scandinavian fast-fashion brand for women 19–38, loved for its look. In 2022, through an agency commission, I was asked to find out whether the website deserved the same reputation.

  • Benchmark Monki.com head-to-head against a leading competitor (PrettyLittleThing).
  • Locate the friction driving abandonment, with evidence the product team can't dismiss.
  • Deliver a prioritised roadmap — not a report that sits in a drawer.
The Monki.com homepage at the time of the study — "Party mode: ON", with only a Sign in option in the header.
Monki.com at the time of the study — strong brand, but note the header: Sign in only, no way for a new customer to sign up.

How it was run

4 tasks · 5 participants · 2 platforms · 8 metrics

01

Recruit

5 participants matching Monki's 19–38 target, screened on shopping habits.

02

Pilot twice

Expert + novice pilot runs; expert time ×5 set each task's novice time budget.

03

Moderated sessions

Think-aloud protocol, audio + screen recorded; every task run on both sites.

04

Post-test instruments

SUS, CSAT, NPS, confidence rating and a desirability word-choice exercise.

05

Analysis

Paired t-test on task times; every issue severity-graded and tied to a business risk.

Task given to participantsExpert pilot×5 budget
1 · "Create an account, add a red dress to the cart, check its reviews"60 s5:00
2 · "Find the Black Flowy wide-leg trousers, apply a student discount"93 s7:45
3 · "Find winter boots, then the nearest store to buy them in person"78 s6:30
4 · "Check the fit guide for an overcoat, then find the refund policy"120 s10:00

The four tasks, verbatim, with time budgets derived from the expert pilot (Common Industry Format).

Who was tested

Five real people, recorded in session

5
Recruited participants, every session recorded
3 / 2
Women / men, matching the customer base
22–33
Age range across the panel
80%
Prefer shopping online
PAgeOccupationShopsWhat they expected from the site
P131EmployedOnlineBuy a gift for a friend on a female-oriented site
P223StudentOnlineThe best student discounts
P326EmployedIn-storeAn easy-to-use website
P428EmployedOnlineSomething easy and quick
P529StudentOnlineThe latest fashion trends

The panel — recruited on gender, age and shopping habits; two knew Monki beforehand.

Six screenshots from the moderated sessions — participants mid-task with screen share and webcam visible.
The sessions as they happened — screen + participant webcam, think-aloud throughout.

The data

Monki wasn't slightly behind. It was in a different category.

Every one of eight metrics told the same story.

MonkiPrettyLittleThing
Task completion rate
Monki: 30%
PrettyLittleThing: 95%
SUS — System Usability Scale (global average: 68)
Monki: 41.5 · Poor
PrettyLittleThing: 82.5 · Excellent
CSAT — customer satisfaction
Monki: 30
PrettyLittleThing: 90
NPS — likelihood to recommend
Monki: 20 · detractor territory
PrettyLittleThing: 86
MonkiPrettyLittleThing
Average time per task — lower is better
Monki: 4.68 min
PrettyLittleThing: 2.37 min
Errors per task — lower is better
Monki: 2.1
PrettyLittleThing: 0.2
Assists needed per task — lower is better
Monki: 2.1
PrettyLittleThing: 0.4
TaskP1–P5 on MonkiMonkiPLTWhat participants said
1 · Account + reviewed product✗ ✗ ✓ ✗ ✓40%100%"There should have been a login from Gmail and Facebook." — P1
2 · Product + student discount✗ ✓ ✗ ✓ ✗40%80%"Even after creating an account, it still shows I need to sign up." — P2
3 · Boots + nearest store✗ ✗ ✗ ✓ ✗20%100%"I have never felt so stressed about shopping online." — P1
4 · Fit guide + refund policy✓ ✗ ✗ ✗ ✗20%100%"I expected the store locator on the product page, not the bottom." — P4

Per-participant completion on Monki with a verbatim per task. On PLT, 18 of 20 task runs succeeded.

.003
Paired t-test p-value — significant at 95% confidence
2.30
Effect size (Cohen's d) — a very large, real difference
2:1
Time on task, Monki vs PLT (4.68 vs 2.37 min)
Null hypothesis rejected — the gap is not noise
Paired t-test output — Monki mean 4.68 ± 1.197 vs PLT 2.378 ± 0.728, d = 2.303, p = 0.00347, verdict: Sample 1 mean is greater.
The t-test output as run — d = 2.303, p = 0.00347: participants really were twice as slow on Monki.
Desirability word cloud from the post-test exercise — Confusing, Inconsistent, Difficult, Distracting, Intimidating, Boring dominate.
The words participants chose for Monki in the post-test desirability exercise — for a brand built on playful and friendly.

What testing surfaced

Ten issues. Four critical. All commercial.

Every issue severity-graded, tied to a business risk, and paired with a recommendation the engineering team could scope.

#IssuePriorityRecommendationStatus
01Cluttered homepage layoutHighStandardised image grid, clear hierarchyImplemented
02No sign-up option on homepageHighSeparate Sign up / Sign in CTAsImplemented
03Store locator buried & unusableMediumGeolocation store finder on the product pageRecommended
04Menu contrast — WCAG failureHighHigh-contrast background for all menu statesImplemented
05Reviews missing or read-onlyMediumUniversal reviews with write & photo capabilityImplemented
06Delivery estimate — false informationMediumPostcode-based delivery estimate on product pageRecommended
07Student discount takes 10+ minutesMediumDirect Totum / UNiDAYS / Student Beans integrationRecommended
08No social sign-inHighGoogle / Facebook / Instagram OAuth loginImplemented
09Size guide cm-onlyLowcm / inch converter in the fit guideRecommended
10Out-of-stock items sit in cartLowReserve stock once it's in the cartRecommended

The full issue log — the single source of truth the roadmap and impact figures below refer to.

High · Acquisition

Sign-up hidden inside sign-in

Participants scrolled to the footer, joined the newsletter, and believed they had an account. Cost: every missed new customer.

There should have been a login from Gmail and Facebook — it makes the signup process quicker. — P1

High · Trust

Reviews missing or read-only

Present on some products, absent on others, writable nowhere. Expert pilot: feels like a dropshipping site.

High · Accessibility

Menu contrast — WCAG failure

White type on a pastel gradient across the primary navigation. Legal exposure, not just friction.

High · Brand

Cluttered, inconsistent homepage

Mixed image sizes, uneven placement — cognitive load working against the editorial brand.

Monki category page with inconsistent product-image sizes and placement.
Issue 01 — the cluttered grid participants met on arrival.
The newsletter "Sign up" block in Monki's footer that participants mistook for account creation.
Issue 02 — the only visible “Sign up” on the site was for the newsletter, not an account.
Monki's menu at the time of the study — white text over a yellow-to-pink gradient background.
Issue 04 — the WCAG contrast failure is visible to the naked eye.
Monki's review drawer — a single read-only review, no way to write one.
Issue 05 — where reviews existed at all, nobody could write one.
Evidence for the medium-priority issues — the drag-a-pegman store locator map, the 10-minute student verification screen, and the delivery-information modal with no postcode field.
Issues 03 · 07 · 06 — the pegman store locator that made 60% quit, the 10-minute student verification, and the delivery modal promising a postcode check that didn't exist.
Evidence for the remaining issues — the long create-account form, the cm-only fit guide, and an out-of-stock size selector.
Issues 08 · 09 · 10 — a long manual form with no social sign-in, the cm-only fit guide, and in-cart items that turned out to be out of stock.

Where users expected it — card sort

  • Reviews directly below the product description
  • Store pickup on the product page
  • Delivery estimate before add-to-cart
  • Size guide next to the size selector

Where Monki put it

  • Hidden behind a tab, or absent entirely
  • Bottom of the page, behind a map interaction
  • After checkout
  • A separate page, in cm only

The card sort didn't just list problems — it pointed to a specific reorganisation. I reworked the site map and the core user flows so the surfaces users looked for (a visible login, reviews, a delivery estimate, store pickup) sat where they expected them.

Revised Monki site map — Home and a main navigation of Menu, Product Search, Login, Sign up, Country/region, Favorites and Shopping Bag, branching into product categories, the product page (description, reviews, product delivery, add to shopping bag) and a guest-checkout flow. New iterations — a visible login, reviews, estimated delivery, locate-store pickup and guest checkout — are marked in red.
Revised information architecture — the reorganised site map, with new iterations (login, reviews, estimated delivery, store pickup, guest checkout) called out in red.
Revised Monki user flow across scenarios — from Join Monki and sign up or login, through choosing a category, product description, delivery and add-to-bag, plus reviews and a store-pickup path (enter postcode, locate store, pin location, get directions). New additions are drawn in pink, with scenario notes explaining each change.
Revised user flows — the new task paths (added login, postcode delivery estimate, product reviews and locate-store pickup) against the original flow, annotated with scenarios.

Users arrived at Monki already interested. The site's job was simply not to lose them. It was failing that job in ten specific, measurable, fixable ways.

Research Insight — Nikita Rohan, 2022

What happened next

A sequenced roadmap — and five fixes live

Sequenced by effort, impact and dependency — not a flat list.

High impact · Low effort — Do first

  • Sign up / Sign in separation
  • Navigation contrast (WCAG)
  • Homepage image grid
  • Social sign-in (OAuth)

High impact · High effort — Plan next

  • Universal reviews system
  • IA restructure — product page
  • Student discount integration
  • Postcode delivery estimate

Low impact · Low effort — Quick fills

  • Size guide cm/inch converter
  • Cart stock reservation

Low impact · High effort — Defer

  • Store locator full redesign
  • Click-and-collect infrastructure
5/10

Recommendations implemented by the client

The client moved on the high-priority phase immediately after delivery.

  • Separate Sign up / Sign in CTAs — the highest-failure path in testing, removed.
  • Navigation contrast fixed — WCAG compliance on the most visible surface.
  • Universal reviews with write capability — the trust collapse addressed.
  • Social sign-in (Google / Facebook) — acquisition friction removed.
  • Homepage grid standardised — first-impression cognitive load down.

Looking back

What the research taught me

Benchmark bias

PLT was a flawed comparator

A conversion machine vs a brand experience skews task-efficiency metrics. & Other Stories would have framed it more fairly — the findings hold, the framing sharpens.

Think-aloud effect

The real gap was likely bigger

Think-aloud inflates completion. Monki lost badly even with that tailwind — a floor, not a ceiling, and worth caveating explicitly in the report.

Implementation gap

Delivery isn't the finish line

Five recommendations shipped; five didn't, and I never learned why. Next time the contract includes a post-delivery debrief with product and engineering.

UX → revenue

Put the money in the document

Broken sign-up = lost acquisition; missing reviews = suppressed conversion. I said it in the room — it belongs in writing, where executives decide.