Operations | Monitoring | ITSM | DevOps | Cloud

When considering or advocating for an Internal Developer Portal (IDP) within your organization, assessing potential impact is an exciting, but sometimes challenging endeavor, especially considering the broad set of use cases IDPs support and the lack of context and visibility before the presence of an IDP. Maybe you understand the inherent value of an IDP, but need to quantify the estimated savings/impact to justify the spend.

Engineering’s gotten really complicated. The rush to “innovate or die” created more code, more tools, and more teams—without a single, unifying way to keep it all healthy and moving. The result? Orphaned services, slow releases, and endless overhead... just to name a few.

The terms engineering excellence and developer experience are often used in ways that make them seem interchangeable. While these concepts do overlap, it’s important to understand that developer experience (DX) is just one subset of engineering excellence, not a one-to-one match. Below, we define engineering excellence, clarify what developer experience entails, and explore how improving developer experience supports—but does not replace—the broader objectives of engineering excellence.