Poised to deploy: The C-suite and adaptive capacity
summary
Defines poised to deploy as knowing what the platform is supposed to do, how it actually works, what it’s doing now, and being able to change it, predict effects, force behavior and handle the inevitable snafus. Calls out that deployment tooling—deploy hooks, code repositories, forks and branches—matters but is insufficient because an organizational layer tracks intent and current state. Argues that metrics like “53 deploys/day” or “72 deploys/day” mislead and that counting deploys is nonsense; notes a tiny schema change can trigger outsized human resistance, showing gearhead focus misses risk.
AI-written summary · about
related talks
26mThe emotional chaos of deploying code
38mJust Ship It!
32mHow Your Deployment Strategy Influences How People Code
26mMission Critical Mindset Building a Culture of Resilience in DevOps Teams
33mWhat Got Us Here Won’t Get Us There: A Story of Transformations
45mBuilding and Scaling High Performing Technology Organizations
23mThe Linear Deployment Experience
31mReducing the fear of go-live