Damkar Graphic
Damkar Graphic
Damkar Graphic
Damkar Graphic

DAMKAR

DAMKAR

A real-time, mission-critical dashboard for emergency response—a SaaS-style tool designed for Seattle's Fire Department.

ROLE

UX Design

UX Research

ROLE

UX Design

UX Research

TEAM

Working with 1 Designer and

and 3 Developers

TEAM

Working with 1 Designer and

and 3 Developers

TIMELINE

24 hours design competition


TIMELINE

24 hours design competition


View Prototype

View Prototype

View Prototype

An Urgent Need

An Urgent Need

+5%

+5%

increase of emergency response


In 2023, the Seattle Fire Department responded to over 110,000 emergencies—a 5% increase from the previous year. Rising incidents like vacant building fires and cardiac arrests have pushed the department to its limits.


This raises the need for a centralized system that supports faster decision-making and better coordination—Which the current systems lacks.

increase of emergency response


In 2023, the Seattle Fire Department responded to over 110,000 emergencies—a 5% increase from the previous year. Rising incidents like vacant building fires and cardiac arrests have pushed the department to its limits.


This raises the need for a centralized system that supports faster decision-making and better coordination—Which the current systems lacks.

The Challenge

The Challenge

Given the 1-day challenge's tight deadlines and resource constraints, there wasn’t enough time for extensive user research like surveys or interviews. To overcome this, we utilized quick user feedback loops and leveraged available data to ensure the design met core user needs effectively.

Given the 1-day challenge's tight deadlines and resource constraints, there wasn’t enough time for extensive user research like surveys or interviews. To overcome this, we utilized quick user feedback loops and leveraged available data to ensure the design met core user needs effectively.

The Problem

The Problem

Damkar Graphic
Damkar Graphic
Damkar Graphic

After conducting our analysis, we found that while volume of calls and responses has been rising by up to 54%, the processing time are declining. Why?

After conducting our analysis, we found that while volume of calls and responses has been rising by up to 54%, the processing time are declining. Why?

After conducting our analysis, we found that while volume of calls and responses has been rising by up to 54%, the processing time are declining. Why?

The answers was surfaced from an evaluation of 911 Dispatch Operators that shows inefficiencies in their workflow. We found 3 pain points.

The answers was surfaced from an evaluation of 911 Dispatch Operators that shows inefficiencies in their workflow. We found 3 pain points.

The answers was surfaced from an evaluation of 911 Dispatch Operators that shows inefficiencies in their workflow. We found 3 pain points.

Pain Points

Pain Points

!

Inefficient Rapid Response Data Utilization

Inefficient Rapid Response Data Utilization

Table
Table

Inadequate capabilities to analyze historical incident data and extract actionable insights

Inadequate capabilities to analyze historical incident data and extract actionable insights

Inadequate capabilities to analyze historical incident data and extract actionable insights

!

Delayed Incident Response

Delayed Incident Response

Government data
Government data

2019 Seattle’s Fire Department CAD System

Weak visual hierarchy and cluttered interface

Low contrast UI

Navigation tabs are very small and lacks flow

Dropdown menu can slows down responses

Dropdown menu slows down responses

See How We Improve This

See How We Improve This

Current Systems clustered design limits agents ability to efficiently navigate to other pages in response to rapid inputs, as well as having to input too many information at once.

Current Systems clustered design limits agents ability to efficiently navigate to other pages in response to rapid inputs, as well as having to input too many information at once.

Current Systems clustered design limits agents ability to efficiently navigate to other pages in response to rapid inputs, as well as having to input too many information at once.

!

Disconnected Communications

Disconnected Communications

Graphic of 911 cases
Graphic of 911 cases

Overlapping case information from different calls

Overlapping case information from different calls

Objective

Objective

Objective

“Design a system that prioritize time efficiency, simplify process, and enhance emergency response systems”

“Design a system that prioritize time efficiency, simplify process, and enhance emergency response systems”

05

Case finished. Report generated

05

Case finished. Report generated

05

Case finished. Report generated

01

911 operators

receives distress call

01

911 operators

receives distress call

01

911 operators

