What do Wildland Fire Fighters and Software Engineers have in common?
They’ve both taken the position that the most important thing after an incident is LEARNING. What may be shocking to some, is they both believe that the learning they produce is more important than corrective actions. In fact, corrective actions are not required – or even desired – for some incidents.
In this session, leaders from both communities will share how they learn from incidents. They will explore commonalities in their practices, what is most important for learning, and what they do differently and why.
“We love incidents. Well, love is a strong word. But incidents don't have to be a terrible experience. The community we started has spent a lot of time understanding just how much value you can get out of incidents, and how they can be used as a way to disseminate expertise throughout the organization.”
Learning From Incidents Community of Practice (Software)
- Persephone Whelan led the team that recently revised Wildland fire Learning from Unexpected Outcomes and Learning Review process.
- Joe Harris has spent the last two years as the chair of the Response Protocol steering committee which is in charge of training and implementation of the accident review processes within the wildland fire community.
- Thai Wood is part of the Software Learning from Incidents Community of Practice.
