Barriers to Adoption of Platform Engineering.

The adoption of Platform Engineering as a core company concept can be hindered by various financial and organizational factors. After introducing ourselves to the world of Platform Engineering, diving into its 4 core elements, and analyzing its benefits and when you should adopt it, we are now moving to the next level.

In this post, we explore the barriers and mistakes that can arise when adopting Platform Engineering. Addressing them proactively is key to achieving a successful implementation.

Main Barriers to the Adoption of Platform Engineering

1 Lack of a Clear Understanding of What IDP Is and How the Platform Should Work

Fear or Concern

There is often uncertainty about what exactly an Internal Development Platform (IDP) should include and how it should be structured. Managers may fear that without a strict definition or blueprint, they might "create something wrong," leading to wasted resources or a platform that doesn’t meet the needs of the organization.

Reality

There is no one-size-fits-all standard for an IDP because each platform should be tailored to the unique stack, workflows, and objectives of the organization. The flexibility of Platform Engineering allows the IDP to evolve in response to specific team needs and company requirements.

As long as the platform is designed to address the challenges and goals of your organization, it cannot be "wrong." Instead, it becomes a custom solution that aligns with your team's way of working.

Platform Engineering Approach

Adopting a product mindset is key to overcoming this uncertainty. This approach focuses on starting with a Thinnest Viable Platform (TVP)—a streamlined version of the platform that addresses the most critical needs of your organization.

By iterating on this TVP based on continuous feedback from users, the platform can grow and evolve in a way that directly supports your company's goals and workflows.

This iterative process ensures that the platform remains relevant, effective, and perfectly suited to your organization’s evolving needs, mitigating the fear of "getting it wrong."

2 Fear of Having to Cut Staff

Fear or Concern

The development of an Internal Development Platform (IDP) can sometimes be met with resistance, particularly from employees in roles such as DevOps, who fear that the automation and streamlining of processes might render their positions redundant.

This concern can slow down the adoption of Platform Engineering, as teams may be reluctant to embrace changes that they perceive as a threat to their job security.

Reality

Platform Engineering does not aim to reduce staff but rather to shift their focus toward more strategic and impactful tasks. Instead of handling routine, manual operations, employees can now concentrate on higher-level responsibilities such as optimizing platform performance, enhancing security, and driving innovation.

The introduction of an IDP actually creates opportunities for employees to develop new skills and take on more complex, rewarding roles within the organization.

Platform Engineering Approach

A successful Platform Engineering strategy involves forming a unified platform team that collaborates closely with development, security, and operations teams. This collaboration ensures that all teams work together towards common goals, leveraging their expertise to build and maintain the platform.

The platform team doesn't replace existing roles; instead, it enhances them by providing a robust foundation that allows other teams to focus on their core competencies. By promoting cross-functional collaboration and continuous learning, Platform Engineering transforms potential resistance into an opportunity for growth and professional development.

3 The Need to Restructure Processes

Fear or Concern

After the implementation of the IDP platform, the teams responsible for IT infrastructure and information security may have to change their usual working procedures, which means they will have to restructure their processes.

Reality

With proper preparation and desire, the transition to a new methodology of work can be smooth and seamless. Organizations with a more mature DevOps culture will be better equipped to adopt and use an IDP platform effectively.

Platform Engineering Approach

Platform Engineering emphasizes a gradual and collaborative approach to process restructuring. Instead of imposing changes all at once, it encourages organizations to involve all relevant stakeholders early in the planning phase. By fostering open communication and providing clear guidance on the benefits of the new platform, teams are more likely to embrace the changes.

Additionally, Platform Engineering promotes the use of automation and standardized workflows, which can significantly reduce the burden of manual processes and make the transition easier. Continuous feedback loops and iterative improvements help ensure that the new processes are refined over time, aligning with the evolving needs of the organization.

4 The Need for Investment and the Length of the Journey

Fear or Concern

Implementing Platform Engineering and developing an Internal Development Platform (IDP) is a significant undertaking that requires ongoing investment and resource allocation. This is not a quick fix, and the commitment of time, money, and effort can be daunting for organizations, especially when the return on investment (ROI) may not be immediately visible.

Reality

While the journey to fully implement Platform Engineering is indeed long and requires sustained investment, the benefits it brings—such as increased release frequency, reduced errors, and enhanced development productivity—far outweigh the costs.

The success of an IDP initiative also heavily relies on the level of support from senior management, as their commitment ensures that the necessary resources and strategic alignment are in place.

Platform Engineering Approach

To mitigate concerns about investment and ensure a successful implementation, it’s crucial to avoid reinventing the wheel by creating custom tools unnecessarily. Instead, leverage existing industry standards, tools, and best practices that are already proven to work.

By staying informed about the evolution and current trends in the industry, your organization can adopt mature solutions that reduce the development burden and allow the platform to grow in a sustainable, cost-effective manner.

This approach not only optimizes resource use but also accelerates the time-to-value of your platform, making the journey more manageable and justified.

5 Resistance to Change and Organizational Misalignment After the Cultural Shift

Fear or Concern

Implementing Platform Engineering often requires a cultural shift, particularly in how teams collaborate and adopt new processes. There may be resistance from teams who are accustomed to traditional workflows and are hesitant to change. Additionally, misalignment between different departments, such as development, operations, and security, can slow down the adoption process.

