October 2014 (approximate date). gene-kim, through it-revolution, founded the DevOps Enterprise Summit (DOES) — a conference specifically designed for large, complex organizations adopting DevOps principles.
Why a separate conference. The devopsdays-conference series was practitioner-driven and community-organized, with an audience concentrated in tech-forward companies and web-native organizations. Enterprises — banks, insurers, retailers, government agencies — faced different challenges: legacy systems, compliance requirements, organizational scale, and skeptical leadership. The DevOpsDays format did not fit their needs, and the community norms were not calibrated for enterprise audiences. DOES created a distinct venue with enterprise transformation case studies as the core format.
What DOES featured. The distinctive format was transformation narratives from large organizations: Target, Nordstrom, ING, financial institutions. Rather than practitioner how-tos, DOES presentations focused on organizational change — how did you get leadership buy-in, how did you handle compliance, what failed, what the three-year arc looked like. This was the content the-phoenix-project had dramatized fictionally; DOES provided the real cases.
Scope and trajectory. DOES ran annually in San Francisco and later expanded to European events. Through approximately 2023 it maintained the DevOps Enterprise Summit name before being rebranded to the Enterprise Technology Leadership Summit in 2024-2025, reflecting both the broadening of the content beyond DevOps specifically and shifts at IT Revolution. The archive of talks constitutes a substantial documentary record of enterprise DevOps adoption.
Significance. DOES institutionalized the idea that DevOps applied to large enterprises, not just web-native startups. The "that only works at Netflix/Google/Etsy" objection was the primary barrier to enterprise adoption; DOES systematically collected evidence against it. Gene Kim's curation of the case studies — what qualified as a genuine transformation versus a surface-level tooling adoption — shaped what counted as success in enterprise DevOps.
The exact date is approximate (October 2014).