DAY_02 / SECTION_04 // FOUNDATION
MODULE READY
The Three Ways of DevOps
The core principles that frame the systemic transformation of technology organizations. They build on each other — flow first, then feedback, then continuous experimentation. Skip a step and the next one fails.
SYS.NODE_01
ONLINE
double_arrow
Flow
Left to Right
Maximize the rate of flow of work from Development to Operations to the customer.
Make work visible, reduce batch sizes, prevent defects from being passed downstream,
and constantly optimize for global goals — not local ones.
// produces
ci.continuous_build()
wip.limit()
envs.on_demand()
SYS.NODE_02
IDLE
cached
Feedback
Right to Left
Create fast and constant feedback loops at every stage of the value stream.
Amplify feedback so problems are detected at the source — and fixed before they
become catastrophic. Quality is created where the work happens, not in QA at the end.
// telemetry streaming
SYS.NODE_03
STANDBY
autorenew
Continual Learning
Above the System
Foster a generative, high-trust culture that supports disciplined experimentation
and risk-taking. Treat failures as learning, not blame. Multiply the effects of new
knowledge — local discoveries become global improvements.
// requires
psych_safety = TRUE
postmortems.blameless()
// the first way · flow
Enables fast left-to-right flow of work from Development to Operations to the customer.
requires
- — Make work visible
- — Reduce batch sizes and intervals
- — Build in quality (don't pass defects downstream)
- — Optimize for global goals, not local ones
produces
- — Continuous build, integration, test, deploy
- — Environments on demand
- — WIP limits
- — Systems and orgs safe to change
// the second way · feedback
Enables fast and constant flow of feedback from right to left at all stages.
requires
- — Amplify feedback to prevent recurrence
- — Faster detection
- — Faster recovery
produces
- — Quality created at the source
- — Knowledge embedded where it's needed
- — Problems found and fixed before catastrophe
Mental image: swarm a problem the moment it appears. The cost of fixing a defect grows exponentially the further it travels from where it was created.
// the third way · continual learning
Generative, high-trust culture supporting disciplined experimentation and risk-taking.
requires
- — Treat failures as learning, not blame
- — Multiply effects of new knowledge
- — Local discoveries → global improvements
produces
- — Experiments that beat the competition's research
- — Cumulative organizational experience
- — Faster systems of work over time
// order matters: flow → feedback → experimentation. skip a step and the next one fails.
// verify_understanding()
help Knowledge Check
Question 1/2 Which "Way" of DevOps focuses on creating fast and continuous feedback loops?
// pick one to verify
// explanation The Second Way is about pulling feedback right-to-left through the value stream — detecting problems as they happen, fixing them at the source, and amplifying signals so they reach the right team fast. Flow (First Way) is about left-to-right speed; Continual Learning (Third Way) is about the experimentation culture built on top of the first two.
help Knowledge Check
Question 2/2 A team has fast deployment pipelines (the First Way) and good monitoring (the Second Way), but blameful postmortems and a fear of trying new things. Which Way are they missing?
// pick one to verify
// explanation Without psychological safety, the feedback loops you do have produce blame instead of learning. The Third Way is the cultural layer that turns flow + feedback into compounding organizational improvement.