Shared-Primitives Expansion
Expand into adjacent formats by reusing infrastructure that solves the same user needs.
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 96%
Start with the job customers are trying to accomplish, then compare an adjacent product against the platform’s existing primitives. Spotify recognized that music and podcasts both required playback, search, discovery, device ubiquity, and freemium monetization. That overlap made integrating podcasts into the main app more defensible than creating a separate destination. The mechanism is infrastructure leverage: shared capabilities lower the cost of entering the adjacent market while an existing audience reduces distribution friction. The framework also challenges category labels that exaggerate differences between formats. A platform should still examine unique requirements, such as podcast merchandising and moderation, but those differences should be weighed against the shared customer experience rather than treated as automatic reasons to separate products.
Origin
Daniel Ek described how audiobook uploads in Germany and Spotify employees’ podcast habits revealed that multiple audio formats could share the infrastructure originally built for music.
Core principles
- 01Define markets by user needs rather than legacy formats.
- 02Look for adjacent products that share core infrastructure.
- 03Test contrarian integrations against first principles.
- 04Treat existing user behavior as evidence of latent demand.
How to run it
- 1
Observe adjacent behavior
Find cases where customers or suppliers are already using the platform for an unintended but related purpose. Treat repeated workarounds as signals of unmet demand.
Pro tip Study unexpected uploads, searches, and consumption patterns before commissioning abstract market research.
Watch out Do not mistake isolated misuse for a durable customer job.
- 2
Define the underlying job
Describe what the customer is accomplishing without relying on existing category labels. Determine whether the adjacent format serves substantially the same consumption or workflow need.
Pro tip Use first-principles language such as discover, play, search, distribute, or monetize.
Watch out A superficial interface resemblance does not prove that the underlying job is shared.
- 3
Map shared primitives
List the existing capabilities that can support the adjacent product, including discovery, identity, playback, distribution, payments, and monetization.
Pro tip Prioritize capabilities that took years to build and would be expensive for a standalone entrant to reproduce.
Watch out Include new liabilities such as moderation and rights management in the comparison.
- 4
Prototype the integrated experience
Place the new format where existing users can encounter it naturally. Test whether integration removes switching costs and expands adoption beyond category enthusiasts.
Pro tip Dogfood the experience with employees who resemble representative users.
Watch out Do not force integration if the format creates persistent confusion or degrades the core experience.
- 5
Iterate through objections
Separate valid execution concerns from resistance caused by unfamiliarity. Improve format-specific weaknesses while preserving the strategic leverage of shared infrastructure.
Pro tip Track whether objections disappear as users become familiar with the concept.
Watch out Contrarian positioning is not evidence that the strategy is correct.
In the wild
Spotify saw that podcast listeners wanted recommendations, playback across cars and speakers, search, and convenient access without switching applications. Those were capabilities the company had already developed for music, so it added podcasts to the same app despite prevailing enthusiasm for separate applications.
→ Podcasting reached Spotify’s existing mass audience while reusing years of platform investment.
A video-learning service notices customers playing lessons in the background and downloading audio-only workarounds. It maps audio courses to its existing search, recommendations, subscriptions, progress tracking, and creator tools, then adds an integrated listening mode rather than launching an unrelated podcast app.
→ The service adds a new consumption mode with limited new infrastructure and lower customer switching costs.
Common mistakes
Treating labels as customer needs
Assuming that podcasts, audiobooks, and music must be separate because the industries use different labels can hide substantial overlap in the actual customer job.
Ignoring format-specific costs
Shared playback and discovery do not eliminate differences such as content moderation, merchandising, licensing, or monetization.
Copying the market consensus
A separate product may feel safer because competitors use one, but inherited architecture should not replace first-principles analysis.
Is it for you?
Best for
It is best for established platforms whose infrastructure can serve multiple content types or customer jobs.
Not ideal for
It is not ideal when the proposed market has fundamentally different users, economics, workflows, and infrastructure requirements.
From the transcript
“all the Primitives that we built for music should work really well in terms of discoverability in terms of ubiquity that we call which is…”
“it was really a lot more of a first principles kind of thinking around it”
“all of these things were basically shared infrastructure that we could utilize”
From the episode
Spotify CEO Daniel Ek
Daniel Ek