Hey there. Here is part I of the top takeaways from Chapter 26 of “Platform Strategy” by Gregor Hohpe. If you find the content compelling, please consider purchasing the book either from Gregor’s Architect Elevator website, or from a distributor.
1. Increasing the functional scope isn’t the only dimension in which a platform grows. One of the more popular models is a 3D cube with a) dimensions across market reach, b) feature breadth, and c) feature depth.
2. Market Reach - Successful platforms (both economically and technically) require broad adoption. Building a platform without growing itse user bae can lead to a platform that’s perfect for the platform team but not its users. Growing a platform’s TAM usually happens by it being adopted by new use groups, new geographies, or new lines of business. Platform teams should be aware that a platform expansion may impact its current org design structure, i.e. new product management to gain insights into a new user segment, or more support personnel that’s can accommodate platform users in a given timezone.
3. Platform Breadth - Market reach can grow only if it offers the features needed or desired by new user groups. The breadth is defined by the feature completeness of the available problem space the platform is addressing. A “broader” platform increases its value proposition but it also comes along with additional maintenance and support costs. Further, growing breadth too fast may distract from other aspects of platform evolution such as quality and cohesion.
4. Platform Depth - defined by the completeness, quality, and sophistication of the elements covered within the platform’s breadth. As such, a “deep” platform can offer a superior user experience by offering ready-made templates for common project types which can be set up at the push of a button, or a single API call. A “deep” platform can be perceived as “well thought out” or “smooth” by users as they experience well rounded features with tight integration.
5. The risk for platform teams comes from balancing their roadmap from too many diverse customer requests, or only adding platform depth in areas that serve a very narrow subset of customers.
#platformengineering #developerexperience
