**What Should We Call What We Do?**

**Disaster Management**

**Dr. James Porto**

**8^th^ Annual Emergency Management Higher Education Conference**

**National Emergency Training Center**

**Emmitsburg, Maryland**

**June 7-9, 2005**

The first thing I would like to say is I do know how to spell
Emmitsburg, my spell checker doesn't though and I didn't catch the
misspelling quick enough. I sent Barbara an updated version but it never
got to you. Apparently my spell checker always replaces the "i" with an
"e" for some reason.

I have a PDF diagram that I would like to show you. I will use this
since I have only 7 minutes.

The issue I want to address first is why do we want to standardize on a
name? I think there are two good reasons. One, it is going to help us
focus our identity as a profession and, someday, as a recognizable
discipline. A second reason is if we standardize on a name and offered
academic degrees in a commonly called profession, then we get
consistency plus we improve the chances of developing an accreditation
process for the degree itself, so the degree becomes a known quantity to
our market.

We need to be thinking about markets at some point as educators because
we cannot produce graduates with degrees if they have no jobs. We need,
therefore, to think about professionalizing what we offer, to make it
like an MBA that is well recognized throughout the country. I have come
to believe that "disaster management" is the name of what we do and
therefore we should call what we do "disaster management."

First, let's decide the easy part of our name---management. Seven of the
eight entries had "management" in it, so seven out eight of the entries
feel that what we do is involved with management, which is the direction
and coordination of persons and things. So I am going to support
"management" in our name because I think what we do is manage.

The tough question is what comes in front of management? What do we
manage? I think we need to look at a framework that describes what we
actually do before we can say what we do. The day before yesterday I
offered the idea of a cost driver model for disaster management and the
reason why I have come up with that framework is that disasters are
defined by our costs. If there were no costs to us, there would be no
disasters. It is as simple as that. What we are about is to minimize
disaster costs for the things we have control over. So we have to
understand what drives these costs and what control we have over cost
drivers. I submit to you that there are four sets of conditions that
drive the costs for disasters.

One is the nature of the hazard itself; one is our vulnerability, both
built up structures and our social, political, and psychological
vulnerabilities. The third is the ability to detect disasters, events or
threats, and the fourth is our ability to respond and to recover. If we
can optimize on all four sets of conditions, we can minimize our costs.

If you look at each one of the names proposed, none of them except
"disaster management" encompasses all four conditions in the cost driver
model. Anything with the word "vulnerability" in it is limited to costs
driven by the vulnerability condition of cost drivers. Anything with the
term "hazard" in it is limited to the nature of the hazard. I also have
a problem with the idea of managing a hazard. We do not manage hazards;
we can't manage hazards. We don't have the technology to do that. In
fact, we don't even manage the risks of hazards. If you use the word
frequency as a substitute for the word risk, you get a close idea of how
difficult it is to manage risk. We do not manage the frequency of
hazards. What we manage though is the frequency of high cost events to
us as humans, so I therefore submit to you that "disaster management" is
what we do.

This also applies, not only to what I've called the service component of
what we do, but to the combat component of what we do\-- the military
and the police. I think the cost driver model fits very well with the
military complex as well. I have been reading an interesting book,
called "Military Misfortune" by Cohen and Gooch that reviews disasters
and failures within the military context. They are making a strong case
for using disaster studies and disaster management studies to apply to
military failures as well. One of the tasks we must undertake over the
next 2 to 3 years is to integrate both the service and combat elements
into a unified profession within a framework that allows us to
communicate with each other to achieve our mission.

For both, the military component as well as the service component, key
objectives are to minimize costs and loss of life and property. In the
military we want to win our battles without losing a single life. In a
hurricane or storm, we do not want to lose a single life. These are
objectives I think we can agree upon. Therefore I am suggesting that the
name that we chose should reflect what we do and what we do, I think, is
attempt to manage the effects of disasters and therefore what we do
should be called "disaster management."

Finally, I would like to urge you to vote for disaster management. Many
years ago I was involved in politics. I was Mayor of my little town and
I realized if you don't ask for the vote you won't get it. I am asking
you to vote for "disaster management."