Author profile

George Spafford

George Spafford is an IT researcher and author who writes about DevOps, cybersecurity and the practical work of improving technology operations.

1 published book 0 published articles

About George Spafford

George Spafford is a vice president analyst at Gartner, where his work covers DevOps and DevSecOps, platform engineering, site reliability engineering, and IT infrastructure and operations strategy. Before joining Gartner, he worked in consulting on ITIL, information security, IT strategy and service improvement. He holds an MBA from the University of Notre Dame and a bachelor’s degree in materials and logistics management from Michigan State University.

His books apply systems thinking and operational discipline to the problems technology teams face: unstable services, overloaded workflows, risky changes and poor coordination between IT and the wider business. His earlier collaborations include The Visible Ops Handbook and Visible Ops Security, both practical guides to making IT operations more controlled and measurable.

Spafford is best known to general readers as a co-author, with Gene Kim and Kevin Behr, of The Phoenix Project. First published in 2013, the novel follows Bill Palmer, an IT manager given ninety days to rescue a late, over-budget initiative at the fictional Parts Unlimited. Its factory analogy and “Three Ways” framework turn ideas about flow, feedback and continual learning into a workplace story.

Start with The Phoenix Project. It is the clearest introduction to Spafford’s recurring concerns because it shows operational failures unfolding through recognizable meetings, outages, queues and organizational conflicts rather than presenting them only as abstract management principles.

Published books

Co-author

The Phoenix Project

When a critical business initiative at Parts Unlimited falls dangerously behind schedule, IT manager Bill Palmer is abruptly placed in charge of technology operations and given little time to restore order. He inherits unstable systems, conflicting priorities, exhausted employees, weak coordination, and a project whose failure could threaten the company. Guided by the enigmatic Erik, Bill begins treating technology work as a production system rather than an endless series of emergencies. The Phoenix Project uses a fictional corporate crisis to introduce DevOps, the Theory of Constraints, flow, feedback, controlled work in process, and continual learning. Its central argument is that reliable technology delivery depends less on isolated technical heroics than on understanding the entire value stream. By dramatizing the relationships among development, operations, security, executives, and business units, the novel shows how organizational design and management decisions shape technical…

View book