Building Minimum Viable Products at Spotify

Many companies face the paradox of wanting to build a delightful product without knowing if people actually want the product […]

Many companies face the paradox of wanting to build a delightful product without knowing if people actually want the product until it’s released.

Spotify’s vision was to give people the right music at the right time while incentivizing artists by paying them based on number of shares their music received. A tall order, no doubt, when you consider how hard it is to build out such a platform, let alone make it profitable. Yet Spotify defied the odds and grew from zero to over 1 million paying subscribers in the US — a market foreign to Spotify’s native Swedish team and one already teeming with competitors.

So how did they develop a product that fulfilled their vision without driving them into bankruptcy? They took an iterative approach combining elements from Lean Startup, Agile, and MVP methodologies.

To achieve its current 10 million paying and 24+ million total user base, Spotify set out a basic roadmap of prototyping early and cheaply, launching only when a baseline of quality was met, and then iterating based on user feedback. In this piece, I’ll explain the goals of each stage and how they all contributed to a sustainable product development cycle.

Lean & Agile at Spotify

According to Henrik Kniberg, Agile and Lean Startup consultant and author, Spotify uses a 4-stage iterative product cycle (Think It, Build It, Ship It, Tweak It) that emphasizes small teams (referred to as ‘squads’) completing small batches of work while producing a complete product. Let’s take a look at the goals of each stage:

Think It — Decide what product to build, then build prototypes and test viability internally.

Build It — Create a physical MVP ready for user testing.

Ship It — Gradually release the MVP to all users while collecting data and improving.

Tweak It — Iterate continuously based on feedback until product is shut down or revamped (returning us to Think It).

Principles of Lean

Lean Startup uses a “Build-Measure-Learn” cycle to reduce waste while achieving quality, speed, and customer alignment. At the heart of Lean Startup is the MVP, a quickly and cheaply produced quality product for learning purposes. Therefore, Lean Startup eliminates the idea that a team can build what it “knows” it will need in the future.

To that degree, each one of Spotify’s four stages are Lean since small teams are always working smartly to test assumptions. The “Think It” stage tests the merit of conceptual MVPs while the “Build It” stage releases a physical MVP only after it’s been tested for quality. The “Ship It” and “Tweak It” phases ensure long-term quality and customer alignment by releasing the MVP gradually, learning from feedback, and iterating tirelessly. Spotify does deviate slightly from Lean, however, since the “Think It” stage only tests prototypes internally — Lean emphasizes customer testing as often as possible.

Principles of Agile

Lean thinking is necessary in order to develop the mentality needed for Agile practices.

While Lean is used to efficiently define and build a marketable product, Agile is the means to accomplish this in software development.

Team members from all disciplines collaborate on short bursts of work (sprints lasting 1-4 weeks), and in doing so, react better to requirements changes. The Spotify strategy stresses this collaboration by preserving the same product team throughout all four stages. These sprints are especially important for keeping resources in check during the “Build It”, “Ship It”, and “Tweak It” phases when all the heavy lifting is done. All the testing and validating in each phase also keeps Spotify on the Lean path even if product requirements must be changed to reflect customer and market needs.

I. Think It

Before committing resources to a project, companies need to evaluate the viability of the idea. The “Think It” stage consists of small teams asking themselves “Why?” rather than just “How?” At Spotify, this phase is the conceptual stage of the MVP since viability is assessed and minimalist solutions like landing pages and prototypes are used to test user demand.

If, however, management verifies an idea is viable, a small “Think It” team consisting of a developer, designer, and product manager is formed. At this point, the team works on creating a product definition document so that a usable prototype can be built. Using the document, they’ll seek to answer questions such as:

Who will benefit from this and how?

What are the key metrics that we expect this product to improve? (e.g. songs streamed, number of downloads, etc.)

What are the hypotheses?

How will we know if this product is successful?

Is this a “step change” (a product yielding at least a 2x improvement on the chosen metric)? If only minor metrics improvements are expected, another strong strategic reason should exist.

The goal here isn’t to outline features or technical requirements but to create a data-focused value proposition. The heart of the product definition is narrative. And the story told by product is what the first iteration of the MVP will test.

Matchist.com cofounder, Stella Fayman, aptly states the goal of an MVP is to prove that people will use your product. Landing pages and paid ads are a great low-cost way to gauge interest because you test the basic value proposition first (or narrative, in the case of Spotify) before sinking money into anything. This is precisely what Spotify does. When developing its Mobile Free Radio (one version being “Radio you can save”), Spotify ran a Google Adwords campaign to test narratives. In doing so, Spotify exemplifies applying minimalism towards an MVP.

Once the messaging is finalized through testing, the Think It team builds low-fidelity paper prototypes and high-fidelity runnable prototypes (with fake data). Internal user testing provides feedback on which prototypes best convey the narrative until the list is narrowed down to just a few contenders.

David Aycan, Design Director at the esteemed design and consultancy firm IDEO, explains that multiple prototyping avoids tunnel vision. Ideating on different user experiences puts your eggs in different baskets (preventing over-attachment) and finds the best solution through real data instead of trying to predict what users want. Testing multiple prototypes lets Spotify find the most viable MVP by focusing on breadth rather than depth.

