Building a Culture of Preparedness: What Actually Works

Most organizations have a plan. Fewer have a culture that uses it.

You can tell the difference in the first five minutes of an incident. In one organization, people pull up the plan, know their role, and start moving. In another, the plan exists in a binder or a shared drive somewhere, and the first ten minutes get burned figuring out who's supposed to do what. Same document. Very different outcomes.

The people who close that gap are the ones who make readiness a habit instead of an event: the emergency manager who runs the drill nobody asked for, the safety officer who updates the call tree in March instead of waiting for the annual review, the compliance lead who insists the after-action review produce a change and not just a PDF. Here's what that takes.

Who's in the room during a tabletop exercise

Preparedness programs stall when they're treated as a compliance checkbox handed down from the top. They take hold when leadership shows up to the exercises, asks about the plan in regular meetings, and treats readiness as part of running the organization.

The tell is who sits in the seat during a tabletop. If the exercise is staffed by a deputy and a note-taker while the people with signature authority are double-booked, staff read that accurately: this is a drill about the drill. When the decision-makers are actually in the room, the exercise surfaces the questions that matter in a real activation — who declares, who can spend, who talks to the press, who calls it off.

That participation also changes what gets funded. A program with a budget line gets software. A program with a seat at the table gets time on people's calendars, which is the scarcer resource.

A plan nobody's touched since the audit is already stale

Emergency managers who handle incidents well are running drills often enough that the plan feels familiar, and revising it after every exercise and every real event.

If your last three incidents didn't change anything in the plan, that's worth a hard look. Either you got lucky or nobody wrote down what they learned.

What does your last after-action review still show up in?

This is the part that gets skipped under time pressure. The after-action review (AAR) is where the learning actually lives, but only if it turns into a change someone can point at: a revised procedure, a different staffing model, a training module that didn't exist last quarter. An AAR that produces a report nobody reads didn't produce preparedness — it produced a file.

The distinction is easy to test. Pick the last incident you reviewed. Name the specific thing that is different now because of it. If you can't name one in under thirty seconds, the review was an archive entry.

Safety officers and compliance teams tend to feel this gap first, because they're the ones who inherit the findings and get asked, months later, whether anything happened to them. The organizations that get this right assign every AAR finding an owner and a date before the meeting ends.

Habits beat tooling, and friction beats both

Mass notification systems, dashboards, whatever your stack looks like — none of it replaces the habit of clear, frequent updates during an event. Teams that communicate well in a crisis are usually teams that already communicate well on a normal Tuesday. The tool should make that habit easier, not create it from scratch.

The flip side is friction. People default to whatever's easiest under pressure, so if reporting a hazard or pulling up a checklist takes ten steps, most people won't do either during an actual event. The strongest programs have cut their tools and processes down to the point where the safe action is also the fastest one.

Preparedness isn't one department's job

Business continuity, safety, IT, facilities, and frontline staff each see a different slice of the risk picture. When preparedness lives in one office, you end up planning for the risks that office knows about and missing the rest. IT knows which systems fail first. Facilities know which door doesn't lock. Nobody has the whole map.

Cross-functional involvement is slower to set up. It's also the only way the plan reflects the building people actually work in.

Start with the review you already ran

Every section above eventually funnels into one question: what did the last review actually change?

You don't need a new initiative to begin. Go back to your most recent after-action review and find one discovery that never turned into a change. Give it an owner and a due date this week. That's the difference between documenting preparedness and building it.