Platform teams that mandated their internal platform were more than twice as likely to say it delivered most or all of its goals: 62.2%, compared with 27.5% for teams that made adoption optional. Over the same year, the share of mandated platforms in our research fell from 63.0% to 45.9%, and optional platforms became the majority.
That puts the data at odds with the most repeated advice in platform engineering. Team Topologies, the CNCF’s Platform Engineering maturity model, and a 2026 review of the platform engineering literature all say a platform should earn adoption through self-service instead of forcing it. Evan Bottcher’s 2018 description, still widely cited, said a platform “cannot stand on a mandate alone.” Going into the 2026 Future of Platform Engineering report, we expected optional adoption to win out. The data pointed the other way.
“An agent never chooses a platform. It works within whatever access someone configures for it…”
Mandates also travel with leadership backing and budget confidence, so the mandate alone probably isn’t what drives results. That distinction matters more now that coding agents open pull requests and, in some organizations, trigger deployments. An agent never chooses a platform. It works within whatever access someone configures for it, which shifts the useful question from whether to mandate the platform to which policies the platform should enforce.
2% say they delivered most or all of the benefits they set out to achieve. 5%.
Source link







