Pilot Critical Decision Making skills - Clifford Agius - NDC London 2023

Learn how to make time critical decisions just like airline pilots do around the world. As developers we all love a good framework well would it surprise you that pilots have a framework for making a team decisions on what to do in any situation be it an emergency, sick passenger or bad weather. The session is 40 minutes learning the TDODAR framework and then a fun exercise using the new skill in a team exercise to resolve a situation under time pressure you have less than 20 minutes GO!
Check out our new channel:
NDC Clips:
‪@ndcclips‬
Check out more of our featured speakers and talks at
ndcconferences.com/
ndclondon.com/

[@unfairworld9626]

Awesome

[@giyaanshgupta]

Appreciate it

[@allmhuran]

10 minutes in I already know this is going to be a great presentation.
A couple of comments on the point about everyone being an equal in the cockpit, such that even the junior member can dispute the decisions of the senior member. First of all, yes, people should definitely be able to speak up. But there does have to be some way to reach a conclusion. If the senior member says X, and the junior member says, no, not X, Y, then what?
Secondly, this situation is not really equivalent to what happens in software development teams. The difference is that if someone is sitting in a chair in the cockpit of a passenger aircraft, you can be quite certain that they have a very large amount of expertise and training, even if they are the junior member. You can probably be confident that they have passed various exams and qualifications checks. If you're flying a large passenger aircraft then you are an expert, even if you are an expert without a lot of experience on that particular model.
This is not true in software teams. You often can't be confident about the level of expertise of the most junior member on a software team. What qualificaton checks have they passed? They managed to get their resume through HR to the IT department, and they managed to get through a one hour (being generious) interview with a manager and (hopefully) a senior technical person. Often the technical interview is lacking, and even if it's a good technical interview it's obviously not even remotely close to the years of tests one has to pass before they can sit in the cockpit of a passenger aircraft.
Therefore I don't think it's reasonable to assume the same premise - that everyone is at least an expert, even if they don't have specific experience (in that type in the case of a pilot, or in your business domains in the case of a developer). And so I don't think the idea that "even the most junior member is a trusted source of information" can be applied to quite the same degree. Yes, still give them an opportunity to provide input, but until they have demonstrated their expertise (ie, they're no longer the junior member), the more senior people should have a stronger veto power.