Perspective · Learning Teams

Learning can begin before an incident

Publication date
Original date not recorded
Updated
Structure, summaries and source presentation
Article type
Perspective
Review status
Not peer reviewed

Summary

Organizations can learn before an incident by exploring tasks that routinely require adaptation, coordination or workarounds. Ask the people doing the work what helps and what gets in the way, then check proposed improvements under normal operating conditions.

The current journal collection is not peer reviewed. The update above records changes to structure and presentation; it does not indicate a technical or independent review.

Key takeaways

  • Successful work can reveal conditions that deserve attention.
  • Include people with direct knowledge of the task and its adaptations.
  • Return to participants to check whether changes helped.

People make work possible in conditions that rarely match a procedure perfectly. They coordinate, notice weak signals, adjust the sequence, and work around friction. A Learning Team creates room to understand those conditions with the people closest to them. There does not have to be an incident first.

Choose a useful question

Start with a task, a repeated difficulty, a change in equipment or staffing, or a job that regularly depends on extra effort. Frame the invitation around curiosity: “How does this work happen on a demanding day?” is more useful than “Why don’t people follow the procedure?”

Bring together people who perform and support the work. Ask them to describe a recent example in concrete detail: the goal, what they could see, the tools and time available, where the plan fit, and where they had to adapt. A facilitator should make space for different accounts and avoid turning the first conversation into a search for fault or a rush to solutions.

Move from understanding to action

A useful pattern is to separate the learning conversation from the action conversation. Between them, participants can check details, observe the task, and think about what was missed. The second conversation can then test possible changes against the actual conditions of the job.

  1. Explore: What helps the work succeed? What makes it harder?
  2. Reflect: Which assumptions should be checked with evidence or observation?
  3. Design: What change would make the work easier to perform safely?
  4. Verify: Who will see how the change works in practice, and when?

The number of meetings is less important than preserving that sequence. The team should know what it learned, what remains uncertain, who owns the next action, and how its members will hear back. Without follow-through, asking people to share what they know can erode trust.

Keep the methods distinct

After an event, an investigation may need to establish a supported account and test controls. A Learning Team can then explore a wider pattern of everyday work when the account raises questions it cannot answer. It can also start independently, before harm occurs, with a question about how a task succeeds.

Adapted and edited from Todd’s 2024 article archive. ← All articles

Sources and further reading

These primary sources support the background concepts. The author’s examples and interpretations are identified in the article; links do not imply agency endorsement.

Article record

Suggested citation

Jenkins, T. J. (n.d.). Learning can begin before an incident. Jenkins Industry Safety Journal. https://www.toddjeromejenkins.com/resources/articles/learning-before-an-incident

“n.d.” indicates that the original publication date is not recorded. Updated October 26, 2026: structure, summaries and source presentation.

Permanent article URL

Authorship & disclosures

Todd Jerome Jenkins, MS, CSP writes about occupational safety, event investigation, human and organizational performance, and practical uses of AI. He holds a Master of Science in Occupational Safety and Health and the Certified Safety Professional credential.

Published in Jenkins Industry Safety Journal, a publication of Jenkins Research Institute. The collection includes practical guides, explainers, perspectives and case analyses; they are not presented as peer-reviewed research.

Review status: not peer reviewed. Editorial policy, sources and corrections.

Submit a question or correction →