This article is based on reporting originally published by Computer Weekly ahead of the DevOps Enterprise Summit, London, June 2017, featuring insights from Gene Kim and John Willis, co-authors of The DevOps Handbook.
The Myth That DevOps Is Only for Startups
Despite a growing list of large organisations successfully adopting DevOps practices, a stubborn misconception persists in the enterprise world: that continuous delivery and DevOps transformation are achievable only by technology-native companies like Google, Amazon, and Facebook—not by large, complex organisations with decades of legacy infrastructure and regulatory burden.
Gene Kim, co-author of The DevOps Handbook, pushes back hard on this view. Speaking to Computer Weekly ahead of the DevOps Enterprise Summit in London (June 2017), Kim pointed to regulated industries—public sector bodies and financial services firms—as some of the most compelling proof points that DevOps can work at enterprise scale.
“If HM Revenue and Customs can do it, if Zurich Insurance and organisations like Allianz can do it—which are all organisations that have a reputation for being conservative—it just gives us more evidence that it really can be done.”
— Gene Kim, co-author, The DevOps Handbook
Kim noted that before he can even begin making the case for DevOps, enterprise leaders often pre-empt the conversation with objections: security, compliance requirements, change management processes, and entrenched legacy code are the most common. Yet organisations operating under government regulation and statutory restriction have managed to overcome precisely these barriers.
Common Enterprise Objections to DevOps
Resistance to DevOps in large organisations typically clusters around a predictable set of concerns:
- Security and compliance: Regulated industries worry that the speed of continuous delivery conflicts with audit trails and change-approval processes.
- Legacy systems: Monolithic architectures and decades-old codebases are seen as incompatible with modern CI/CD pipelines.
- Organisational complexity: Large enterprises have more stakeholders, more silos, and more entrenched processes than startups.
- Cultural inertia: Changing how developers and operations teams collaborate requires sustained leadership commitment.
John Willis, then Director of Ecosystem Development at Docker and a fellow co-author of The DevOps Handbook, acknowledged that enterprise practitioners who have succeeded with DevOps are often treated by peers as exceptions rather than examples to follow.
“People say things like: ‘It’s different for my company. You don’t know how hard it is, and I do. I really do.'”
— John Willis, co-author, The DevOps Handbook
How Scaremongering Puts CIOs Off DevOps
Willis identified a second major barrier: the way DevOps is marketed and sold to enterprise decision-makers. Aggressive sales pitches and over-the-top evangelism have caused many CIOs to become understandably cynical about the entire movement.
“I’ve watched a lot of sales people over the years, on calls I’ve done, and they’ll go into enterprises and say—after just 10 minutes of meeting them—you’re doing it all wrong and you need to stop now and do it this way instead.”
— John Willis
Few experienced IT leaders respond well to that approach, especially when it is paired with doom-laden predictions about being overtaken by competitors. Willis described a pattern he has observed repeatedly: every two years or so, a new technology or practice is declared existentially important, and those who don’t adopt it immediately are positioned as dangerously behind.
“I spoke to a large financial organisation the other day and five years ago they were told they had to use Puppet. The world would be doomed if they didn’t go to Puppet. Then they started hearing that if you don’t do DevOps, you’re doomed, and then they’re told a year or so later that if you’re not doing Docker, you’re horrible and should be thrown in jail.”
— John Willis
The practical consequence is that CIOs develop a healthy—sometimes excessive—scepticism toward any new IT practice, even one with genuine, demonstrated value like DevOps. Willis’s advice: look past the hype cycle and focus on peer organisations that have made measurable progress.
Are You Ever “Done” With DevOps?
A question that surfaces frequently among enterprise IT leaders is whether there is a defined finish line for DevOps adoption. Kim argues this framing misunderstands what continuous delivery and continuous improvement actually mean—there is no completion state, because the goal is ongoing capability-building, not a one-time project.
That said, Kim is clear that progress is both measurable and rewarded. He pointed to specific organisations—Capital One in the US, ITV and Barclays in the UK—as examples of enterprises that, while not at 100% DevOps adoption, have made enough progress that the leaders championing those efforts are being given greater organisational authority as a result.
“My prediction is they will continue to be elevated to influence the practices in as much of the organisation as possible, and they can share their experiences about how to foster these initiatives without getting fired, or having it killed by the more conservative elements within the organisation.”
— Gene Kim
External Forces Beyond IT’s Control
Willis raised an important and often overlooked point: even organisations that execute a DevOps transformation correctly can be derailed by macro-economic forces entirely outside IT’s influence. A retailer that builds excellent CI/CD pipelines and a strong DevOps culture can still struggle if the retail sector itself is under structural pressure.
“I get this pain in my heart when I see a company that does everything right, but then they get off tilt—not because of anything they’ve done with IT, but because of the economics of the business they’re in.”
— John Willis
Kim echoed this with a widely cited example: no IT transformation could have saved Blockbuster from the structural disruption caused by streaming services. Technology capability is a necessary but not sufficient condition for surviving disruption.
“No amount of technology could have saved Blockbusters. Maybe they could have found a way out, but technology in and of itself could not have saved Blockbusters.”
— Gene Kim
Why DevOps Still Matters for Large Enterprises
Despite the caveats, Kim’s broader argument is that DevOps capability is increasingly table-stakes for any established enterprise that wants to remain competitive. Large brands in any industry vertical face a growing number of smaller, more agile competitors who can iterate faster and deliver value to customers more efficiently.
The practical implication for enterprise IT leaders:
- Treat DevOps as a long-term capability investment, not a project with an end date.
- Look to peer organisations in similarly regulated or complex environments for credible proof points.
- Be sceptical of vendor-driven scaremongering, but don’t let that scepticism prevent genuine modernisation.
- Measure progress, reward the people driving it, and expand successful practices incrementally across the organisation.
- Recognise that IT transformation improves competitive agility but cannot compensate for fundamental business model problems.
The organisations that have made DevOps work at enterprise scale—in regulated financial services, government, and broadcasting—demonstrate that the barriers most commonly cited are real but not insurmountable. The challenge is sustained leadership commitment and a willingness to learn from those who have already made the journey.