Author profile

Kevin Behr

Kevin Behr is an IT management practitioner and co-author of business novels and practical guides about DevOps, operational improvement and organizational change.

1 published book 0 published articles

About Kevin Behr

Kevin Behr is an IT management practitioner, adviser and author. He founded the Information Technology Process Institute and has held senior technology leadership roles. His work draws on decades spent helping organizations improve the way technology teams operate.

Behr writes about IT service management, DevOps and organizational performance. He is particularly interested in the systems behind daily work: constraints, unplanned tasks, fragile processes and the habits that keep teams trapped in cycles of emergency repair. His books turn these concerns into practical frameworks or workplace narratives.

He co-wrote The Visible Ops Handbook with Gene Kim and George Spafford, offering a staged approach to stabilizing and improving IT operations. The same authors later produced The Phoenix Project, first published in 2013. This business novel follows Bill Palmer at the fictional Parts Unlimited, where an over-budget initiative and recurring outages expose deeper problems in the flow of work. A graphic-novel adaptation followed in 2024.

Begin with The Phoenix Project. Its pressured meetings, production failures and overloaded specialists make abstract ideas about DevOps and the Theory of Constraints concrete. It is also the clearest introduction to Behr’s recurring subject: how leaders can replace firefighting with visible, manageable work.

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