Software development is a fast-moving industry needed to support an increasingly digital world – and it’s vital that engineering leaders find innovative ways to keep up. One way organizations are doing this is by adopting Internal Developer Portals (IDPs) – centralized platforms designed to streamline the software development lifecycle. In fact, Gartner predicts that by 2026, 80% of enterprises will have some form of platform engineering initiative, underscoring the growing interest in IDPs. One of the most widely adopted IDPs is Backstage, an open-source IDP framework with 3,000+ adopters and 210+ open-source plugins.
IDPs are in demand because they are capable of controlling the chaos within software development at any scale, enhancing efficiency, improving collaboration and streamlining workflows. They provide developers with the necessary tools, best practices and infrastructure to build, deploy and manage applications effectively. What’s more, by reducing cognitive load and automating routine processes, IDPs enable developers to focus on delivering high-quality software efficiently.
However, despite the potential benefits, widespread adoption of IDPs remains a challenge. Engineering organizations can struggle with adoption due to cultural resistance, lack of perceived value, and misalignment with existing workflows. To change this, leaders must address these barriers head-on.
Why IDP Adoption is so Important
One of the biggest challenges engineering leaders face in achieving success with an IDP is encouraging an adoption rate that delivers benefits across the organization. Engineers often have deeply ingrained workflows and tool preferences. As a result, IDPs may be met with scepticism, particularly if developers see them as an additional layer of complexity rather than a facilitator of efficiency.
If developers view the IDP as a top-down initiative with limited input from engineering teams, adoption can stagnate. Without a sense of ownership, teams may resist integrating the platform into their daily workflows. Developers may also struggle to see how an IDP will directly benefit their work. Without clear and immediate benefits, they may even revert to using existing tools and processes, limiting the platform’s impact.
Successful IDP adoption requires buy-in across multiple levels of an organization, and leadership, platform teams and development teams must all align on its goals and benefits. So how can engineering leaders make their IDP adoption a success?
Three Strategies for Successful IDP Adoption
For those teams considering IDP adoption, there are strategies engineering leaders can consider to overcome common barriers – ones that helped the Spotify team to achieve a 99% adoption rate of its IDP, Backstage, a year after implementation.
1. Adopt phased maturity models
A sudden overhaul of existing processes can create resistance, so it’s essential that IDPs enhance current workflows instead of abruptly replacing them. Considering this, one way to gain momentum is through phased maturity models within IDP adoption. By integrating an IDP in stages – from basic to advanced maturity levels – developers have the chance to become accustomed to its functionality at a pace that matches their own.
Collecting early feedback is another crucial step in a phased approach. Organizations should iterate on the platform based on developer input, making continuous improvements that align with their users’ real needs. This fosters a culture of shared ownership and ensures that the platform remains as relevant and useful as possible.
2. Demonstrate tangible benefits
To encourage adoption, developers must get hands-on and experience the everyday benefits of an IDP. They need to understand how the platform can improve their workflows and reduce friction in their day-to-day tasks – whether it’s automating CI/CD processes, environment provisioning, or incident management.
Training sessions can help demonstrate what’s possible and ensure that developers experience tangible benefits from the start. Similarly, internal champions who advocate for the IDP and its associated efficiency gains can help promote the platform organically and further demonstrate its value—not to mention train and champion other developers.
3. Use a top-down AND bottom-up approach
Successful and aligned IDP adoption requires leadership-level support and developer-level engagement. From the top-down, executives and engineering leaders must articulate the strategic importance of the IDP clearly to their teams. They should communicate its value in improving efficiency, reducing operational burdens, and standardizing workflows – and back it up with the necessary budget.
But bottom-up developer engagement is equally important. To foster the right level of ownership resulting in behavioral change, engineers must feel empowered to contribute enhancements and customizations to the IDP. By establishing feedback loops, IDPs become inseparable from genuine developer needs and can make the difference between a truly valuable tool and an imposed requirement.
Foster a Culture of Continuous Improvement
IDPs are indispensable ecosystems that evolve according to developer and organizational needs. But for their adoption to be a success, leaders must ensure they embody the collaboration, communication and adaptability that sits at the heart of good engineering.
Ultimately, organizations that successfully implement and adopt IDPs will empower their developers, accelerate software delivery and create a more collaborative and efficient development environment—helping to unlock everyone’s full potential.
KubeCon + CloudNativeCon EU 2025 is taking place in London from April 1-4. Register now.