Platform engineering is evolving faster than many teams realize - and the data is challenging some long-held assumptions. New research from Octopus Deploy surveyed 379 platform engineers, developers, and sponsors to uncover what actually separates high-performing platforms from the rest. The findings on adoption strategies, feedback loops, and platform scope offer a data-driven roadmap you can act on today.

Main insights

• Platform breadth has exploded from an average of 4 capabilities to 23 in just 18 months, signaling that platform engineering is absorbing responsibilities across the entire organization
• Mandatory adoption correlates with higher-performing platforms - contrary to the common belief that optional adoption is the mark of a mature platform
• Measuring developer satisfaction and using structured feedback channels like pull requests and code reviews are strong predictors of platform success
• Platform maturity and leadership engagement are critical force multipliers, especially as teams integrate AI capabilities

Charlotte Fleming, a researcher at Octopus Deploy, recently published The Future of Platform Engineering report based on a comprehensive survey conducted from October 2024 to February 2025. The study examined platform adoption, capabilities, obstacles, collaboration patterns, well-being, leadership engagement, and AI integration across 379 respondents.

You can watch the full discussion here if you missed it.

Platform scope is expanding at an unprecedented rate

One of the most striking findings is the dramatic expansion in platform breadth. In the previous report, the most common number of capabilities platform teams owned was four. In 2025, that number jumped to 23.

"It's astounding," Charlotte explains. "This expansion tells you how platforms are absorbing responsibilities. It's not been gradual at all. Platforms are just absorbing all of these responsibilities."

What started as a discipline focused primarily on developer experience and productivity has evolved into a central enabler across the organization. Platform teams now serve application developers, AI teams, data teams, and increasingly, business users. Automation has become the top adoption driver - replacing the previous leaders of improving efficiencies and standardizing processes - reflecting both the growing complexity of modern software delivery and the influence of AI on platform priorities.

High performers share distinct characteristics

The research defined high-performing platforms as those achieving most or all of their expected goals - a self-reported measure that captures whether organizations are realizing the value they intended from their platform investments.

Platform maturity matters more than you think

Platforms operating for three years or longer are 2.4 times more likely to achieve their goals. This aligns with DORA's J-curve research, which shows that any discipline improves meaningfully with time and experience.

"The changes associated with legacy migrations, integration work, developers adjusting their workflows - that can take a really long time," Charlotte notes. "When platforms reach that three-year mark, they're more likely to get funded, which is obviously very important in keeping platform engineering within an organization."

Maturity isn't just about technical refinement. Established platforms benefit from organizational learning, stronger stakeholder relationships, and proven track records that make securing ongoing investment significantly easier.

Developer satisfaction measurement is non-negotiable

High-performing teams consistently measure developer satisfaction - yet one-third of all platform teams still don't measure it at all. That gap represents a significant missed opportunity.

"You can't see a gap between what you think you've done and what developers are actually experiencing unless you assess it," Charlotte emphasizes. "Measuring developer satisfaction has actually increased since our last report, which means the industry is moving in the right direction."

You don't need a complex framework to start. Simple surveys asking what's working and what needs improvement, supplemented by regular conversations with platform users, can establish the consistent feedback loop that informs platform evolution.

Feedback channels matter more than feedback speed

Many teams assume faster feedback is always better. The research tells a more nuanced story. A weekly feedback cadence was optimal for high-performing teams - but the channel through which feedback flows proved even more important than the cadence.

Teams that embedded feedback directly into developer workflows through pull requests and code reviews significantly outperformed those relying on ad-hoc channels.

"We had an option that was Slack channels and it rated very poorly," Charlotte explains. "It was one of the most popular, but it was the least effective."

This finding challenges the "Slack ops" pattern common in many organizations, where platform support and feedback happen through unstructured messaging. Structured, in-system feedback creates better documentation, clearer context, and more actionable insights for platform teams.

The mandatory adoption paradox

Perhaps the most provocative finding challenges conventional wisdom directly. The research found that mandatory adoption correlates with higher-performing platforms - contradicting the widely held belief that optional adoption signals platform maturity.

