Home Social Sciences Pre-Disaster Established Trust and Relationships: Two Major Factors Influencing the Effectiveness of Implementing the ICS
Article
Licensed
Unlicensed Requires Authentication

Pre-Disaster Established Trust and Relationships: Two Major Factors Influencing the Effectiveness of Implementing the ICS

  • Ray Chang EMAIL logo and Joseph Trainor
Published/Copyright: September 21, 2018

Abstract

Since the establishment of the Incident Command System (ICS), many discussions have centered on its design, using the failure or success of disaster response to evaluate the effectiveness of this system. However, even prior to implementation, there are certain pre-conditions that must be first satisfied by responders. Two major factors underlying these pre-conditions, that strongly influence the eventual design and consequent functioning of the ICS, are pre-disaster established trust and relationships. This research utilizes qualitative methods to explore the importance of pre-disaster established trust and relationships in the implementation of the ICS. Twenty-eight in-depth qualitative interviews were completed and analyzed. From looking at how ICS users make a variety of different decisions regarding the establishment of the incident command, the setting up of overall response goals and objectives, the implementation of the Incident Action Plan, the selection of new ICS leaders, and the working arrangements made with volunteers, it can be observed that relationship and trust are two very important factors that dictate the successful implementation of the ICS. Based on this analysis, three conclusions could be drawn in this research: (1) any thorough evaluation of the ICS should also include an analysis of any existing pre-conditions, (2) future ICS training should cover strategies to build relationships and trust between response organizations, and (3) additional research should be conducted to understand other factors that influence the implementation of the ICS at scene of disaster.

Appendix A

Qualitative Interview Questions

  1. (This question is only for the interviewees who served as IC on the selected disaster) to get started I want to ask you about XYZ event. I want to know during that event were you the sole Incident Commander (IC) or were you part of a Unified Command (UC) team? How that decision was made? (this interview question is to understand how people determine using a single IC or UC, which is the first decision point)

    1. What were the driving factors that led to this? Did you ever consider doing the alternative set up? Why or why not?

    2. Same or different from other events

    3. What were the processes for making that decision at the scene?

    4. Would you please give me an example showing how you make decisions under the UC structure? (this question is aimed to understand how people cooperate in the UC, which is the second decision point)

  2. How do you decide when to or not to activate branch, division, team, group, and etc. What are your criteria for deciding you actually need to use these structures? (this question is aimed to understand how do people create new ICS branches, which is the third decision point)

    1. The ICS mentions if personnel or resources exceed a manageable span of control, ICS leaders have to create new branches. What is a manageable span of control? How can you determine it? (this question is aimed to understand how do ICS leaders determine ICS span of control, which is the eighth decision point)

    2. Once you establish a new ICS branch, how do you decide who should lead it?

      1. Do you consider people out of your organization?

      2. What skills do you look for serving as a leader in that new ICS branch?

      3. What are most important traits to select new ICS leaders?

    3. From you experience, this leader is selected from the original ICS hierarchy (promoted people from lower ICS positions) or outside communities (hired people from other groups that were not within the ICS structure)?

  3. Can you explain to me how Incident Action Plan (IAP) works (this question is aimed to understand do ICS leaders change the IAP during disasters, which is the fifth decision point)

    1. Based on your experience, do you change the IAP?

    2. If you do, can you explain the reasons of changing the IAP?

    3. If you do not, how do you deal with those situations that are not expected before disasters? (this question is aimed to understand how do ICS leaders allocate responsibility to resolve unexpected problems, which is the fourth decision point)

  4. Based on your experience, do you think ICS users improvise at the scene? (this question is aimed to understand do ICS users in response to disastrous situations, which is the seventh decision point)

    1. If they do, can you give me an example of improvisation?

    2. If they do not, how do they deal with those situations that are not expected before disasters?

  5. On the selected disaster, did you work with people from different organizations or backgrounds, such as the deputies or technicians? (this question is aimed to understand how do ICS leaders work with people from different organizations and backgrounds, which is the sixth decision point)

    1. If you did, did you give instructions to them or work with them on making decisions?

    2. Would you please give me an example of the above situation (instruct them or make decisions with them)?

