By now, self-service sounds like a silver bullet... It’s not. (It never is.)

The Hidden Costs

1. Platform Complexity

Someone has to build:

• The golden paths
• The automation
• The guardrails

That “simple button”?

It probably hides 5000 lines of YAML.

2. Adoption Is Hard

Engineers won’t use your platform because:

• It exists
• It’s “best practice”
• You said so

They’ll use it if:

• It’s easier than alternatives
• It saves time immediately

Otherwise? ...Shadow tooling. Every time.

3. Over-Abstraction

Too much abstraction and you get:

“I clicked the button and… I have no idea what happened.”

Which is fine—until something breaks.

Then it’s chaos.

4. Cognitive Load Still Exists

Self-service reduces coordination load.

But increases:

• Decision-making
• Responsibility
• Context switching

If not designed well, it just moves the pain.

So What Actually Works?

Good self-service platforms:

• Have opinionated defaults
• Are boringly consistent
• Optimize for common paths, not edge cases
• Treat developers like users, not experts

Takeaway

Self-service is powerful—but fragile.

It works when:

• It’s easier than asking
• Clearer than guessing
• Faster than waiting

Otherwise, people go back to Slack.

And honestly… can you blame them?