Suran Tierney
I am a product designer driven by curiosity and a lot of questions. I design thoughtful experiences inspired by how people interact with the world.
Email
CV
LinkedIn
Work
  1. Share & Earn
  2. HP x Yoto
  3. Yoto Club
  4. IT Sportswoman
  5. IT National Debate
  6. Type & Order
  7. Platform for Joy
  8. Dreamcatchr

Yoto Club — When Visibility Isn't Enough



Yoto

A screen-free audio player for children

Shipped: March 2025
Role: Product Designer
Team: Seb & Vince (Engineer), Sarah (Product Manager)
Yoto Club is a monthly subscription giving families credits to discover and download audio content — stories, music, podcasts and more — available on card and digitally in the app.
Problem
Users struggled to understand their Club membership, how many credits they had, when they were used, and when they expired. This led to confusion and frequent support queries.

Discovery
I pulled together evidence from three sources, Gorgias support tickets, user interviews, and a hypothesis that the credits banner wasn't clearly communicating how credits worked or when they expired.

The pattern that emerged: users didn't lack access to information, they lacked the context to interpret it.
Constraints
Working within four weeks, I collaborated closely with engineering to understand what data was available and what was feasible to surface in the MVP.

Credit expiry and subscription visibility were the most repeated pain points — forming the hypothesis that the banner wasn't doing enough.
Audible and ClassPass showed how credits and membership could live clearly in one place.
What the API could surface — shaping the MVP.

Solution
The MVP focused on one thing, bringing fragmented information together into three clear areas:

— Credit summary (remaining, expiry, next credit)
— Credit history (usage over time)
— Subscription details (plan and billing visibility)





Outcome
The MVP shipped and improved visibility, but didn't significantly reduce confusion or support queries. In hindsight, exposing more data isn't the same as helping users understand it.

What I'd explore next
Given more time I'd have focused on helping users interpret their credits in context, surfacing what they need to know next, rather than everything at once.

Personal learning
This was my first shipped product feature and it taught me more than any successful project could. I've since become much more focused on defining success upfront and making sure I'm solving the right problem, not just making information visible.

It's the project I think about most when starting something new. What does success actually look like, and am I solving the right problem? :)