Trust as foundation of DevOps
summary
Claim that trust makes teams faster and is the foundation of DevOps. Defines trust as readiness for unguarded interaction built from perceived competence, perceived intentions and history. Recommends cross‑functional teams sized to teams of ~10 (citing Dunbar and 150/15 thresholds), foster psychological safety and a failure‑tolerant culture, and remove slow controls (example: 229 change forms blocking daily deploys). Concrete actions: create product‑focused crews, enable social interaction, let leaders show vulnerability, and measure trust by decision and deployment speed.
AI-written summary · about
chapters (27)
- 0:00Introduction
- 1:52Dirks background
- 3:51DevOps
- 6:05Design Thinking
- 7:30Why Trust
- 9:50What is Trust
- 11:21Perceptions of Trust
- 14:14Trust and Speed
- 15:03Trust accelerates things
- 16:37How can we build trust
- 17:05Team size
- 18:29Dunbars number
- 22:06Trust is bad
- 22:41Diversity
- 23:23Social interactions
- 24:31How do groups exist
- 26:03Minimal Crew Parody
- 27:46Scientific explanation
- 29:29Magic
- 29:55Heterogeneity
- 30:26Safety
- 30:42Failure tolerance
- 31:54The iterative way
- 33:25Thomas J Watson
- 35:39Psychological safety
- 38:00Leaders
- 39:17Recap
