> 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.
It reminded me that story I saw on internet where companies wanted to help give meals for poor people and most of them gave money, except for Toyota, which improved the chain of supply by applying the methodology they use themselves to build their cars. And basically they improved by ~40% the number of meals delivered per day.
The strategy department may be laughably bad, but at least with pitstops they've got it nailed down. They currently hold the fastest pitstop of the season [0] and they've been consistently faster than the rest of the field with pitstops so far.
Basically, standardize the work with clear roles and responsibilities.
> 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.
[1]: https://www.formula1.com/en/latest/article/williams-pit-stop...
[0] https://www.formula1.com/en/latest/article/2025-dhl-fastest-...