"Mandating platforms brings in users," Charlotte explains. "It enforces developers to use the product rather than competing with old workflows. When you have users coming in to use the product, you can justify budget. The platform gets resourced where it matters."

Mandatory adoption correlates with budget confidence and positive leadership perception, creating a reinforcing cycle: leadership support enables mandates, mandates drive adoption, adoption justifies investment, and investment enables platform improvement.

That said, this finding requires careful interpretation. Charlotte acknowledges the limitation directly: "Our survey can't tell if optional or mandatory came first and therefore can't tell which one drove success."

The practical implication is that you shouldn't fear using mandates as a strategic tool when appropriate. If your platform demonstrably improves developer satisfaction, velocity, security, and compliance - but adoption remains low due to inertia or competing workflows - a mandate can accelerate value realization. The key is ensuring your platform genuinely delivers value before mandating its use.

AI and platform engineering: Complementary, not competing

The research confirms that platform engineering and AI enablement are not competing priorities - they are deeply complementary capabilities. Platform engineers are among the heaviest adopters of AI tools, and platforms provide the essential foundations that make AI successful at scale.

"AI accelerates everything," Charlotte notes. "It needs the automation foundations. It needs the guardrails to work safely, and that's what platforms provide. Platforms are the place for guardrails and compliance checks and standardization, which is what AI needs."

This relationship explains much of the capability expansion. As organizations invest in AI, they need platforms that provide secure data access, policy enforcement, compliance verification, and standardized workflows - exactly what platform teams excel at delivering. Critically, the research found that platform maturity shapes whether AI investment actually pays off. Organizations with mature platforms are better positioned to realize value from AI because the infrastructure, governance, and operational patterns are already in place.

Building for the future: Practical guidance

Leverage underlying tools rather than building from scratch. High-performing teams are more likely to use existing tools rather than rebuilding every capability. This lets platform teams focus their limited build capacity on solving unique organizational problems rather than recreating solutions that already exist.

"Platforms should save their build time focusing on problems that need to be solved rather than building something that an underlying tool has already solved," Charlotte advises.

Make policies mandatory, but keep platforms optional when they work. The research suggests a nuanced approach: enforce policies around security, compliance, and governance, but allow developers to choose platform capabilities when those capabilities genuinely add value. This approach balances organizational standards with the product-thinking mindset that makes platforms successful. When your platform solves real problems effectively, adoption becomes natural rather than forced.

Invest in measurement and feedback infrastructure. Given the strong correlation between developer satisfaction measurement and platform success, building robust feedback mechanisms is essential. Prioritize structured feedback through pull requests and code reviews over ad-hoc communication - and build that feedback directly into developer workflows rather than relying on separate channels.

​

If you enjoyed this, find more great insights and events from our Platform Engineering Community.

If you want to dive deeper, explore our instructor-led Platform Engineering Certified Leader course and connect with peers from large-scale enterprises who are driving cultural transformation.

​

Key takeaways

• Platform scope is expanding rapidly: The jump from 4 to 23 average capabilities in 18 months reflects how platform engineering is becoming central to organizational success across development, AI, security, and business enablement. This expansion requires deliberate prioritization and investment in the right tools and practices.
• Measurement drives improvement: High-performing platforms consistently measure developer satisfaction and use structured feedback channels. Start with simple surveys and regular user conversations, then embed feedback directly into developer workflows through pull requests and code reviews rather than relying on ad-hoc messaging.
• Maturity and leadership support are force multipliers: Platforms operating for three years or longer are 2.4 times more likely to succeed, and that success is closely tied to leadership engagement and funding confidence. Invest in building stakeholder relationships and demonstrating value early to secure the long-term support your platform needs.
• Strategic mandates can accelerate value realization: While optional adoption is often viewed as a maturity indicator, the data shows mandatory adoption correlates with higher performance when platforms genuinely deliver value. Use mandates thoughtfully to overcome inertia and competing workflows - but only after ensuring your platform solves real problems effectively.