This article is based on reporting originally published by InformationWeek covering the DevOps Enterprise Summit in San Francisco.
DevOps Is About Solving Real Business Problems
At its core, DevOps is not a technology — it is a business strategy. Some organizations adopt DevOps to accelerate delivery. Others need to capitalize on a market opportunity before a competitor does. Still others face shrinking budgets and must find a way to do more with less. Regardless of the motivation, organizations at the DevOps Enterprise Summit in San Francisco shared a common experience: the path to DevOps is paved with cultural resistance and hard lessons.
What follows are four real-world case studies presented at the summit, each illustrating a different context for DevOps adoption and the practical outcomes — both successes and setbacks — that resulted.
U.S. Department of Defense: Doing More With 30% Less
The Department of Defense’s Joint Warfare Analysis Center (JWAC) did not choose to adopt DevOps from a position of strength. Over several years, the center lost 30 percent of its staff and budget, making it impossible to maintain its existing processes at scale.
Kurt Hockaday, a data systems technical lead for JWAC, told summit attendees that the center was left with no viable alternative.
“We simply couldn’t keep doing what we were doing.”
Kurt Hockaday, Data Systems Technical Lead, JWAC
Working with outside consultants, JWAC developed a set of guiding principles aimed at speeding up service delivery, managing services more proactively, bringing consistency to operations, and enabling self-service provisioning. Early results were encouraging: the team reduced environment build times to roughly one week and decreased dependence on manual admin access through automation.
However, the journey was not without setbacks. Self-service provisioning remained incomplete, and the team found itself re-learning and re-implementing foundational processes that had been assumed to be solid.
Hockaday’s lesson for other government adopters was direct:
“Battleships can’t turn on a dime, and neither can fairly mature government organizations. Introducing large-scale change into the DoD is never an easy endeavor.”
Kurt Hockaday, JWAC
The JWAC story is a useful reminder that DevOps adoption in regulated, resource-constrained, or hierarchical environments requires patience and realistic timelines. Progress is still progress, even when it is incremental.
Nationwide Mutual Insurance: Fixing Test Bed Bloat to Unlock Speed
Nationwide Mutual Insurance set out with an explicit goal: become a world-class software development organization. As the company began embedding DevOps practices, one of the first obstacles it uncovered was the state of its testing environments.
“When you’ve been testing for so long, it’s natural that you form a bloat around your test beds. Often they were broken and no one was paying attention.”
Cindy Payne, Director of IT Application Development, Nationwide
After applying DevOps principles to streamline and stabilize those test beds, one development team reported that the time to receive test results dropped to just two hours — a dramatic reduction from previous baselines.
The business impact of that improvement became tangible almost immediately. When Hurricane Harvey triggered a surge in food-related insurance claims from the Houston area, Nationwide’s developers were able to re-engineer the relevant claims workflow by 40 percent in just eight hours.
“A year ago, this kind of change would have taken about 90 days.”
Jim Grafmeyer, Digital Solutions Architect, Nationwide
This example illustrates one of the clearest value propositions for DevOps in traditionally slow-moving industries: when a business event demands rapid response, teams with mature DevOps practices can act in hours rather than months.
AdvancedMD: Every Common Mistake in One Journey
John Esser, senior director of IT and data center operations for medical SaaS provider AdvancedMD, offered one of the summit’s most candid accounts. His story is effectively a catalogue of anti-patterns — and why avoiding them matters.
Mistake 1: Creating a Centralized DevOps Team
Esser’s first instinct was to stand up a dedicated, centralized DevOps team. He was quick to acknowledge the outcome:
“Worst decision I’ve made. It was a bottleneck, it was a chokepoint, it was a constrained resource, and it was a silo.”
John Esser, Senior Director of IT, AdvancedMD
The fix was to embed DevOps practices directly into individual development teams — the model most practitioners now recommend. But that created its own friction.
Mistake 2: Underestimating Cultural Resistance
Once DevOps responsibilities were distributed across teams, many team members pushed back, treating DevOps as someone else’s concern — something needed only in a specific corner of the organization, not in their work.
Mistake 3: Ignoring Technical Debt in the Architecture
The company’s monolithic data model was incompatible with the autonomy and loose coupling that DevOps practices depend on. Breaking up a single, shared data store is painful work, but it was necessary before meaningful progress could be made.
Mistake 4: Letting Past Success Justify the Status Quo
A prevailing attitude within AdvancedMD held that because the company had succeeded without DevOps, it did not need DevOps. Esser’s response:
“Where we are and where we need to go is something different. We needed to create a different kind of success for the future.”
John Esser, AdvancedMD
Mistake 5: Equating DevOps With Automated Deployment
Perhaps the most pervasive misconception Esser encountered was that DevOps simply meant automated deployments. While automation is a component of DevOps, conflating the two causes organizations to stop short of the cultural, organizational, and process changes that make DevOps genuinely transformative.
“That’s something you want to do, but it’s definitely not DevOps.”
John Esser, AdvancedMD
Amazon Prime Now: Adapting a System Built for Days to Deliver in an Hour
Tison Mathew — now CTO for Alignment Healthcare, but previously working on Amazon’s Prime Now service — described one of the more technically demanding DevOps contexts at the summit. Prime Now promises customers free delivery within one hour. The challenge: the underlying infrastructure had been designed for two-to-five-day delivery windows.
To bridge that gap, Mathew’s team applied DevOps practices within the framework of what Amazon calls its Virtuous Cycle: a feedback loop in which infrastructure investment drives efficiency, speed, and reliability, which in turn fuels customer demand and further growth.
The work required continuous iteration on ordering and fulfillment systems under demanding operational constraints — the kind of rapid, incremental delivery that DevOps is specifically designed to support.
Mathew drew a direct line from that experience to his current mission in healthcare:
“I want to do the same thing for healthcare. That’s my passion now.”
Tison Mathew, CTO, Alignment Healthcare
Key Takeaways Across All Four Stories
Despite coming from radically different industries and contexts, the organizations at the DevOps Enterprise Summit shared several consistent lessons:
- Culture is the hardest problem. Technical tooling is the easier part. Getting people to change how they work, collaborate, and think about ownership is where most DevOps efforts stall.
- Centralized DevOps teams create bottlenecks. DevOps practices are most effective when embedded within cross-functional delivery teams, not isolated in a dedicated silo.
- Legacy architecture will slow you down. Monolithic systems and shared data stores are structural impediments to the autonomy and speed that DevOps requires. Addressing technical debt is part of the transformation.
- Progress is non-linear. Setbacks — such as JWAC’s incomplete self-service provisioning — are normal. The measure of success is whether the organization keeps learning and iterating.
- DevOps is not automated deployment. Automation is a tool. DevOps is a discipline that spans culture, process, measurement, and collaboration across the entire software delivery lifecycle.
- The business case becomes clear under pressure. Nationwide’s ability to respond to Hurricane Harvey in eight hours instead of ninety days is the kind of outcome that makes DevOps investment self-evident to business stakeholders.
The Broader Lesson: DevOps Works Across Industries
The DevOps Enterprise Summit brought together leaders from defense, insurance, healthcare, and e-commerce — and the consistent message was that DevOps principles apply regardless of industry vertical. The specifics of implementation differ, the pace of change varies, and the obstacles are shaped by organizational context. But the underlying principles — fast feedback, automation, continuous improvement, shared ownership, and a focus on delivering value — translate everywhere.
Whether your organization is a government agency navigating budget cuts or a SaaS company wrestling with a monolithic architecture, the question is not whether DevOps applies. The question is how to begin — and how to sustain the momentum when the inevitable resistance arrives.