DubsTech Protothon
A 24-hour prototype to help the Seattle Fire Department dispatch and route faster.
- Problem
- Crews lose time between the call, dispatch and the drive.
- Solution
- Case details, routes and blockages on one tablet screen.
- Role
- Researcher (team of 3)
- Tools
- Figma
- Timeline
- 24 hours
Research
Where does time get lost between a 911 call and a crew on the road?
The data
Two teammates and I charted the department’s own numbers. Against a 90% standard at each stage, the 2023 report fell short everywhere: only 51% of calls were processed within 60 seconds.
Define
Three pain points to design around.
Slow dispatch and prep
Gaps between receiving a call and preparing the right equipment.
Poor routing visibility
Wall maps and run books are outdated or missing detail.
Unclear communication
Dispatch messages lack real-time feedback, and on-site updates are hard to track.
Design
Colour and layout that direct attention under pressure.
A focused visual system
Bold orange headers such as “Location” and “Caller information” guide the eye. On the map, headers drop to 50% opacity while routes stay bright, and case details live in a collapsible sidebar.
Dispatcher updates and road blockages are always within two clicks of the main screen.
Prototype
Case details and the route on one screen. There was no time to recruit testers, so the judges gave feedback.
Learning outcomes
Scope to the evidence
With 24 hours, anchoring every decision to three pain points from the data kept the team focused.
Design for stress
Colour, opacity and a two-click rule help people act quickly when every second counts.
Plan feedback, even in a sprint
We relied on judges’ feedback. Next time I’d set aside an hour for quick hallway tests.