- WILDLAND FIRE? -

Introduction

Streamlining a complex process of coordination for wildland fire incident management teams.

The "E-IAP: Electronic Incident Action Plan" is a digital upgrade of the paper-based Incident Action Plan (or IAP) that incident management teams currently work 16 hours a day to create and distribute to firefighters on the field in large wildland fire incidents.

​

Watch the 3 minute concept video (planned, shot, and edited by me), and be immersed in the experience.

- FINAL MOCKUPS AND PROTOTYPES -

Final Design

A few screens from the final design and a little bit about how it works.

Interact with the main map screen to toggle on and off assets on the map, side screen opens for more information.

We addressed the connectivity issue with the screens on the left. To the right, capture an image to update the team.

Approve resources from your mobile device. Also, navigate to any personnel's last known location.

- WHAT IS THE PAPER? -

The Incident Action Plan (IAP)

The IAP contains critical information such as objectives, strategy, tactical actions, and supporting information for the current day. It includes incident objectives, organization assignment list, division assignments, radio communications plans, medical plan, traffic plan, safety plan, and the incident map.

- IMPORTANCE OF INNOVATION -

Why We Need A Change.

IAP is Labor Intensive

Creating the IAP every day is a highly manual and labor intensive process that takes 50+ people 16+ hours to make. The office and field teams collaborate face to face, sometimes traveling 2-3 times a day between the command post and the field for up to an hour each way for two weeks straight.

Rapidly Changing Situations

When situations change rapidly, the paper IAP makes it hard to stay accountable for individuals, have situational awareness outside of your line of sight, quickly moving personnel where they are needed most, logging, and accountability.

Static Paper Document

The IAP is a static paper document that lacks real time data and is impossible to update until the next day. However, situations change rapidly during the day and this leads to limited situational awareness, putting personnel and operations at risk and makes it hard to use resources effectively.

- HOW DID WE DO IT? -

Project Overview

- DISCOVER+DEFINE -

Research Timeline

Our team did a lot of exploratory and generative research into Wildland Fire to understand the complex problem space and human pain points within it.

- CREATE+TEST+ITERATE -

Design Timeline

We created 100 concepts and used co-design (down selection workshop) to down select to the Incident Action Plan (IAP) concept. We came up with the storyboard through our field trip to Batterman Rd. Fire experiencing a full day of the making of the IAP in person. We spent a few weeks creating prototypes to test and did two rounds of testing and iteration: one remote and another in the field at the Whitmore Fire. Then finalized the designs and created the video.

- 11 WEEKS TO LEARN -

The Research Phase

- WHO (WHAT WHY HOW) -

Our Stakeholders

In researching wildland fire communication, we needed to find and understand a great number of people and the positions they held to be able to create a viable product.

The Incident Command System (ICS)

Wildland Fire Incident Management Teams use the Incident Command System (ICS). We talked to people across the incident command system in order to get a holistic view of what information needed to be communicated during a wildland fire.

​

After research, we decided the most critical information that is the biggest factor in how quickly the fire gets put out is the communication between select groups at the incident command post and the people out on the field fighting the fire.

We focused on the Incident Commander, Incident Command Team, Operations Section, Planning Section, and Communications.

These are some of the people we've interviewed and built relationships with over time both over Zoom and in person at the Batterman Rd. Fire in Wanatchee and the Whitmore Fire in Nespelem.

- WHAT'S OUT THERE? -

Competitive Analysis

There were a lot of products that were trying to get off the ground, but never did that were specific to wildland fire. Things that were successful were for other applications like the military or police organizations.

- EDITORIAL STYLE RESEARCH PAPER -

Final Research Paper

I led my team in designing an editorial style 90+ page research paper in order to give my team additional training as designers.

- THE SHOW -

Final Research Presentation

Our final research presentation was highly anticipated and attended by 40+ people from Wildland Fire, companies like Axon, Launch Consulting that work in industries tangential to fire, and people from academia.

- 9 WEEKS TO CREATE+TEST+ITERATE -

The Design Phase

- CONCEPT GENERATION -

Ideation

Created 100+ initial concepts inspired by our research and design principles. We used methodologies like braiding, crazy eights, etc.

- NARROWING TO FINAL DESIGN -

Co-Design Group Stakeholder Workshop

We created and administered a two hour group co-design workshop in order to narrow to a final design through dot voting. After their selection, we wanted to understand why our stakeholders liked the design, the impact they think it would have, and the probablility of success.

Zoom call to compliment co-designing on Miro

Co-Design Workshop Agenda

1. Presented our concepts to our stakeholders

2. Asked them to dot vote and explain why

3. Best rated concepts had stories written about them from our stakeholder's perspective

4. Our stakeholders agreed that digitizing the Incident Action Plan and extending it would make the biggest difference in wildland firefighting today

Screen captures from our co-design workshop with some of our wildland fire stakeholders.

- THE E-IAP WAS BORN -

The Initial Idea

