The emotional chaos of deploying code
summary
Claim: routine deploys routinely trigger hidden emotions across an org, from sales demo breakage to support ticket surge, and those effects are measurable by missed demos, extra support hours, and surprise rollbacks. Practical fixes include written team deploy checklist, staging discipline, async release notes, product sync meetings, explicit timezone decisions, QA‑agreed acceptable bug state, and manager reassurance while watching adoption metrics; when those processes run the release works and downstream teams keep their SLAs.
AI-written summary · about
chapters (12)
- 0:00Start
- 7:05Deploy time
- 7:34The day after
- 8:54Paloma Medina's BICEPS model
- 12:06How they felt Amir from the Marketing Team
- 12:42How they felt Will the Engineer
- 13:38How they felt Dave from the sales team
- 14:02How they felt Antonio from the support team
- 14:19How they felt the engineering team
- 15:55Preparing the build
- 17:59Planning the deploy
- 21:06How do I get there?
