Decision making in black box scenarios
summary
A bought legacy system turns into a critical black box: weird language, no external support, no backups, and a complete work stoppage with direct financial loss. Practical responses are concrete: wait before acting so teams improvise, or run controlled experiments—flip components, trace APIs, locate the database, measure inputs and outputs. Emotional control matters—stay calm like a Zen monk—and document findings until migration succeeds, then treat changes as repeatable experiments.
AI-written summary · about
chapters (8)
- 0:00Intro
- 0:35Fire
- 2:12Decision Making
- 3:11Black Boxes
- 3:47constraints
- 4:34learnings
- 8:54ending
- 9:12parting thoughts
related talks
29mGaining Insights from a Black Box System
22mThe magic of crisis
48mHarnessing Chaos; the hidden ingredient behind building better systems
41mLessons from Mission-Critical Systems in Fast-Moving Industries
49mHard Choices, Tight Timelines: A Closer Look at Skip-level Tradeoff Decisions...
26mBreaking Systems for Resilience
29mTaking Over & Managing Large Messy Systems
21mSelling your Company on Chaos Engineering