receives distress call

02

Operators begin asking. Where? What? Anything Else?

02

Operators begin asking. Where? What? Anything Else?

02

Operators begin asking. Where? What? Anything Else?

Reduce process

03

Data entry in CAD begins as call is ongoing

Reduce process

03

Data entry in CAD begins as call is ongoing

Reduce process

03

Data entry in CAD begins as call is ongoing

Reduce process

04

Resources are allocated and department alerted

Reduce process

04

Resources are allocated and department alerted

Reduce process

04

Resources are allocated and department alerted

Needs and Priorities

Needs and Priorities

After gathering enough data, we divided the tasks / needs using the prioritization matrix to help determine different how importance the tasks and its impact on the system.

After gathering enough data, we divided the tasks / needs using the prioritization matrix to help determine different how importance the tasks and its impact on the system.

Effort vs Impact Diagram
Effort vs Impact Diagram
Effort vs Impact Diagram
Effort vs Impact Diagram

Solutions

Solutions

Sketches and Wireframes

Sketches and Wireframes

Sketches and Wireframes

Whiteboards
Whiteboards
Whiteboards
Whiteboards

Since this is a 1 day in a half project, we didn’t have the time to document all the design process, but we do all the ideations and sketches on this whiteboard

Since this is a 1 day in a half project, we didn’t have the time to document all the design process, but we do all the ideations and sketches on this whiteboard

Initial Navigation

Initial Navigation

Menu 1

Menu 2

Menu 3

Menu 4

Real Time Screen

Initial Concept

Using arrows for keybinds to move between pages


Initial Concept

Using arrows for keybinds to move between pages


Navigation

Navigation

Navigation

Final Concept;

*ctrl + tab to move between pages

*Arrows for move between data entry fields


Final Concept;

*ctrl + tab to move between pages

*Arrows for move between data entry fields


Key Features

Key Features

Prompt Generator AI

Prompt Generator AI

AI pictures

Aid Operator Experience with Historical,

Data-Driven Questions

Aid Operator Experience with Historical,

Data-Driven Questions

Case Summary

Case Summary
Case Summary

Comprehensive Summary for Resource management

Resource Allocation

map
map
map
map

Operations and inputs run in the background with real-time active fire stations and weather information

Operations and inputs run in the background with real-time active fire stations and weather information

Interactive Map

map
map
map
map

Color coded proximity, interactive pop-up menu, and road cctv cameras showing to route operational departments.

Color coded proximity, interactive pop-up menu, and road cctv cameras showing to route operational departments.

What I Learned

What I Learned

This was my first design sprint—and the perfect crash course in fast, collaborative problem-solving.

This was my first design sprint—and the perfect crash course in fast, collaborative problem-solving.

In the rush of a 24-hour challenge, I leaned heavily on heuristics and existing patterns, skipping user testing in favor of speed. In hindsight, I saw how even the simplest feedback loop could have grounded the design in real context.

In the rush of a 24-hour challenge, I leaned heavily on heuristics and existing patterns, skipping user testing in favor of speed. In hindsight, I saw how even the simplest feedback loop could have grounded the design in real context.

I also learned the cost of skipping structure. Without defined deliverables or a shared north star, the process felt more reactive than intentional. Since then, I’ve learned to anchor sprints with clear goals, time-boxed checkpoints, and moments for reflection.

I also learned the cost of skipping structure. Without defined deliverables or a shared north star, the process felt more reactive than intentional. Since then, I’ve learned to anchor sprints with clear goals, time-boxed checkpoints, and moments for reflection.

If you're curious on how I approach design sprints now, check out my FigBuild project—where I brought structure, used AI meaningfully, and prioritized validation from the start.

If you're curious on how I approach design sprints now, check out my FigBuild project—where I brought structure, used AI meaningfully, and prioritized validation from the start.

Next project Adobe Venn

Copyright © 2020 Enrico Soputra. All rights reserved.
Copyright © 2020 Enrico Soputra. All rights reserved.
Copyright © 2020 Enrico Soputra. All rights reserved.
Copyright © 2020 Enrico Soputra. All rights reserved.