In UXPin, we can turn wireframes into prototypes rather quickly in our web app. We take a similar iterative approach to Spotify by starting out with several lightweight, even low-fidelity, prototypes and narrowing down the options from there. However, we like to involve a small subset of friends and customers in the prototype testing (unlike Spotify which just keeps it internal) since they help us “think outside the building.” Ultimately this keeps our team centered on a good customer solution instead of just a technical marvel.

Spotify, on the other hand, will only move forward if it can match the right prototype to the narrative. Because it only involves prototyping and experimenting, the Think It stage is the essence of MVP thinking — the team fails quickly and cheaply, and keeps learning until they find the exact product to build.

II. Build It

Now that a product is decided, the team moves beyond testing concepts to creating a physical MVP that is good enough to release to external users and test assumptions.

The right balance of minimalism and quality must be struck with the physical MVP. Building a feature-complete product requires too much time and money, but rushing a feature-poor product out the door would embarrass Spotify and yield no useful learnings. As such, the team must create the smallest possible thing of quality that still fulfills the narrative and delights users.

Deep — Great products have just the right level of functionality and don’t become useless after just a few weeks.

Intelligent — Great products map specific solutions to pain points (and make customers aware of problems they didn’t even know they had).

Complete — Great products are completely usable, even in early stages.

Empowering — Great products incite users to action and encourages them to spread the news to help others.

Elegant — Great products have intuitive user interfaces and work the way people think they should.

You’ll see in the above diagram that the key question Spotify’s product and management team asks is “Is the MVP good enough for real users?” By making its MVP narrative-complete and not feature-complete, Spotify is able to inherently satisfy all five qualities for a desirable and usable MVP. Perhaps, a better term for Spotify’s MVP would be MLP (Minimum Loveable Product).

The Cupcake Model, which was first coined by Brandon Schauer, CEO of Adaptive Path, emphasizes desirability and completeness regardless of iteration. The analogy states that instead of starting with an uninteresting cake and then adding filling and icing, you start with a cupcake and iterate it into a cake. That way, you invest less resources and the MVP is desirable — people will pay for a cupcake because it’s complete with filling and icing. On the other hand, a dry cake requires more resources to create and is unlikely to be good enough for real users. By following a Cupcake Model, Spotify more importantly avoids misleading conclusions: “Well, we baked a plain cake and nobody wanted it, so the cake failed and we shouldn’t bother adding frosting or filling.”

Source: The cake model of product planning.

III. Ship It

The purpose of the Ship It stage is to gradually roll out the product to all users while measuring and ensuring that the product fulfills its promise in the real market.

Spotify starts by releasing to a small percentage of all users (usually 1-5%) to collect early feedback. During this stage, the hypotheses that were internally tested during the Think It stage are now externally validated.

As you’ll see in the above illustration, the beauty of this stage is that Spotify doesn’t need to get it right on the first try. Collecting data, iterating the MVP, and then A/B testing the changes allows for continuous rounds of maximized learning at minimized cost. Releasing an MVP early and to a small user base allows Spotify to iterate until it becomes an EVP (Exceptional Viable Product) that is ready for all users.

When management and the product team agree that the product is having the intended impact on the small user group (based on the product definition), Spotify will gradually roll it out to all users, while still measuring and improving.

IV. Tweak it

At Spotify, this stage is the longest, and perhaps most important. Unless products get scrapped during the previous MVP stages, they spend most of their life in this completely iterative phase.

While they may have proven themselves to a certain extent in the Ship It stage, Spotify’s products are never considered feature-complete. The team continues the Ship It process of gathering customer feedback, experimenting, and A/B testing to improve the product, resulting in either major rework or just minor tweaks. But, at some point soon, they may reach a point of diminishing returns when the cost versus benefits of new features just looks less and less attractive.

As demonstrated in this article on value vs. complexity, this is an important crossroad where feature prioritization is required. While Spotify believes that no product is truly complete, it also understands the danger of feature creep. Once a product hits its “local maximum” where small tweaks won’t really improve things, Spotify’s product team and management evaluates if being at the top of the hill is sufficient, or if a higher peak is in sight. If the effort isn’t worth the time, the team will move on to other products. Otherwise, the product returns to the “Think It” stage so it can be reworked and leap to the next peak of quality. Spotify’s Tweak It stage ensures that it does not fall victim to the idea that first to market will always stay king of the hill.

As you’ve seen, Spotify’s 4-stage product cycle helps them carefully find the right product early and build it quickly and sufficiently. The length of each stage may differ, but the constant balance between minimizing resources and maximizing product quality is consistent. Ultimately, it leads to a lower cost, lower risk, higher quality product.

We hope Spotify’s strategy has helped you better understand the roles that Lean, Agile, and MVP thinking play towards streamlining your own product development. Don’t be afraid to fail fast and quickly — as long as you keep testing, your most profitable idea might just come from what you learn.