Our group imagined a GIS based platform that would span multiple devices like tablet, mobile, desktop, and mobile accessible by everyone on the fireline with leadership having access to update and make changes. Maps with personnel location data, weather, current fire line, and work assignment visualizations. With location tracking, features could streamline processes such as logistics, planning, logs, creating the IAP itself, and check-in.

Why Our Stakeholders Chose the IAP.

1. They liked the design because they could easily move and trade resources quickly throughout the day instead of waiting for the morning briefing to be more efficient in dynamic situations.

2. The impact would reach everyone in wildland fire connecting the incident management team to the people on the ground for more up to date situational awareness

3. They though it would have a high probability of success because there are already similar platforms out there for the military and they work in places with low connectivity. Wildland fire is also already looking to technology for efficiency and expanding capabilities because of resource shortages.

E-IAP Benefits

1. Accountability

2. Increased situational awareness on the fireline

3. Increased situational awareness for command post

4. Increased safety on the fireline

5. Increased awareness of overall operations 

6. Automating logs

7. Automating check-In

8. Automating logistics

9. Streamlining and visualizing operations

10. Streamlining the production of the IAP

11. Saves paper

12. Streamlines the documentation process

13. Makes meeting at a location easy

14. Ability to communicate visually on the map

- SETTING UP A TRIP TO A REAL FIRE -

IAP Field Research

After narrowing to the E-IAP concept, we wanted more in-depth knowledge on the IAP and how it is being used on the field to be able to improve on the current processes and understand it's current context. Luckily, my recruiting and conversations with incident commanders paid off, and I was able to gain enough trust to coordinate a spur of the moment field trip to our first real live fire. The fire at Batterman Rd. had mostly been put out and they were just working on clean up, so it was safe and the incident command team had plenty of time to answer our questions and show us everything we wanted to see.

A Long Day at the Batterman Rd. Fire with the NW12 Incident Command Team

5:40am - Arrive at Incident Command Post

6:00am - Experience Morning Briefing

7:00am - Firefighter Breakfast

8:00am - Incident Commanders' Meeting

9:00am - Meeting Public Information Officers

10:00am - Planning Section Meeting

11:00am - Meeting Communications

12:00pm - Firefighter Sack Lunch and Section Chiefs and Command Staff Meeting

2:00pm - Trip to the field to see Division Supervisor

4:00pm - Section Chiefs and Command Staff Meeting

5:00pm - Meeting with Resources Unit

6:00pm - Firefighter Dinner

7:00pm - Section Chiefs and Command Staff IAP Approvals

8:00pm - Planning Section finalizes IAP

9:30pm - Planning Section prints IAP

9:45pm - Depart

Going to the Batterman Rd. Fire gave us context for all our conversations with participants and grounded us in the reality of wildland fire incident management.

- WHAT WE LEARNED FROM BATTERMAN RD. -

Field Research Findings

By going to the fire, our team was able to experience and contextualize everything we learned in the previous 13 weeks which was critical in aligning the team in our knowledge base and grounded the team in reality.

- DREAMING OF A NEW PROCESS -

Concept Storyboard

After our field research at the Batterman Rd. Fire and having deep conversations with the NW12 Incident Management Team, we came up with compelling ideas ground in the reality of the current context of Wildland Fire.

​

See below for our storyboard which includes low fidelity mockups that use tablet, desktop, and mobile interfaces.

The E-IAP concept would give the incident management team more agency to make quicker decisions instead of going through the 24 hour process to plan each day.

- CLOSER LOOK -

Low Fidelity Mockups

Here's a few examples of some of the screens we made for our mockups for the storyboard.

- ALIGNING THE TEAM VISUALLY -

Branding Workshops

I created and facilitated the branding workshops for my team in order to align us on our visual system and basic product consistency. This created more efficiency by helping the team understand what visual styles were being imagined and produced many more viable solutions.

- DEFINING FLOWS AND FEATURES -

Information Architecture (IA)

In order to ensure the adoption and success of this product, we made sure everything in the paper IAP was in the E-IAP. Then, we expanded the IA to accommodate the features we explored with our stakeholders.

Homepage IA

General Menu IA

Map Navigation IA

- GETTING AROUND THE INTERFACE -

Navigation Iterations

Once we identified the key flows with the information architecture, we knew that we needed a usable and simple navigation to allow users to easily access and identify features.

Made several iterations of the main menu navigation including top and left nav, top nav only, and left nav only and a floating horizontla nav.

Downselected Navigation Frame

The team aligned on a floating vertical navigation due to the following reasons:

​

• Horizontal navigation was harder to reach and navigate to on a tablet

• Wanted to maximize the amount of space for the map on the screen since that was the primary way for users to visualize, receive, and distribute information. So instead of having a menu that took up the entire side, we opted for a minimal floating menu.

• Because of the specific needs of wildland fire management, menus with only icons did not provide enough affordances for what they were so added labels.

Observation of how people hold their iPads, one hand on each side.

- GETTING FEEDBACK FROM OUR STAKEHOLDERS -

Remote High Fidelity Usability Tests

I facilitated two remote, moderated prototype assessment/e