Emergency management doesn't need to work harder to prove we're busy. We need to get better at demonstrating what our work makes possible and what organizations stand to lose without it.
Emergency management professionals have spent decades advocating for preparedness. We encourage organizations to develop plans, conduct exercises, train personnel, identify vulnerabilities, and invest in mitigation before disasters occur. We know these activities matter, and we can usually explain why. Yet many programs continue to struggle for the funding, staffing, and organizational support necessary to build and sustain meaningful capabilities.
When those investments don't materialize, it's easy to conclude that leadership doesn't understand the importance of emergency management. Sometimes that may be true. But I think we need to ask ourselves a more uncomfortable question: Are we making the case for our work in a way that resonates with the people responsible for deciding where limited resources go?
We frequently describe our value through the activities we complete. We report how many plans we've developed, how many exercises we've conducted, how many employees we've trained, and how many people our preparedness campaigns have reached. These numbers demonstrate that work is happening, and they have a legitimate place in program management. But they don't necessarily tell leadership what that work accomplished, which risks were reduced, or what the organization can now do that it couldn't do before.
We know how to count what we do. We aren't always as good at measuring what changes because we did it.
And until we get better at making that connection, we're going to continue struggling to compete for resources against investments whose value is easier to explain.
We're Selling the Activity Instead of the Outcome
Consider a familiar accomplishment: an emergency management program delivers 30 training sessions to 500 employees over the course of a year. That's a substantial investment of time and effort, and it may represent important progress toward building organizational readiness.
But what does that number actually tell us?
It tells us how many training sessions occurred and how many people participated. It doesn't tell us whether those employees can perform their assigned responsibilities, whether a known capability gap has been addressed, or whether the organization is better positioned to manage a disruption.
Those questions are more difficult to answer, but they're also more meaningful.
Imagine instead being able to explain that an organization identified a weakness in its ability to coordinate incident priorities across departments. Through targeted training, procedural improvements, and exercises, the organization demonstrated measurable improvements in how quickly personnel could establish priorities, communicate decisions, and coordinate resources under the conditions evaluated.
Now we're having a different conversation. We're not simply reporting that training occurred. We're demonstrating that an identified organizational weakness was addressed and providing evidence of improved performance.
That doesn't make participation metrics irrelevant. We still need to understand whether programs are reaching the intended audience, whether required activities are being completed, and whether we're meeting established obligations. But those measures should be the beginning of our evaluation, not the end.
The same principle applies to plans, exercises, and other preparedness activities. Completing an emergency operations plan is an accomplishment. Demonstrating that personnel understand their responsibilities and can execute the processes within it is a capability. Conducting an exercise is an accomplishment. Identifying and correcting weaknesses that could otherwise complicate a real-world response is an outcome.
Capability is what organizations need.
Organizations aren't ultimately investing in the number of activities an emergency management program can complete. They're investing in the ability to manage risk, sustain essential functions, protect people, and navigate disruption.
Our responsibility is to make that value visible.
The Problem With Selling What Doesn't Happen
This becomes particularly challenging when we consider mitigation. After a disaster, the consequences are often painfully visible. We can document damaged infrastructure, interrupted services, displaced populations, recovery expenditures, and economic losses. The numbers may be staggering, but at least they give us something tangible to measure.
Before a disaster, we're trying to make the case for investments intended to prevent or reduce consequences that haven't occurred.
A community considering flood mitigation may face a significant upfront investment to reduce future damage. A utility evaluating infrastructure hardening may need to justify substantial expenditures against uncertain future events. An organization considering redundant systems or alternative operating arrangements must weigh immediate costs against disruptions that may never materialize during the useful life of those investments.
And when mitigation works, its value may be difficult to observe. Infrastructure that survives a storm doesn't produce a damage estimate. A facility that remains operational doesn't generate a recovery expenditure. A disruption that never occurs doesn't appear in an after-action report.
That creates a fundamental challenge for the way we communicate the value of risk reduction. We're often better equipped to describe what disasters cost than to demonstrate what effective mitigation and preparedness prevent. But there's an important distinction here. The cost of a disaster is not necessarily the cost of being unprepared. Even well-prepared organizations experience losses, and not every consequence can reasonably be prevented. The value of mitigation lies in the portion of those consequences that an investment can credibly be expected to reduce or avoid.
Making that case requires more than describing a worst-case scenario. It requires examining exposure, likelihood, potential consequences, available interventions, and the expected difference between acting and doing nothing. It also requires acknowledging uncertainty and recognizing that not every mitigation investment will be justified by its projected benefits.
These are familiar concepts in risk analysis and benefit-cost evaluation. Yet they aren't always capabilities embedded within emergency management programs, particularly those operating with limited personnel and resources. And I think that deserves more attention.
We Need More Than Better Storytelling
Emergency managers are often encouraged to become better communicators, build stronger relationships with executives, and learn to speak the language of organizational leadership. I agree with that advice, but I don't think it goes far enough.
A compelling story can help leadership understand why a risk matters. It cannot substitute for credible evidence about the scale of that risk, the effectiveness of a proposed intervention, or the consequences of choosing not to act. We need to become better at producing that evidence, and that means recognizing that the skills required to manage emergency management programs aren't necessarily the same skills required to quantify their organizational value.
To do that effectively, we need people on our teams or at least in our corners who understand statistical analysis, financial modeling, risk assessment, economics, and program evaluation. People who can help us establish meaningful baselines, examine historical losses, evaluate competing mitigation strategies, and estimate how investments may change an organization's exposure over time.
I'm not suggesting that every emergency manager needs to become an economist or that quantitative analysts should replace experienced practitioners. Emergency management requires operational judgment, relationships, coordination, and an understanding of how organizations and communities function under pressure. Those capabilities remain essential. But why wouldn't we want people with strong analytical skills working alongside us?
We recognize the value of multidisciplinary teams when responding to emergencies. We bring together technical specialists, operational leaders, public information professionals, logistics personnel, and representatives from organizations whose expertise is necessary to manage complex incidents.
We should be equally intentional about the expertise we bring together when we're trying to understand and reduce risk before those incidents occur. That expertise may already exist within an organization. Finance, engineering, enterprise risk management, business intelligence, and other functions may have analytical capabilities that emergency management programs can draw upon. Building these relationships may be a more realistic starting point than adding dedicated positions, particularly for smaller programs.
The point I’m making isn't that every emergency management office needs its own statistician. It's that the profession needs more consistent access to the expertise required to translate operational knowledge into credible, decision-useful analysis. And that expertise should help us do more than justify the investments we already want to make. It should help us determine which investments are most likely to produce meaningful improvements in the first place.
The Funding Paradox
Of course, there's an obvious problem with this argument. Building stronger analytical capabilities requires resources, and resources are precisely what many emergency management programs are struggling to secure. We need better evidence to justify investment, but producing better evidence may require investments in people, systems, and expertise that we don't currently have.
It's a chicken-and-egg problem. And I don't think we have the luxury of waiting for someone else to solve it. We have to begin working our way out of that cycle with the resources and relationships already available to us. That might mean partnering with an existing finance or risk management team to evaluate a proposed mitigation project. It might mean establishing baseline performance measures before implementing a new training program, rather than attempting to reconstruct them afterward. It might mean working with operational departments to identify the consequences of delayed decisions, interrupted functions, or unavailable resources.
It could also mean being more selective about what we measure. Instead of reporting only how many employees completed training, we could evaluate whether they can perform the critical tasks the training was intended to support. Instead of reporting only how many exercises were conducted, we could track whether identified capability gaps were addressed and subsequently retested. Instead of presenting mitigation as an inherently worthwhile investment, we could work with technical experts to compare the expected consequences of different options.
None of these approaches will produce perfect data. Emergency management deals with uncertainty, complex systems, and events that may have limited historical precedent. Quantitative analysis can create a false sense of precision when assumptions are weak or important consequences are excluded. But imperfect evidence, transparently developed and appropriately qualified, can still improve decision-making.
We obviously do not need to and should not turn every preparedness decision into a financial equation. Life safety, public trust, legal obligations, and community well-being matter even when their value cannot be reduced to dollars. A responsible analysis should recognize those considerations rather than exclude them simply because they’re difficult to quantify. The objective ultimately is to provide a clearer understanding of what is at stake, what an investment can reasonably accomplish, and what risks remain.
The Case We Should Be Making
Emergency management programs don't operate in a vacuum. They compete for resources with infrastructure improvements, technology investments, workforce needs, operational initiatives, and countless other priorities. Many of those competing proposals come with financial projections, performance measures, and evidence intended to demonstrate their organizational value.
We shouldn't be surprised when generalized appeals for preparedness struggle to compete. That doesn't mean every emergency management recommendation should be funded, or that leadership is wrong when it chooses to accept a particular risk. Organizations have finite resources, and responsible decision-making requires evaluating competing needs. Our role is to help ensure those decisions are informed by a credible understanding of the consequences. That means moving beyond explaining why preparedness is important and becoming more effective at demonstrating what it accomplishes.
What is the organization exposed to today? Which capabilities are necessary to manage that exposure? Where are the gaps? What would it cost to address them, and what consequences could reasonably be prevented or reduced? How will we know whether the investment worked?
Those are the questions that connect emergency management to organizational risk, performance, and investment decisions.
They also challenge us to look critically at our own programs. If we're going to ask leadership to evaluate preparedness based on outcomes rather than activities, we need to be willing to do the same. We may discover that some long-standing practices produce less value than we assumed, while relatively modest changes create meaningful improvements. Better measurement should help us identify both.
I don't believe emergency management needs to reinvent itself to become valuable. The work we do already addresses risks and consequences that matter deeply to the organizations and communities we serve. But recognizing that value within our profession is not the same as demonstrating it to the people making investment decisions.
We need to get better at connecting what we do to what changes because we did it. We need stronger analytical partnerships, more meaningful performance measures, and greater confidence in explaining the consequences our work is intended to prevent or reduce.
