Perspective · Leadership

Accountability without reflexive blame

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

Summary

Accountability without reflexive blame means examining decisions, responsibilities and working conditions before judging an event. A fair response uses evidence, considers what people knew at the time and follows through on changes to the work system.

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

  • Establish what happened before judging an individual's decision.
  • Examine organizational responsibilities as well as the person's actions.
  • Evaluate follow-through by whether work conditions and protection improve.

After an event, “Who is accountable?” can be a fair question. It becomes less useful when it is answered before we understand the work. A person’s action is visible; the conditions surrounding that action often need to be uncovered.

Ask what shaped the decision

What was the person trying to accomplish? What information and tools were available? Were there competing demands, unclear handoffs, or a control that looked workable on paper but failed in practice? These questions do not excuse every decision. They make a judgment better informed. Human and Organizational Performance (HOP) asks leaders to examine how people and systems interact. A useful standard is to learn before assigning responsibility and to examine organizational decisions alongside individual ones.

Accountability has more than one owner

Workers have responsibilities to colleagues and to the work. Leaders have responsibilities for the resources, priorities, procedures, and controls they create and maintain. An organization should be willing to examine both. It should also distinguish a mistake, a reasonable adaptation under pressure, and deliberate harmful conduct rather than flattening them into one category.

  • Check the evidence before reaching a conclusion about intent.
  • Ask whether the expected action was possible under the actual conditions.
  • Identify who can change the conditions that repeatedly produce the same difficulty.
  • Set an owner and a way to check whether the response improved the work.

Fairness requires clear expectations and consistent decisions. It also requires care with language: “human error” can name an observation, but it does not explain why a system allowed the event or what will prevent a recurrence.

Close the loop

When workers contribute an account of the work, tell them what was learned, what will change, and what could not be changed yet. Check the result with them. Accountability becomes credible when the organization follows through on its own commitments as carefully as it examines individual actions.

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.). Accountability without reflexive blame. Jenkins Industry Safety Journal. https://www.toddjeromejenkins.com/articles/accountability-without-blame

“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 →