Appendix B

List of Twenty-Eight Interviews

ICS RoleRepresenting GroupDisaster Name/Type
1General and Command StaffEmergency Management Office2013 CO Flood/ Type 3
2ICS userNYPD/Incident Management TeamHurricane Sandy/Type 3
3Operation Division ChiefVolunteer and later become a federal contractorWaynesville, Missouri flooding/Type 3
4Operation Division ChiefFEMAHurricane Irene/ Type 2
5Incident Command/Operation Division ChiefEmergency Management OfficeImperial sugar refinery explosion 2008 (Georgia)/Type 3
6Command Staff/Liaison OfficerSouthwest Incident Management Team2013 CO Flood/ Type 3
7Safety OfficerFEMA9/11 Ground Zero US&R Operation
8Planning Section ChiefEmergency Medical Technician2012 Ohio Tornadoes/ Type 3
9Federal Coordination OfficerFEMA2014 Mississippi Tornados/ Type 2
10UC member (the Federal Coordination officer)FEMATornados and floods/ Type 2
11Incident CommanderSouthwest Incident Management Team2013 CO Flood/ Type 3
12EMS Branch LeaderContra Costa County2013 Asiana Air Crash
13Incident CommanderDirector of Butler CountyHurricane Sandy
Emergency Management Agency
14IC for EOC Operation Support ChiefSan Francisco EOC2013 Asiana Airplane crash
15Incident CommanderForest Service- Fire & Aviation managementNo Specific disastrous case
16Incident CommanderIncident Command TeamNo Specific disastrous case
17Incident CommanderPublic Works1996 Floods in Portland
18Incident CommanderPark ServicesNo Specific disastrous case
19Incident CommanderSalvation ArmyNo Specific disastrous case
20Incident CommanderFire DepartmentTrain Crush in Washington State
21Operation Division ChiefFDNYHurricane Katrina
22Incident CommanderWashington State Forest ServiceMany Type 2 and Type 3 Wildfires
23Operation Section ChiefNational Park ServiceHurricane Irene
24Incident CommanderDepartment of Nature ResourceType 2 and type 3 disasters; no specific one
25Incident CommanderLA County Fire DepartmentType 3
26Deputy Planning Section ChiefLA Department of Forestry SafetyWild land Fires in California
27Incident CommanderA city fire department in SF bay areaWild land fires in California
28Incident CommanderOrange County Fire DepartmentType 2 and Type 3 wild land fires

References

Bigley, G., and K. Roberts. 2001. “The Incident Command System: High-reliability Organizing for Complex and Volatile Task Environments.” The Academy of Management Journal 44: 1281–1299.10.2307/3069401Search in Google Scholar

Buck, D., J. Trainor, and B. Aguirre. 2006. “A Critical Evaluation of the Incident Command System and NIMS.” Journal of Homeland Security and Emergency Management 3 (3): 1–27.10.2202/1547-7355.1252Search in Google Scholar

Burns, T., and G. M. Stalker. 1972. “Mechanistic and Organic Structure.” In Organizational Systems, edited by K. Azumi and J. Hage, 240–255. USA: DC Heath and Company.Search in Google Scholar

Daft, R. 2009. Organization Theory and Design. OH, USA: South-Western Cengage Learning.Search in Google Scholar

Emergency Management Institute (EMI). 2013. IS-100.b: Introduction to Incident Command System, ICS-100. Retrieved 12/07, 2013, from http://training.fema.gov/EMIWeb/IS/courseOverview.aspx?code=IS-100.b.Search in Google Scholar

