← work04·PM · UX·2025

When MyProtein became a marketplace, someone had to figure it out.

MyProtein was expanding from a single-brand store into a full marketplace. The existing checkout supported one delivery option per order. I took on both PM and UX, defined the scope, designed the flow, validated it with users, and shipped it signed-off for development.

scroll · case study

Client

MyProtein · THG

Year

2025

Discipline

PM · UX

Role

Product management · UX design · User testing

PM + UX

Dual role ownership

Signed off

Greenlit for development

0/5 users

Unanimous approval

Overview

The marketplace expansion meant customers could buy items from multiple vendors in one basket, each with different delivery options, timelines and costs. The existing checkout barely supported one delivery option. The project had no PM. Rather than wait, I took ownership of both PM and UX: wrote the V1 scope, worked with engineering on feasibility, designed and tested the flow, and shipped it in under a month.

Challenge

01

The problem

Support 4+ delivery groups in a single checkout, completely new territory for the existing architecture.

02

The complexity

  • Different delivery options for different vendor groups
  • Order summary with split deliveries and separate pricing
  • Users needing to understand why items were grouped
  • Avoiding overwhelming the user with logistics

03

The gap

No PM assigned. I took on both roles, wrote the V1 scope through 5 iterations, defined EPICs and user stories, and drove the project through Q4 Big Room Planning.

What I did

  1. 01/ 05

    Wrote the V1 scope through 5 iterations to define EPICs, user stories and technical requirements. Got it signed off at Q4 Big Room Planning.

  2. Product requirements and acceptance criteria documentation—translating business needs into technical requirements, user stories, and testable success criteria for engineering handoff.
    Product requirements and acceptance criteria documentation—translating business needs into technical requirements, user stories, and testable success criteria for engineering handoff.
  3. 02/ 05

    Designed the split delivery flow, grouping items by vendor with separate delivery selections per group ("Delivery 1 of 4 (5 items), Delivered by MyProtein").

  4. 03/ 05

    Created Named Day Delivery as a clean list rather than a calendar, specific dates with clear pricing at a glance.

  5. 04/ 05

    Designed the order summary with split delivery pricing, transparency over compactness.

  6. 05/ 05

    Ran usability testing with 5 participants through PlaybookUX before committing engineering investment.

  7. Prototype, testing results and follow-up iteration, research-led validation before engineering investment.
    Prototype, testing results and follow-up iteration, research-led validation before engineering investment.

Outcome

01

Named Day Delivery validated

All 5 participants approved unanimously: "Beautiful UI for Named Day Delivery, this is nice, this is very clear."

02

Split basket needs clearer labelling

All 5 understood why items were split, but the notation needed clearer vendor labels, a scoped iteration identified through testing, before engineering investment.

03

Signed off for development

The V1 scope was officially approved at Q4 Big Room Planning and the project greenlit for engineering.

Services delivered

Product ManagementUX DesignScope DocumentationStakeholder ManagementUsability TestingMobile-First DesignMarketplace UX

More of my work