Ignite: What we’re learning about burnout and how a DevOps culture can help
summary
Explains concrete steps: use value stream mapping to establish a baseline, have the actual practitioners map each step, and measure cycle time (dishes routinely take 30 minutes in the example) to find waste. Shows a small experiment: shift responsibility so one role empties the dishwasher while others load it, cutting end-to-end time and friction. Connects clinical findings that burnout raises cardiovascular risk similar to BMI and cites the State of DevOps link between job satisfaction and company success.
AI-written summary · about
chapters (11)
- 0:00Intro
- 0:13Where do I start
- 0:29Value Stream Mapping
- 0:59Common Understanding
- 2:14The Process
- 2:59Constraints
- 3:29The Room
- 4:01The Steps
- 4:17When to Improve
- 4:32Empty the Dishwasher
- 4:47Summary
related talks
28mBreaking the Trenches: Nurturing a Continuous Improvement Culture in DevOps
29mDEVOPS DAYS MTL 2018 - Jason Yee
05m5 ways to burnout your engineers
06mIgnite - Go Rin No Sno - What DevOps Can Learn From a ...
25mBurnout: The Hidden Failure Mode of High-Performing Teams
47mDevOps or DevX – Lessons We Learned Shifting Left the Wrong Way
40mDev (depresiya) Ops
46mManaging the Burnout Burndown
