A platform offers self-service provisioning and teams still file tickets. Why, and what would change it?

Why they still file tickets

• The self-service path does not cover their case. It provisions the standard thing, and their requirement differs in one respect — so they use the path that can accommodate anything, which is a human.
• It requires knowledge they do not have. A form asking for values they cannot supply is not self-service; it is a ticket with extra steps.
• It is slower than asking. If provisioning takes twenty minutes of form-filling and a ticket takes two minutes to write, the ticket wins even if it takes a day to be actioned.
• They do not know it exists, which is a discovery problem and is more common than platform teams expect.
• It failed once, and the ticket is now the trusted path.

What would change it

• Sensible defaults for everything that can have one. A request should be answerable with one or two decisions, not twenty. Every field that could have a default and does not is friction that the ticket path does not have.
• Cover the second and third most common cases, not just the first — since the long tail is where the tickets are, and two or three additions usually capture most of it.
• An escape hatch that is part of the platform rather than outside it, so an unusual requirement is a parameter rather than a defection.
• Speed: provisioning that completes in seconds, with the result immediately usable.
• Visibility of what was provisioned and what it costs, so the team owns it afterwards.

The measurement that finds the gap

Ticket volume by category. The categories with the most tickets are the self-service gaps, ranked by demand — which makes the roadmap obvious and evidence-based rather than a matter of opinion.

The underlying principle

Bypass is a product signal, not a compliance failure. Teams file tickets when the ticket is faster, easier or more capable — and the response that works is to fix that rather than to prohibit the ticket.

Removing the ticket path without closing the gap produces neither self-service nor tickets; it produces workarounds nobody can see.