Safety Management Basics: A Beginner’s Primer on the Pre-Mortem

If you are new to safety management in aviation, you will meet a lot of vocabulary quickly: hazards, risks, mitigations, reporting, review. A pre-mortem is one of the simplest tools you can add to that kit, and it needs no software or special training. In a pre-mortem you imagine a project or change has already gone wrong, then list the reasons. It brings hazards to the surface before anybody is exposed to them. This primer explains the idea for beginners and ends with a mini-glossary. It is general education only; your organisation’s safety manual, regulator requirements and accountable staff define how safety management is actually done.

Why beginners should care

Safety management is about noticing trouble early. Most people assume that means reacting to incidents and reports. That is part of it, but a mature approach also looks ahead, asking what could go wrong with the thing we are about to start. A pre-mortem is a structured, friendly way to do exactly that, and because it takes minutes, it fits into ordinary planning meetings.

The core idea in plain terms

Teams usually plan with a hopeful mindset. They describe the goal, the steps and the schedule. A pre-mortem flips the mood. You say, “It is some time from now, and this change caused a problem. What happened?” The shift matters because people find it easier to explain an event that is treated as fact than to predict one that is merely possible. Even quiet team members tend to speak up, since nobody is criticising the plan; they are describing a story.

When to use it

  • Before introducing a new procedure, form or checklist.
  • Before changing a schedule, shift pattern or training routine.
  • Before a new piece of equipment or software enters regular use.
  • Before a large event, such as a visit, an audit or a busy operating period.

It is not designed for an emergency or an urgent incident. Those follow established procedures, not brainstorming.

A beginner-friendly format in five steps

  1. Define the change. One sentence is enough: “We are changing how shift notes are passed between teams.”
  2. Imagine the failure. Tell the group the change has gone badly.
  3. Write silently. Everyone lists causes on their own for a few minutes.
  4. Share and cluster. Read everything out, then group similar items.
  5. Choose follow-ups. Pick the most worrying items and agree who will look into each, then pass anything formal to the people responsible for the safety process.

A worked example, kept deliberately simple

Imagine a small organisation switching from paper notes to a shared digital sheet for communicating between shifts. In the pre-mortem, staff might write: “Someone could not log in and missed a note.” “Two people edited at once and one change was lost.” “Old paper habits continued, so information lived in two places.” “Nobody knew who checked the sheet at the start of each shift.” “Older staff were not shown how to use it.”

Notice these are about people, habits and roles, not technology. That is typical. The follow-ups, such as a trial period, a named person to check the sheet and a short training session, are small and sensible. They also feed naturally into the formal hazard process: the notes become candidates for the organisation’s own hazard log if the accountable team decides they belong there.

Questions that make the exercise richer

If the group runs dry, prompt it with a few open questions. Who might be affected that we have not mentioned? What would we need to know on day one that we only learn on day thirty? Which part of this relies on somebody remembering something? What would a new starter misunderstand? Which step could be skipped when people are rushed, and what would happen then? These prompts steer people toward the human and organisational angles that formal checklists tend to miss, and they keep the discussion practical rather than abstract.

What it adds to a safety system, and what it does not

A pre-mortem complements proactive hazard identification by capturing worries while a plan is still flexible. It does not replace reporting systems, risk assessment methods, audits or the judgement of qualified personnel. Think of it as a spark: it raises candidates, and the organisation’s formal process decides what to do with them.

A look across the fence

Aviation is not alone in valuing early warning. In software, a whole field is dedicated to protecting the automated pipelines that build and ship products. the DevSecOps community writes about it at DevSecOps Now, a blog largely about securing CI/CD pipelines, and browsing it is a quick way for a curious beginner to see another industry applying the habit of anticipating failure at every stage.

Mini-glossary for beginners

  • Hazard: something with the potential to cause harm or disruption.
  • Risk: how likely a hazard is to cause trouble combined with how serious the result would be.
  • Mitigation: an action that lowers a risk, either by making it less likely or less damaging.
  • Safety culture: the shared attitudes and habits that decide whether people raise concerns freely.
  • Proactive: acting on potential problems before they cause an event.
  • Reactive: responding after something has happened.
  • Pre-mortem: an exercise imagining a plan has failed in order to list reasons beforehand.
  • Follow-up: a named action with a named person and a review point.

Common beginner mistakes

  • Treating the list as a final verdict. It is a set of questions to investigate, not proven facts.
  • Letting the most senior person speak first. That shapes everyone else’s answers.
  • Writing vague items. “Poor communication” is hard to act on; “night staff do not see the morning note” is not.
  • Forgetting the follow-up. A list without owners is just a conversation.
  • Using it to override procedure. The official process always stays in charge.

Getting started this week

Pick one small change on your calendar and schedule a fifteen-minute pre-mortem for it. Invite the people who will be affected, not just those who designed it. Keep the notes, pass relevant items to whoever manages your formal safety process, and look again after the change has settled. That single repetition will teach you more than any definition, and over a few cycles you will find that asking “how could this fail?” becomes a natural reflex rather than a meeting.

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top