Why your developers hate your internal tooling (and how to fix it)

Why Your Developers Hate Your Internal Tooling (And How to Fix It) Your platform team built a beautiful internal developer platform (IDP). Then you launched it. Now your Slack is full of complaints, PRs are stalling on infrastructure requests, and your best engineers are writing one-off scripts to bypass your "standard" tooling. This isn't a tools problem. It's a friction problem . The Hidden Cost of Friction Every extra step between "I need infrastructure" and "infrastructure exists" is a decision point where developers choose to work around you. A 15-minute CLI workflow that requires three Slack approvals? Your team will Docker their way to production instead. A self-service portal that requires knowing Terraform internals? They'll ask Ops, who'll ask Platform, who'll ask you. The math is brutal: one hour of developer time costs more than the cognitive load of simplifying your IDP by 90%. What "Self-Service" Actually Means Self-service isn't just removing gatekeepers. It's removing d