Platform engineering is the discipline of designing and building toolchains and workflows that enable self-service capabilities for software engineering organizations in the cloud-native era.

Platform Engineering

*"Reflecting on the question, 'What could go wrong with the Platform Engineering hype?' inspired me, <https://thenewstack.io/8-real-world-reasons-to-adopt-platform-engineering/|Steve Fenton> earlier this year, to undertake independent research into the business and technical motivations behind Platform Engineering. We’re now one step closer to opening this research for public review"*

• *Teams are focussing on too few features for a platform, platforms are more successful with more features in general, though precision in feature selection is more important than “trying to do everything”*
• *The top reason for platform adoption is to “improve efficiency” and cost control is a great practical thing to track to demonstrate progress. A platform that pays for itself is going to have a safe budget over the longer term.*
• *Talking to platform users regularly (at least monthly, but weekly or daily is better) predicts higher success - user-centricity will not only lead to success but will also keep platforms light as they’ll have fewer unused features.*
• *There are common themes around deployment pipelines, but the worst outcome from the research would be people creating carbon copies. Some of the top-rated platforms had just 3 features, yet achieved “all goals” for adoption.*
Meanwhile *I recorded and pushed an episode on #cloudnativefm People, Processes, Power, and Performance with Platform Engineering <https://www.youtube.com/watch?v=fC-TTfW9S0M>*.