Emergency Management Institute (EMI). 2013. IS-100.HE: Introduction to the incident command system for higher education. Retrieved from http://training.fema.gov/EMIWeb/IS/courseOverview.aspx?code=IS-100.HE.Search in Google Scholar

Federal Emergency Management Agency (FEMA). 2006. ICS-400: Advanced ICS for command and general staff, complex incidents and MACS for operational first responders (student manual). Retrieved from http://www.nctcog.org/ep/training/ICS_400_Student_Manual.pdf.Search in Google Scholar

Federal Emergency Management Agency (FEMA). 2008. ICS Review Document. Retrieved 12/18, 2012, from http://www.training.fema.gov/EMIWeb/IS/ICSResource/assets/reviewMaterials.pdf.Search in Google Scholar

Hansen, R. 2006. “Letter to the Editor Regarding Incident Command System (ICS).” Journal of Homeland Security and Emergency Management 3 (4): 1–3.10.2202/1547-7355.1289Search in Google Scholar

Harrald, J. 2006. “Agility and Discipline: Critical Success Factors for Disaster Response.” The ANNALS of the American Academy of Political and Social Science 604: 256–272.10.1177/0002716205285404Search in Google Scholar

Hesse-Biber, S. N., and P. Leavy. 2011. The Practice of Qualitative Research. 2nd ed. CA, USA: SAGE Publications.Search in Google Scholar

Hsieh, H., and S. Shannon. 2005. “Three Approaches to Qualitative Content Analysis.” Qualitative Health Research 15: 1277–1288.10.1177/1049732305276687Search in Google Scholar

Jensen, J., and W. Waugh. 2014. “The United State’s Experience with the Incident Command System: What We Think We Know and What We Need to Know More About.” Journal of Contingencies and Crisis Management 22: 5–17.10.1111/1468-5973.12034Search in Google Scholar

Kitao, S. K., and K. Kitao. 2002. Approaches to Social Science Research: Communication and Language Teaching/Learning. Japan: EICHOSHA.Search in Google Scholar

Klein, G. 1999. Source of Power. How People Make Decisions. Cambridge, MA, USA: The MIT Press, 236–238.Search in Google Scholar

Merriam, S. 2009. Qualitative Research: A Guide to Design and Implementation. 2nd ed. USA: Jossey-Bass.Search in Google Scholar

Moynihan, D. 2007. From Forest Fires to Hurricane Katrina: Case studies of incident command system. IBM Center for The Business of Government.Search in Google Scholar

Neal, D., and B. Phillips, 1995. “Effective Emergency Management: Reconsidering the Bureaucratic Approach.” Disasters 19 (4): 327–337.10.1111/j.1467-7717.1995.tb00353.xSearch in Google Scholar

Neal, D., and G. Webb. 2006. “Structural Barriers to using the National Incident Management System.” In Learning from Catastrophe: Quick Response Research in the Wake of Hurricane Katrina, 263–282. Boulder, Colorado: Institute of Behavioral Science, University of Colorado at Boulder.Search in Google Scholar

Quarantelli, E. L. 2002. In Here is a Statement about the Incident Command System, edited by Dr. Oleary. Newark, DE: University of Delaware, Disaster Research Center.Search in Google Scholar

Rubin, H., and I. Rubin. 2005. Qualitative Interviewing: The Art of Hearing Data. 2nd ed. CA, USA: Sage Publications.10.4135/9781452226651Search in Google Scholar

Sylves, R. 2008. Disaster Policy and Politics. Washington, DC: CQ Press.Search in Google Scholar

Wenger, D., E. L. Quarantelli, and R. Dynes. 1990. “Is the Incident Command System a Plan for all Seasons and Emergency Situations?” Hazard Monthly 10: 8–12.Search in Google Scholar

Published Online: 2018-09-21

©2018 Walter de Gruyter GmbH, Berlin/Boston

Downloaded on 13.3.2026 from https://www.degruyterbrill.com/document/doi/10.1515/jhsem-2017-0050/html
Scroll to top button