Hard Choices, Tight Timelines: A Closer Look at Skip-level Tradeoff Decisions...
summary
Analysis mines a public corpus of over 10,000 incident reports (the the VOID), then runs a vignette study with 27 participants using scenario probes and thematic coding. Key claims: public reports rarely include explicit tradeoff reasoning; incident decisions are complex, cross‑boundary, and emotionally loaded; senior management often still engages in technical diagnosis. Concrete recommendations: run game days that practise roll back and data loss choices, map what info legal needs before involving them, and record tradeoff rationales in postmortems.
AI-written summary · about
chapters (11)
- 0:00Introduction
- 1:03Why trade-off decisions feel hard
- 5:42Researching software incident trade-offs
- 10:13Searching incident reports for evidence
- 16:53Why organizations avoid trade-offs
- 17:58Using vignettes to study decisions
- 20:05Multi-phase incident scenario
- 25:02Key research findings
- 44:22Practical recommendations
- 46:27Limitations and future research
- 48:34Closing and call to action
related talks
44mDevCorp: Choose Your Own Adventure
35mLeader in the Land of Dilemmas
22mDecide Like a Pro: Navigate the Time-Quality-Cost Trifecta
39mThe Art of Technical Decision Making
40mDo we need it?
18mMaking Better Decisions in Incidents (Why Playbooks Aren’t the Answer)
32mThe Art of Technical Decision Making
19mLeader in the Land of Dilemmas