Voluntary Adoption

A platform can achieve high usage in two ways: by being the best available option, or by being the only permitted one. The usage figures look identical and mean entirely different things.

Voluntary adoption is usage by teams with a real alternative. It is simultaneously the outcome the platform wants and the only honest evidence it is producing value — and the two are inseparable, which is what makes mandates so damaging.

Why it matters

A mandate converts an adoption signal into a compliance signal. After it, the platform team cannot distinguish "teams use this because it helps" from "teams use this because they must", and therefore cannot tell whether any of its work is worthwhile. The feedback loop that would have told it what to build is gone, and what arrives instead is complaints — a much worse input, biased toward whoever complains loudest.

Mandates also invert the platform team's incentives: the measure of success becomes compliance reporting rather than developer outcomes, and the platform's quality becomes disconnected from its usage.

Implementation patterns

• Make the paved path genuinely faster than the alternative. If the platform is not quicker than doing it yourself, it will not be chosen, and no policy fixes that.
• A supported escape hatch carrying the operational burden, so deviation is possible, visible, and self-limiting without prohibition.
• Measure the right things: voluntary adoption rate and trend; the proportion of teams that tried it and left, which is a far stronger signal than those who never tried; time from zero to production; support burden per adopting team, which should fall as the platform matures.
• Compare adopters against non-adopters on lead time and change failure rate — the outcome the platform exists to improve, and rarely measured because it requires the comparison.
• Treat deviation as roadmap input, since repeated escape in one direction is a requirement not met.
• Publish SLOs on the platform, because teams depending on it need to know what they are depending on.
• Reserve mandates for genuinely collective properties — ownership metadata, telemetry instrumentation, deployment provenance — where one team's non-compliance harms everyone else, and enforce those through generated defaults rather than through policy wherever possible.

Industry example

The internal developer platform movement, exemplified by Backstage-derived catalogues and templates and by large-scale internal platforms such as Mercado Libre's, is built explicitly on the product framing: the platform has users, users have alternatives, and adoption is the measure.

The consistent published contrast is with mandated platform rollouts, which report high compliance and low satisfaction, minimal usage beyond the mandated minimum, and platform teams unable to explain why their capabilities are not used — because the mandate removed the mechanism that would have told them.

Failure scenarios

• A mandate issued to demonstrate adoption, which permanently removes the signal it was meant to demonstrate.
• A paved road slower than the alternative, which no amount of advocacy rescues.
• Escape forbidden, producing hidden deviation and complaints instead of data.
• Measuring capabilities shipped, which correlates with nothing users care about.
• Not measuring departures, so a platform that people abandon looks the same as one they never tried.
• Under-resourcing a platform that everything depends on — a bottleneck with a mandate, worse than no platform.
• Repeated deprecations, which teach teams that adopting anything new is a liability and suppress adoption of everything shipped afterwards.

Trade-offs

Relying on voluntary adoption means accepting inconsistency, sometimes for years. Some teams will not adopt, some will build their own, and the organisation carries duplication that a mandate would have removed — which is a genuine cost, particularly for security and compliance properties.

It is also slower. Persuading forty teams by being better takes longer than instructing them, and there are situations — a regulatory deadline, a security requirement, a decommissioning date — where the organisation legitimately cannot wait.

The trade is consistency and speed of rollout against the feedback signal and the goodwill that make a platform improve. The workable position is a narrow mandate on genuinely collective properties, delivered through defaults so that compliance is automatic, with everything else earned — because a platform that must be mandated in its entirety is telling you something about itself.

Interview question

"Leadership wants to mandate our platform to hit an adoption target this quarter. Tell me what that would cost us, what you would propose instead, and which specific things you would be willing to mandate anyway."