Spotify: Fresh discovery. A familiar place.
A recurring collection can offer novelty without making the interface unfamiliar. Explore the boundary between refresh and saved value.
See the idea in one picture ↓- refresh
- Weekly
- a familiar format
- Playlist
- launch account
- 2015
Figures as reported by the company.
Independent educational analysis. Scenarios, people, numbers and illustrations on this page are original PMcademy practice material, not company research results or an endorsement.
Novelty asks for attention every time.
Novelty that takes effort to find
New things in a place you already know
Read the analysis
Imagine a learner who wants useful new reading but has little time to explore a large library. A changing collection can reduce search effort, yet too much unpredictability makes it hard to form a routine. The opportunity is to put changing content inside a recognisable container with an understandable rhythm.
A return needs a reason beyond a reminder.
Just tell me what is new, and let me keep what I like.
What would help?
Something fresh each week. And an easy way to save.
What gets in the way?
Relearning the interface. Fear of losing a find.
Fictional personRead the analysis
Our fictional listener, Omar, opens a collection during a weekly commute. He does not need to relearn controls each time. He does need to understand what is new, what will change later, and how to keep something he likes. A reminder alone cannot create that value. The recurring experience needs a clear job in the person’s life.
Fresh discovery in a familiar place
- 1Start from listening
What someone already plays points to tracks that are new to them.
- 2A familiar format
The finds arrive as a playlist, something people already know how to use.
- 3A weekly ritual
It refreshes on the same day each week, so there is a reason to come back.
Animated illustration. Names, numbers and people are fictional teaching material.
Refresh the collection, preserve saved value.
Illustrative data and simplified behaviour. This model does not represent a live company system or measured company results.
Read the analysis
Switch between week one, week two and a saved item. The container remains familiar while its contents change. Saving creates a different state from merely encountering a recommendation. This model does not use Spotify data or play music. It helps you inspect the promise made when a temporary collection contains something a person wants to keep.
A rhythm can become pressure.
Read the analysis
A regular refresh may support anticipation, but it can also create anxiety about missing content. Give people an understandable way to save, revisit or decline. Do not imply that every item must be consumed before the next refresh. Consider accessibility and variable schedules: useful recurring value should not depend on a perfect weekly routine.
Separate exposure, discovery and lasting value.
Spotify reflects on a personalised playlist delivered in a familiar format with a recurring refresh.
Which part, the format or the schedule, drove return visits.
- Week-on-week return
- Saves per refresh
- Skips in the first minute
Read the analysis
In your project, distinguish opening the collection, trying an item, saving it, and returning to something saved. A high open rate might reflect curiosity without usefulness. Inspect skips and feedback alongside deeper actions. Define the evaluation period before declaring that a weekly feature formed a habit, and avoid claiming retention lift from a simple before-and-after comparison.
What should happen to a useful find?
Your fictional reading collection refreshes tomorrow. A learner wants to retain one article. You can provide a clear save action, silently overwrite the collection, or make saving require an unrelated social post. Choose a flow that preserves the learner’s agency and the value already discovered. Explain what feedback confirms the action and where the saved item lives.
Choose a next move
Design the next two visits.
Your artifact
Design a two-visit journey with refresh, save, retrieval and missed-week recovery states.
Critique my project artifact using only the evidence I provide. Design a two-visit journey with refresh, save, retrieval and missed-week recovery states. Separate observed facts, assumptions, proposed tests and missing evidence. Identify a failure mode and a cheap check. Do not invent company results or user research. Ask for my artifact before starting.
Read the analysis
Sketch the first collection, the next refresh, and the saved-item view. Name the recurring job, the refresh rule, and the preservation rule. Add a way to recover after a missed week. Your experiment should measure useful discovery and return to value, not just notification opens.