Mandatory platforms deliver results, but teams are abandoning them for optional adoption

When organizations forced teams to adopt their internal platforms, those platforms succeeded at nearly twice the rate of their voluntary counterparts. Among teams with mandatory adoption, 62.2% reported delivering most or all of their intended goals, while only 27.5% of teams with optional adoption said the same. Yet this data contradicts a striking industry trend: the share of mandated platforms fell from 63.0% to 45.9% over the past year, while optional platforms now represent the majority at 54.1%.

The contradiction runs deeper than adoption strategy alone. Influential voices in platform engineering—including Team Topologies, the Cloud Native Computing Foundation's Platform Engineering maturity model, and a 2026 review of the field's literature—all advocate for platforms that earn adoption through self-service rather than compulsion. Evan Bottcher's widely cited 2018 definition stated that a platform "cannot stand on a mandate alone." Researchers expected optional adoption to dominate the data. Instead, the numbers pointed elsewhere.

The emergence of AI coding agents complicates the mandate question further. "An agent never chooses a platform. It works within whatever access someone configures for it…" This shift moves the critical question away from whether to mandate adoption and toward which policies the platform should enforce. Agents will follow whatever routes the system makes available, making standardization and policy enforcement increasingly central to platform design.

What travels alongside mandatory adoption

Mandatory adoption does not succeed in isolation. Network analysis of survey responses revealed that mandatory adoption clusters with stronger leadership direction, higher job satisfaction among platform teams, and greater confidence in budget security. These factors correlate with one another and with goal delivery. The simplest explanation is leadership support: executives who genuinely back a platform are the ones who mandate it, and that same support typically secures funding.

AI adoption sits in a similar cluster. Respondents reporting the strongest positive impact from AI also reported stronger budget confidence, clearer leadership direction, and higher job satisfaction. AI's impact was also associated with mandatory adoption, though less strongly. Because this data is cross-sectional, causality cannot be established. Regardless, the implication remains consistent: without leadership engagement and the budget commitment that usually accompanies it, a mandate is unlikely to produce comparable results.

Where mandatory adoption delivers value

Mandatory platforms reported considerably higher confidence in budget renewal: 78.9% compared with 50.0% for optional platforms. When examining adoption strategy, budget confidence, and goal delivery together, budget confidence matters more for optional platforms than for mandatory ones.

For optional platforms, moving from low to high confidence in budget renewal produces a dramatic shift in goal delivery, lifting from 9.5% to 52.4%. For mandatory platforms, budget confidence shifts similarly but less dramatically, from 37.5% to 70.0%. This reveals a practical insight: mandating platforms makes performance less dependent on budget safety. An optional platform's success is tightly bound to funding security; a mandatory platform holds up more consistently regardless. For platform leaders with limited advocacy capacity, this matters: mandatory platforms appear most effective when funding is uncertain, and less critical once the budget is secure.

Mandatory adoption also helps standardize processes and reduce decision fatigue and tool sprawl. Rather than leaving every team to solve security, compliance, and governance independently, the platform can handle these concerns. This becomes more important as agents take on more delivery work. Where a developer might consider deviating from standard processes, an agent will follow whatever routes the system makes available, making standardization a safety mechanism.

The limits of mandate alone

Mandatory adoption carries risks that a mandate alone cannot resolve. Less reliable documentation tracks more closely with mandatory adoption than with optional adoption. When developers have no choice, getting the basics right becomes a lower priority, since the mandate already addresses the problems that would normally drive users away.

Mandatory platform adoption showed only weak association with higher overall job satisfaction. More tellingly, mandatory platforms were no more likely to track developer satisfaction. Under mandatory adoption, this gap matters because adoption numbers no longer signal whether the platform is working.

A more measured approach would mandate the policies—security, cost control, the standards a business actually requires—while making platform adoption itself optional. A platform that becomes the path of least resistance for meeting those policies will win adoption on its own merits. Done well, this approach retains the benefits of mandatory adoption, including scale and standardization, while preserving the signal from developers choosing the platform. A useful test of any platform is whether developers would still choose it if they were not required to.

This distinction grows more important as agents take on more delivery work. Documented policies and manual reviews only work when people engage with them. Agents need the same policies, but those policies must be built into the delivery process itself, making the platform that enforces them the most practical option for both developers and agents.

"The strongest platforms probably need both: a reason people have to use them, and a reason they would want to." Bottcher's 2018 observation holds true: forcing people onto a platform is insufficient. Yet the data suggests that relying on people to choose the platform may also fall short. For agents, which do not choose at all, the platform itself must build in the safe path.