I’ve already explained about the differences between a product and platform in a previous article. I also explained what is software product management. Now I want to talk about the differences between managing a product and a platform.
When we talk about software products, our only concern is with one type of customer. In a single-side platform, besides worrying about understanding one single type of user, it is necessary to understand the relationship between users.
When we talk about a multi-side platform, we should take into consideration two or more different types of users, and the relation between users of the same kind and of different kinds. In other words, the concerns, both from the product manager and from everyone who works in developing the platform, can be more complex than the ones regarding a product with one single kind of user.
A platform strategy must take into account that the customer does not perceive value only from the features of the product, which are 100% under the platform owner’s control. Aside the features, the customer seeks value in interactions with third parties, and it is the platform owner’s responsibility to manage these relations in order to create the best value both for participants of the platform as well as for itself.
Besides all concerns of software product management that I’m describing in my articles, those who manage a platform must also take in consideration other aspects:
The platform features depend on the participation of users. We use the expression tipping for this concern, i.e., how to make the platform attracts and retain users so it can be useful for those who participate in it? Some strategies for tipping are:
There are also the features that depend on users’ behavior. The term used for that is coring, i.e. how to guarantee that they are not taking advantage from each other, ensuring that every participant has benefits? Some strategies for taking care of coring:
It is important to understand if you are working on a product or a platform, because there are some differences in managing each one of them.
A platform needs a strategy for attracting the first users, and this is equally or more important than the features. As software product managers, we tend to get excited with technical features. However, in platforms the focus is concentrated on users, on their relations and on how to attract the first users (tipping). In addition to that, managing a platform requires control and relation governance inside the platform itself in order to guarantee that all participants are benefiting from it (coring).
Once we understand what is software product management and what are the differences between managing a software and managing a platform, what we need now is to understand what is a software product manager. That’s the subject of my next article. Stay tuned!
In 2015 I wrote a book on Software Product Management in Portuguese. In the beginning of 2016, Paulo Caroli talked to me about how he enjoyed the book and how this book could be useful to people in the software industry not only in Brazil but anywhere in the world. For this reason, we decided to create an English version of my book.
The book is organized in 5 sections:
This book is suitable for anyone working with software. Even companies that do not have software as its core business use software in their day to day and often have developed some software that interfaces with its customers such as a website or a mobile application. It is important for these companies to understand the software product management role and responsibilities, so they can better manage this software and increase its chances of success.
We are working on the translation but as we progress we are already releasing the content. If you want to see the work in progress, please visit the book page at LeanPub. Still in beta but already with valuable content. Feedback is always welcome!