The Three Ways: Flow, Feedback, Learning¶
Definition¶
The Three Ways are three complementary, mutually reinforcing disciplines that form the philosophical foundation of DevOps practice. The First Way emphasizes fast, predictable flow of work through the system. The Second Way focuses on shortening and amplifying feedback loops to fix problems at their source. The Third Way cultivates a culture of experimentation, learning from failure, and continuous practice toward mastery.
In the Book¶
Erik Reid, a manufacturing consultant, articulates this framework to Bill Palmer while standing on a factory floor. He explains that the First Way "helps us understand how to create fast flow of work as it moves from Development into IT Operations, because that's what's between the business and the customer." The Second Way "shows us how to shorten and amplify feedback loops, so we can fix quality at the source and avoid rework." The Third Way "shows us how to create a culture that simultaneously fosters experimentation, learning from failure, and understanding that repetition and practice are the prerequisites to mastery."
The book grounds this in IT Operations context: Bill recognizes from his military background that "the need for rigor and discipline, and constantly practicing and honing our skills are important lessons" that apply directly to creating the predictability and mastery the Three Ways demand. The framework reframes IT Operations management away from reactive firefighting toward systematic, culture-centered improvement.
Why It Matters¶
The Three Ways provides a portable mental model for any technical organization to diagnose why it is stuck and which dimension to fix first. Most teams know they have chaos (lack of flow) or that they learn slowly (weak feedback), but the three-part structure prevents local optimization in one area from creating blind spots in another. It makes visible the difference between faster individual activity (First Way only) and faster value delivery (all three together), and explains why culture and learning practices are as load-bearing as process discipline.