At some point, every engineer has the same realization:
“Why am I waiting 3 days for someone to create a database?”
It usually starts small. A ticket here. A Slack message there. Then suddenly half your sprint is blocked on “someone else’s queue.”
And this is where things get interesting…
The Real Problem Wasn’t Technology
We used to think the issue was tooling.
Better CI/CD! More automation! Stronger processes!
But the real bottleneck was us... humans as gatekeepers.
Not because they’re bad at their jobs. But because queues don’t scale.
Enter: Self-Service
Self-service flips the model:
Instead of: “Ask Ops to do the thing” You get: “Do the thing yourself, safely”
Infrastructure, environments, pipelines—available on demand.
No tickets. No waiting. No awkward “just bumping this” messages.
Why It Works (Psychologically)
Here’s the weird part.
Self-service isn’t just about speed — it’s about perception of control.
Think about supermarket self-checkouts.
They’re not always faster. Sometimes they’re objectively worse.
And yet… people prefer them.
Why? Thats a great question...
- You’re in control
- No waiting behind someone who can't find their pocket change
- Progress feels immediate
This taps into:
- Autonomy bias (we prefer doing things ourselves)
- Instant feedback loops
- Reduced social friction
Engineering teams are no different.
Give them a button instead of a queue—and suddenly everything feels faster.
Takeaway
Self-service didn’t win because it’s perfect.
It won because:
- Waiting is painful
- Control feels good
- Autonomy scales better than coordination
