Stop 01 · DevOps FoundationsTopics · 9/9

The 3 Ways of DevOps (Flow, Feedback, Learning)

In short

The novel The Phoenix Project boiled DevOps down to three simple ideas. They sound obvious, but almost every slow, unhappy tech team is breaking at least one of them.

A framework from 'The Phoenix Project' — the First Way optimizes flow from dev to production, the Second Way creates fast feedback loops, and the Third Way builds a culture of continual experimentation and learning.

The mascot at a street tea stall pours tea into a row of glasses while a customer gives a thumbs up.

Think of it like this

A busy chai stall

Flow: tea moves quickly from stove to glass to customer, with no pile-up. Feedback: a regular says 'less sugar' and the next cup is fixed. Learning: the bhaiya tries a new elaichi blend on Sundays and keeps what customers love.

Watch it happen

The three ways in order

Flow

Feedback

Learning

1/3First Way, Flow: make work move smoothly left to right, from idea to production, in small batches.

The big ideas

What you need to know

Make work visible

A board showing every task helps you see where work piles up. You can't fix a bottleneck you can't see.

Fast feedback is cheap

A bug caught by a test in 5 minutes costs little. The same bug found by a customer costs a lot more.

Safe experiments

Feature flags and canary releases let you try ideas on a few users first, so failures stay small.

Turn incidents into lessons

Every outage should leave behind a fix, a test or a runbook, so the team gets stronger each time.

Save yourself the pain

Common mistakes

Oops

Speeding up deployments while test results still take a day to arrive.

Do this instead

Flow without Feedback just ships bugs faster. Make sure failures reach developers within minutes.

Oops

Punishing people when an experiment fails.

Do this instead

The Third Way needs safety to try things. Keep experiments small and celebrate what you learned.

Your mission

Find the broken way

~15 min

Quick check

A team deploys 10 times a day but only learns about bugs from angry customer emails a week later. Which Way is weakest?

Go deeper

1Read a summary of 'The Phoenix Project' or 'The DevOps Handbook' for this framework's origin.
2Identify a real practice (like automated testing) and map it to which of the 3 Ways it primarily serves.
3Learn why fast feedback (the Second Way) is often the highest-leverage improvement for a struggling team.