Read Time: 30 sec
Summer 2024
SaaS
Turning fragmented emergency operations into a connected system—designed a unified dashboard for SFD
Context
Response 360 was designed for the Dubstack Protothon 2024 Enterprise track to address a critical gap: the lack of a unified platform for first responders to efficiently track and manage operations.
This was an ambitious and ambiguous challenge that I took on solo; designing the entire end-to-end experience in just 2 days.
I conducted domain research, explored dashboard patterns, and did a lo-oot of iterations to reach here. I’m genuinely proud of how much I was able to accomplish under such a tight timeline.
TOOLS
Figma, Qualtrics
TAGS
Desktop • EMS • SaaS
DURATION
2 days, Summer 2024
COLLABORATORS
→ TL;DR
PROBLEM
Fire Department lacked a centralized tool to manage in real time → leading to delays during critical moments
SOLUTION
A unified emergency management system to improve overall response time and communication
IMPACT
CES score of 5.7/7 reflecting ease flow
Potential impact I'd like to track
Response time per incident before and after adoption
Time saved in resource dispatch decisions
Team confidence in incident visibility and coordination
MY CONTRIBUTION
As a solo designer, I designed Response 360 in under 48 hours
Conducted interviews, studied articles, videos and current solution efforts
Facilitated surveys before submission for feedback
→ Bridging the solution to the problem
BRIDGING
Department needed a unified system to improve communication and resource allocation
→ Design process
CONTEXT
Where the current system falls short
The SFD struggles with inefficiencies which stem from the absence of a unified digital platform to streamline operations.
Issues the current system at Seattle Fire Department faces
DEFINING
Zooming in on the core opportunity, I identified 3 key areas
Communication Gaps
Gaps delay critical information sharing, leading to slower response times.
Resource Allocation Inefficiencies
Result in inefficient deployment of resources, leaving areas underserved.
Unclear Response Coordination
Create delays in managing complex incidents effectively.
DESIGN
With 48 hours on the clock, I prioritized clarity, role-based access, and interactions to support confident decisions in high-stakes environments
I approached this project with a “clarity over complexity” mindset. I scanned real world dashboards, mapped out critical interactions, and focused on making high pressure moments intuitive. With only 2 days, I made fast decisions, built rough flows, and pushed clarity through UI hierarchy and role based visibility.
My focus wasn’t on features — it was on focus
→ Conclusion
SOLUTION
Designing a unified system
Improving Communication
Focused incident details ensure all team members are informed, while a direct chat option with the reporting officer enhances clarity and speed
Improving Resource Allocation and Management
A detailed resource overview table equips operating officers with critical insights for making swift, informed decisions.
Faster Response Coordination and Communication
A mobile push-to-text feature integrated with the dashboard chat ensures seamless communication, reducing gaps and improving emergency response times.
IMPACT
Impact
CES score of 5.7/7 reflecting ease flow
Designed end-to-end within 48 hours
REFLECTION & LEARNINGS
Reflecting my journey
This was my second time designing a web product after my IMDb experiment, and I really enjoyed breaking down multiple JTBDs into clean, digestible designs.
Designing an end-to-end product in just 2 days was intense,I couldn’t explore all the tiny pain points, but it gave me a solid starting point. I’m planning to revisit this project with deeper research.
I worked solo, but before submitting, I shared my design with friends and family for feedback. Their input led to strong improvements, specially the voice-to-text feature on mobile.
