«Zero Trust» is for Networks, Not Your Teams
summary
Argues that zero trust belongs to networks, not people, and that real reliability comes from people-based resilience defined as resilience is a verb with four measurable capacities: rebound, robustness, graceful extensibility and sustained adaptability. Cites Project Aristotle and DORA linking psychological safety to higher software delivery performance, recalls March 2020 teams that improvised successfully, and prescribes concrete practices: service contracts between squads, social contracts, measurable long‑term metrics, guard rails that make the right path the easy path, and bring a brick not a cathedral.
AI-written summary · about
chapters (10)
- 0:00Intro
- 0:30The hardest thing about DevOps
- 3:16Resilience is a verb
- 8:22Socio-technical systems
- 14:12Conway's Law
- 19:46What is psychological safety?
- 24:17Trust within teams
- 29:06Trust of teams
- 35:13Bring a brick, not a cathedral
- 40:13Outro
related talks
05mBuilding resilience in our organizations...
46mTrust as foundation of DevOps
13mTrust and Teams
51mIt’s All Geek to Me: Communicating The Business Value of Zero Trust
27mLeveraging Infrastructure as Code to Create Zero Trust Access to Your Apps and Infrastructure
39mProtect Your Application, Not the Network. Add Zero Trust Superpowers to Your Critical...
20mRefactoring Trust on Your Team
49mBuilding Trust in Teams