Is Platform Engineering just all hype?

Gartner stirs the pot with the first Hype Cycle for Platform Engineering

Last week Gartner published the first edition of the Gartner Hype Cycle for Platform Engineering. Most in the community were pleased to see such recognition, but some were disappointed to see that IDPs, AI-Augmented Software Engineering, DevOps Platforms and even GitOps all gained a spot in the dreaded “Peak of Inflated Expectations” phase.

What is the Hype Cycle?

The Gartner Hype Cycle maps out the lifecycle of new technologies. It’s like a tech rollercoaster that starts with the initial hype, dips into the “Trough of Disillusionment” when the tech doesn’t meet sky-high expectations, and then climbs to a more realistic “Plateau of Productivity” as it matures and proves its worth.

Knowing where a technology stands on this curve helps businesses decide when to invest. Jumping in too early can mean wasted resources on immature tech, while getting in at the right time can give you a competitive edge without the headache of early bugs and inefficiencies.

What’s the problem with it?

One of the main benefits of the Gartner Hype Cycle is that it’s an incredibly simple graph that will often feel relatable - things that dominate the media will likely appear at the top of the hype curve. And that is also where Gartner draws the most criticism; is there credible research behind it, or are we just looking at a graph depicting how popular a set of loosely related buzzwords happen to be?

The big issue for me is that many decision makers, particularly those in large enterprise, will make assumptions about how useful or valuable a technology is based on its position on the graph. They’ll likely see the graph posted on social media, but never get round to reading the (paywalled) analytical report that accompanies it. As a result, those in large organisation who are innovating and seeing value will waste valuable effort re-iterating why what they’re doing is important. Worse, they’ll likely face harsh criticism from people with limited experience in subject.

The truth is that all innovations inevitably go through the fives stages, and its position on the Hype Cycle has little correlation with how much value your organisation can expect from implementing it.

What else was in the report?

The report that accompanies the graph is over 100 pages long and delves into Gartner’s analysis of each technology on the curve, as well as providing recommendations of where organisations should accelerate their efforts.

In addition to providing a definition and reasoning as to the benefits of each technology, Gartner also provides estimates on market penetration, drivers and obstacles, as well as a set of recommendations, sample vendors and additional reading for those that would like to learn more.

I won’t go too deep into Gartner’s recommendations, given its commercial property, but I can share where their research echoes my own experience. If you’re a busy IT leader, there’s a reason why Garner’s services are held in high regard.

It’s clear that three main pushes in the industry just now are around Developer Experience, producing software that’s Secure by Design, and building product-centric delivery models described in Team Topologies.

Developer Experience

Kate over on team RedMonk recently wrote a great piece on why developers are the new kingmakers, acknowledging the unique impact they can have within an organisation. I’ve seen the same change out in field, ever since the Covid pandemic, where the survival of many firms was reliant on the quality of customers’ digital journey. It seems naturally that top-tier developer talent find themselves in a strong position, able to choose between a raft of companies. IT Leaders must find ways to enable developers to be effective in their role and not held back by layers of crusty bureaucracy. If it is perceived to be too difficult to effect change within an organisation, developers will simply go elsewhere.

Secure by Design

Of course, it’s never that simple though. Whilst enabling developers, organisations are under increasing pressure to build quality software that is resistant to attack. The IBM Cost of a Data Breach Report continues to show that whilst we have more awareness of security and tooling to support, there is a steady increase in both the probability and severity of a security breach resulting in the theft of sensitive customer data. The main message I hear from organisations is that after a period of accelerated innovation and development as a result of the pandemic, they now want to normalise ways of working across development teams, rationalise an eclectic mix of duplicate tooling, and bring a new wave of simplicity to their software delivery lifecycle.

Team Topologies

And finally, it’s refreshing to see the most innovative of brands recognising that such change requires more than tooling; it needs an appreciation of human psychology and a desire to architect culture alongside technology. Since it’s publication in 2019, Team Topologies has become the go-to handbook for those wishing to understand how organisational structure, communication paths, and culture can work in harmony with technology to effect sustainable change. This is reflected by Gartner by its inclusion within the Slope of Enlightenment.

Summary

Gartner rightly receives a lot of attention when they release snippets from their reports, be that the coveted Gartner Magic Quadrant or the Hype Cycle. It’s important for the industry to appreciate that there is significant research behind these that is necessary to understand the full picture. With the Hype Cycle in particular, it’s important to recognise that the rating of a technology within the graph does not directly reflect the value a business might see or whether it’s an area that they should invest.