An internal platform team's tooling is being bypassed by product teams building their own. What is the diagnosis, and what changes?

The diagnosis

Bypass is a product signal, not a compliance failure. Teams route around a platform when the platform is slower, harder or less capable than the alternative for their case. Responding with a mandate treats the symptom and guarantees the underlying gap persists.

The usual specific causes: the platform solves the platform team's problem rather than the product team's · it is slower to adopt than to build directly · it lacks an escape hatch, so a team with one unusual requirement must abandon it entirely · onboarding requires a conversation rather than a command.

What changes when it is treated as a product

• Adoption is the metric, voluntary and measured. A platform with a mandate and no measurement has no feedback loop and will drift further from need.
• Users are interviewed, and the roadmap comes from their friction rather than from the platform team's architectural preferences.
• The paved road is genuinely faster than the alternative. That is the whole mechanism: the compliant path must be the path of least resistance, or compliance depends on enforcement.
• Escape hatches are supported, not forbidden. A team that needs something the platform does not provide should be able to opt out of that piece without abandoning the rest — otherwise every unusual requirement becomes a total defection.
• Backwards compatibility and deprecation are managed like an external API, because internal customers have the same migration costs and less patience.

The funding consequence

Platform teams funded as cost centres optimise for cost; funded as products they optimise for adoption. That difference determines whether the team invests in documentation, onboarding, support and developer experience — all of which look like overhead on a cost centre and like the product on a product team.

The honest limit

Some things must be mandated: security controls, audit requirements, data residency. The distinction is that a mandate should apply to the outcome — every service must have an audit trail — while the platform competes to be the easiest way to achieve it.

Mandating the mechanism rather than the outcome is what produces resentment and workarounds, and it removes the pressure that would have made the platform good.