Building Internal Developer Platforms that Engineers Actually Use
How to design an IDP that reduces cognitive load without adding another tool to ignore.
Internal Developer Platforms were supposed to be the cure for engineering fragmentation. Instead, most organizations end up with another portal that developers ignore, another Backstage instance with broken plugins, and another ticket explaining why the golden path isn't golden. The problem is rarely technical — it's about design philosophy.
Why Most IDPs Fail
The failure mode is predictable: leadership mandates a platform, a small team builds it in isolation, and engineers are told to adopt it. The result is a tool shaped by platform team assumptions rather than actual developer workflows. Features accumulate, the UI grows complex, and adoption plateaus. The IDP becomes shadow IT — tolerated but not trusted.
The Golden Path Principle
A golden path isn't a feature list — it's a curated, opinionated route through your infrastructure. The goal is to make the right way the easy way. This means resisting the urge to support every edge case from day one. The best IDPs start with the most common workflow and make it exceptional, then expand. Fewer options, better decisions.
Self-Service Without Complexity
- Design for the p95 developer, not the p1 power user
- Expose infrastructure as an API, hide implementation details
- Automate the boring parts: environments, secrets, pipelines, permissions
- Measure time-to-first-deployment, not feature count
Measuring Adoption
You can't improve what you don't measure. The metrics that matter for IDPs are: time-to-first-deployment for new engineers, percentage of services using the golden path, time spent on platform support tickets, and DORA metrics across teams. Adoption is a lagging indicator — the leading indicator is whether developers choose the platform voluntarily.
The best IDPs we've built share one trait: the platform team treats developers as customers. That means user research, feedback loops, and the willingness to delete features that aren't used. Culture first, platform second. The technology follows.
Build intelligent systems with confidence.
Let's engineer the future together. No forms, no friction — just a direct conversation about what you're building.