Good read. Here's the crux for me: > If something went wrong in the journey to theatre — such as a crucial wire becoming unattached — all staff would rush to t

Good read. Here's the crux for me: > If something went wrong in the journey to theatre — such as a crucial wire becoming unattached — all staff would rush to the issue in an attempt to fix it, rather than having the discipline and structure for one dedicated staff member to do so in a less panicked manner. I've never been a part of F1 racing or pediatric surgery, but even in plain old software development, it's always been great to step back and look at a process that we repeat; there's often a few improvements that seem obvious in retrospect, that don't pop out until you analyze the process.