Skip to content

iQiyi · 11 min read

Making a membership legible

43.2% of people were leaving on the Membership Selection page. The flow turned out to be fine — what they could not read was what their money bought.

At a glance

Role
Product Designer · UX Researcher & Analyst
Duration
3 months (of a 14-month tenure)
Platforms
iOS · Android · Tablet · Web
Tools
Sketch · Zoom
Team
1 PM · 1 engineer — research and design both on me

Shared with permission. Some figures are shown as relative change.

Challenge

The page people left on

iQiyi brings Asian entertainment to a worldwide audience. In North America that means 6 surfaces — iOS, Android, tablet, responsive web, Roku and Amazon Fire TV — and one standing constraint: hold the company's identity together while each surface still fits its local users.

Checkout data put the exit rate on the Membership Selection page at 43.2% — more than 4 in 10 people reached the page where they choose a plan, and left. Two different groups were stuck there. Prospective subscribers could not connect what a package described to what they would actually get to watch. Existing subscribers were not sure which membership they were already on.

Engineering capacity was tight, which set the terms for everything that followed: whatever I designed had to be reusable to be worth building at all.

Research

Ruling out the obvious suspect

I ran a survey through the newsletter, an in-app and on-site flash notice, and push notifications — 2 weeks of fieldwork, 1 week of analysis, 11,765 responses, 89% from the US and 11% from Canada.

  1. 01The checkout flow itself was easy to follow and smooth to complete. The funnel was not the problem.
  2. 02Users could not identify which membership type they were already on.
  3. 03Users could not tell which programmes their money actually bought.
  4. 04Exclusive content was the leading reason to subscribe, ahead of ad-skipping and discounted price.

“I don't really know what I spent my money on, since I can't recognize which programme is for free and which is VIP only.”

Interview participant
Survey — 11,765 responses
Interview synthesis

Design

Three rules, then the decisions

The survey had ruled out the flow, so the work moved from fixing a funnel to making the service legible. 8 moderated interviews and usability tests — 4 in the US, 4 in Canada, across diverse racial and ethnic backgrounds — told me where the confusion actually sat.

Four how-might-we questions came out of that: help users easily compare membership packages, understand what a privilege means in real practice, feel the value of the membership, and manage their own membership status. Each one became a design track.

Every signifier decision after that followed three rules: simple but comprehensive (never substitute one tag for another — show every VIP marker), helpful (VIP versus free, airing info and titles all present), and standardised across platforms and across drama and variety alike.

  1. Comparing packagesChanged the orientation of the membership display so every privilege sits in one area. Both versions tested well for comparability, but Version 1 did not distinguish membership type at a glance — so Version 2 shipped.
  2. Tagging what's includedThe original showed a single tag and did not prioritise VIP. Type 4 won because users picked up all the useful information in one standardised format.
  3. Skip-ads3 versions tested for skip-ads. The text-led Version 1 won over the more visual Version 3 — in her words from testing: users liked knowing they were privileged, yet did not want an extra interaction to make it happen. The louder treatments were rejected for asking something of people in exchange for a benefit they had already paid for.
  4. Membership SwitchWhen the catalogue felt thin, users thought about cancelling. Cancelling and coming back is expensive in clicks — an average of 8 to cancel across iQiyi, iTunes and Google Play, then 6 more to re-subscribe — so the platform was making its own churn permanent. I proposed a switch system so users could move up or down a tier instead: flexibility, fewer cancellations, and no repurchasing. Concept only, never launched.

Before

Version 1

  • Keeps the existing structure

After

Version 2 — shipped

  • Every privilege reorganised into one area
  • One standardised format, so nothing useful gets missed

Impact

What moved

Against a 43.2% exit rate going in, sign-up rate rose 43% once the flow was rebuilt around what people had told us they were actually buying. The share of higher-value Premium memberships rose 23.6% over 2 months.

The constraint turned out to be the outcome too: because the tag and signifier system had to be reusable to get built, it ended up working across drama and variety, and across every platform — which is what made it the starting point for iQiyi North America's first design system.

The membership display and VIP signifiers shipped in June 2022. Membership Switch stayed a concept.

Across surfaces

Three renderings, one set of rules

The VIP signifiers hold together across the product for the same reason. The phone, the web player and the tablet are not three designs that happen to look similar — they are the same rules rendered three times. Standardised was one of the three rules for a reason: it is what let a 2-person build reach 6 platform surfaces.

Phone
Web
Tablet

Design system

The other half of the job: a design system library

Alongside the membership work, and separate from it, I built and extended iQiyi North America's design system library. The membership components and the VIP signifiers fed into it — that is how they got there — but the library was its own piece of work, with its own output.

I was the only designer on the region, which meant every pattern I shipped either became a rule, or became a one-off that the next person would have to guess at. I chose rules.

The clearest worked example is the global navigation — what “design system” meant in a team of one: one component, specified across 4 breakpoints, 6 page contexts, 5 feature panels, and both signed-out and signed-in, before a single screen was handed over.

4 breakpoints — 1920 / 1024 / 768 / H5
6 page contexts, including scrolled and VIP
5 panels, each signed-out and signed-in
…and the pieces themselves, every state drawn

Reflection

What I'd carry forward

There is always another opportunity in the product, if you stay patient enough with users to hear it.

Personal learning

Validation settles the argument

Not seniority, not taste.

In a design team of one, a test result was the only thing I could put on the table that did not depend on who was asking.

Personal learning

Advocacy was half the job

Building a design-thinking environment mattered as much as the design did.

So did holding business objectives and user needs together under real limits on people and time.

Related work

All case studies