Reality

While change is challenging, the alignment of teams around a common platform can lead to more cohesive, efficient operations and a stronger organizational culture. Successful Platform Engineering requires breaking down silos and fostering a culture of shared responsibility and continuous improvement.

Platform Engineering Approach

Focus on cross-functional collaboration and communication from the outset. Use workshops, training sessions, and regular feedback loops to ensure all teams are aligned and understand the benefits of the new platform. Encourage a culture of experimentation and learning, where teams are empowered to contribute to the platform's evolution.

6 Difficulty in Articulating ROI and Value Proposition

Fear or Concern

Senior management may struggle to see the immediate value of Platform Engineering, making it difficult to secure the necessary investment and support. The abstract nature of "platforms" can make it hard to articulate a clear ROI.

Reality

The value of Platform Engineering becomes evident over time through improved developer productivity, faster time-to-market, and reduced operational costs. However, these benefits may not be immediately visible.

Platform Engineering Approach

Leadership consensus and support are vital to the long-term sustainability and success of platform teams. Develop clear, measurable goals and metrics from the start. For example, track improvements in deployment frequency, error rates, and developer satisfaction. Regularly communicate these metrics to stakeholders to demonstrate the platform's impact. Creating a detailed value proposition that ties the platform's benefits to business outcomes can also help secure buy-in from senior leadership.

7 Skill Gaps and Training Needs

Fear or Concern

Adopting Platform Engineering may reveal skill gaps within the team, particularly in areas like automation, cloud-native technologies, and DevOps practices. This can create anxiety among team members who feel unprepared for the shift.

Reality

While these skill gaps can be a barrier, they also present an opportunity for professional development and growth. Investing in training can help bridge these gaps and empower teams to fully leverage the benefits of Platform Engineering.

Platform Engineering Approach

Implement a continuous learning program that provides team members with the training and resources they need to upskill. Consider partnering with industry experts for workshops or certifications. Encourage a culture of knowledge sharing within the organization, where experienced team members mentor those who are newer to the technologies involved.

Common Pitfalls and How to Avoid Them

Adopting Platform Engineering can bring numerous benefits, but there are common pitfalls that organizations may encounter during the process. Being aware of these potential challenges and knowing how to avoid them is crucial for a successful implementation.

1 Managing the Platform as a Project Instead of a Product

Pitfall

One of the most common mistakes is treating the platform as a one-time project with a start and end date, rather than as an ongoing product that evolves with the organization’s needs.

How to Avoid

Adopt a product mindset where the platform is continuously developed, iterated upon, and improved based on user feedback and changing business requirements. Establish a dedicated platform team responsible for the platform’s long-term success, ensuring that it remains relevant and valuable over time.

2 Misaligned Abstractions

Pitfall

Creating abstractions that are either too complex or too simplistic can render them unusable or irrelevant to the teams that need them. Poorly designed abstractions can lead to confusion and inefficiency.

How to Avoid

Ensure that abstractions are well-aligned with the needs of your development teams. Engage with end-users during the design process to gather feedback and iterate on the abstractions. The goal is to create abstractions that simplify complex tasks without oversimplifying to the point of losing essential functionality.

3 Forcing All Teams to Use the Golden Paths

Pitfall

While Golden Paths are intended to standardize and streamline development processes, forcing all teams to adopt them rigidly can stifle innovation and create resentment.

How to Avoid

Golden Paths should be seen as guidelines rather than strict mandates. Allow teams the flexibility to deviate from these paths when necessary, especially if their use case requires a different approach. Encourage teams to provide feedback on Golden Paths so they can be continuously improved and adapted to meet diverse needs.

4 Failing to Measure Platform Success and Capture Feedback

Pitfall

Without clear metrics and feedback mechanisms, it’s difficult to know whether the platform is meeting its goals or how it can be improved. This lack of measurement can lead to stagnation and a platform that fails to evolve.

How to Avoid

Implement key performance indicators (KPIs) to track the platform’s success, such as adoption rates, time-to-market improvements, and developer satisfaction. Regularly gather feedback from users to identify pain points and opportunities for improvement. This data-driven approach ensures that the platform continues to meet the needs of its users and the organization.

5 Overcomplicating the Platform

Pitfall

There is a risk of overengineering the platform by adding too many features and capabilities, which can lead to increased complexity and maintenance overhead.

How to Avoid

Focus on building a Thinnest Viable Platform (TVP) that addresses the most critical needs of your teams. Start small and expand the platform iteratively based on user feedback and evolving business needs. Prioritize simplicity and usability to ensure that the platform remains manageable and effective.

6 Lack of Cross-Functional Collaboration

Pitfall

Platform Engineering requires input and collaboration from multiple teams, including development, operations, and security. A lack of cross-functional collaboration can result in a platform that doesn’t fully meet the needs of all stakeholders.

How to Avoid

Foster a culture of collaboration and communication from the outset. Establish clear lines of communication and regular touchpoints between all teams involved in the platform’s development and use. Cross-functional collaboration ensures that the platform is comprehensive, secure, and aligned with the organization’s overall goals.

In this post, we have covered the main obstacles and common mistakes when implementing Platform Engineering in an organization, along with strategies to avoid them. If you want to dive deeper, in the next installment, we will discuss what capabilities a platform should have and how to launch it as a product. We look forward to your thoughts in the comments! 👇