As product people at SUMSUM, we strive to continuously search for new ways to build the right products efficiently. That is how we stumbled upon Pandora’s story during one of our research sessions.
For those who’ve never heard of Pandora, Pandora is a music streaming service based in the United States. The company was founded in 2000 with a B2B business model, and in 2005, they shifted to a B2C model, where they launched as an internet radio product.
After Pandora went public in 2011, it went on to build products for 70 million monthly users spread across multiple platforms. The company generated half a billion in revenue, and today, it is valued at $7 billion. Surely, this is not unusual. At first glance, you’d think thisis just another vast enterprise. But what if I told you that Pandora accomplished all of this with approximately 40 software engineers? Their secret? They figured out how to build the right things fast by using a prioritization process.
Pandora’s prioritization process was invented by their CTO Tom Conrad when he came on board of the company in 2004. Conrad came up with the process by understanding the company’s limits. That is why he based the process on the following three essential rules:
With those three rules in mind, Tom Conrad went to work and designed a model that allowed the company to create maximum value with limited capacity.
At SUMSUM, we strongly believe in the value of Pandora’s Prioritization Process (PPP). We decided to put the process to the test and use it for one of our products. To make it easier to apply the model, we decided to put it in a matrix and a template, which you can consult in the Miroverse here.
You can use the matrix as a quick overview of the different actions, deliverables, and team compositions for each process step.
Pandora’s Prioritization Process exists of 7 steps:
How to calculate the scope in euro?
A feature that takes one engineer one month to complete is worth €5. If the same feature takes them two months, it’s €10, €15 for three months, and so forth. If you’re going to put two engineers on it, that’s €10, €20, €30, and so on.
How to calculate the engineering capacity?
Decide how many developers you have on the team who are available to work on the ideas. For example, if you have ten developers available, each for €5 per month (ref. step 2), and for three months (ref. step 1), this gives you an engineering capacity of €150.
How to distribute the bills?
E.g. The engineering capacity is €150 and the prioritization team consists of 5 people. Each member then gets €30 (6 bills) to spend on ideas.
Note that all steps should be repeated every 90 days. However, this may vary, depending on the size of the company and the flexibility and skills of the developers. You can shorten the period to two months or even one month. After all, you will see for yourself what is feasible for you. The basic rule is that the period should not exceed three months.
Aside from the matrix, we also created a ready-to-use template. All seven steps are included as well as a pre-filled example.
Since we like to share our insights with other product-minded people, we want to share this matrix and template so that you can try out Pandora’s Prioritization Process as well. You can find the link for the matrix and the template shortly on the Miroverse. Can’t wait? Send us a PM and we will deliver it to you shortly.
We’re very curious how you will use this template and for which products it helps you! So feel free to use it and share your insights.