One post tagged with "your"

If your platform team’s North Star is getting every development squad into the “elite” performer bracket for DORA metrics, you’re aiming at the wrong target. You’re probably making things worse. I’ve watched organizations obsess over average deployment frequency or lead time, only to see platform complexity balloon and team friction increase. The real goal isn’t to build a rocket ship for your top performers; it’s to build a reliable highway for everyone else.

The corrective lens comes from a pivotal but under-appreciated source: the CNCF’s Platform Engineering Metrics whitepaper. It makes a contrarian, data-backed claim that cuts through the industry hype. The paper states bluntly that platform teams should focus on “improving the performance of the lowest-performing teams” and “reducing the spread of outcomes, not just the average.” This isn’t about settling for mediocrity. It’s about systemic stability and scaling effectively. When you measure platform success by how much you compress the variance in team performance, you start building for adoption and predictability—not vanity metrics.

The Misapplied DORA Dashboard​

The DORA research is foundational, but it’s been weaponized by poor management. Deployment Frequency, Lead Time for Changes, Time to Restore Service, and Change Failure Rate are diagnostic metrics for teams. They were never intended to be uniform, organization-wide KPIs. A team maintaining a legacy financial monolith with regulatory gates will never deploy daily. A greenfield mobile app team shouldn’t be the benchmark for everyone.

Yet, leadership demands: “Why isn’t Team X also elite?” So, platform teams are tasked with building capabilities to chase these uniform highs. This leads to a fatal misalignment. The platform’s roadmap gets driven by the needs of the already-fast teams who want newer, shinier abstractions, while the teams struggling with basic deployment toil get left further behind. The performance spread widens, and systemic risk increases.

Why Variance is the Real Enemy​

The CNCF paper’s focus on the lowest performers isn’t about compassion; it’s about risk management and predictability.

1. Reduces Systemic Risk: A single team with a terrible Change Failure Rate or a glacial lead time can become a bottleneck for the entire product release. It can cause outages that impact dependent services. Improving the floor of your performance distribution directly mitigates this operational risk. As the whitepaper notes, this focus “reduces risk” for the entire organization.
2. Enables Business Predictability: Product and business planning are built on forecasts. If delivery timelines are a wild guess because team capabilities vary wildly, planning fails. Compressing performance toward a reliable, predictable baseline makes forecasting possible. This is what Abby Bangser means by “The goal is predictability, not necessarily pushing every team to elite.”
3. Scales Effective Practice: A platform is a vehicle for disseminating best practices. If it only serves the teams that already have their act together, it fails. Success, as Manuel Pais frames it, is about the “flow of most teams, not top ones.” By making the “paved road” so simple and effective that struggling teams naturally adopt it, you encode and scale good practices where they’re needed most.

Measuring the Spread, Not Just the Average​

So, what do you put on your dashboard instead?

• Ditch Averages, Embrace Distributions: Stop reporting “Average Lead Time: 3 days.” Start reporting “Lead Time Std Dev: Reduced from 10 days to 4 days over Q2” or “Bottom Quartile Lead Time: Improved from 14 days to 7 days.” This shift tells the true story of platform impact.
• Track the Paved Path Adoption Rate: The most telling platform metric might be the percentage of services/deployments using the platform's standardized workflow. High adoption with low outcome variance is a slam-dunk success signal. It means the easy path is also the good path.
• Use Cognitive Load as a Leading Indicator: The whitepaper hints at this. Survey developer cognitive load. A decrease in average reported cognitive load is a powerful leading indicator that DORA variance will soon follow. If your platform makes the hard things easier for the teams struggling the most, you’re winning.

Addressing the Counterarguments: Yes, You Can Still Innovate​

The immediate pushback is that this approach fosters complacency and stifles high performers. This is a false dichotomy.

A well-designed platform provides a solid, boring, and incredibly reliable foundation for 80-90% of all use cases—this is the variance-reducing constraint. However, it must also provide well-abstracted escape hatches. Elite teams should be able to opt-out of the paved road for a specific, justified reason (e.g., experimenting with a new service mesh) without having to rebuild the entire CI/CD pipeline from scratch. The platform enables their innovation by giving them a stable base to jump from, not by letting them pave their own chaotic roads everywhere.

The goal is not to cap the ceiling but to raise the floor so high that “going off-road” is a deliberate, costly choice for exceptional needs, not a necessity borne of frustration.

Practical Takeaways for Your Platform Team​

1. Audit Your Dashboards Today: Replace every average DORA metric with a view of its distribution (a histogram) and track the standard deviation over time. This one change will reframe every roadmap discussion.
2. Prioritize by Friction, Not by Glamour: Your highest-priority features should come from the teams using your platform the least or struggling the most. Their pain points are your most valuable product insights.
3. Redefine Platform ROI for Leadership: Stop talking about “faster deployments.” Start framing value as “reduced operational risk” and “increased delivery predictability for product planning.” Translate a reduced standard deviation in lead time into weeks saved in project timelines. This is the language of business.

The broader implication is that platform engineering is ultimately about engineering management. It’s about applying constraints thoughtfully to create a more predictable, scalable, and lower-risk system. The CNCF whitepaper gives us the correct measure: don’t be distracted by the stars. Focus on lifting the tide for everyone, and you’ll build a platform that truly moves the business forward.