A commonly sought-after integration, Emergency Response Module was missing—causing a critical gap in the offering
The Smart City Suite is a city-scale IoT platform used in command centres to monitor and operate urban services such as waste management, irrigation, street lighting, etc.
While the platform positioned itself as a unified city operations layer, it lacked an emergency response capability. Emergency services continued to operate on separate systems, limiting visibility, coordination, and use of city data during incidents.
This gap surfaced repeatedly through customer conversations, RFPs, and ongoing deployments.
Define and design an emergency response module for the existing City Suite customer. Designing the module as a native extension of the existing product
I worked on defining and designing an emergency response module as a native extension of the Smart City Suite.
An existing customer was actively exploring a centralized emergency response solution. We, especially the UX function led by me, partnered with them to co-develop and pilot the module in a live city environment, ensuring the solution was productized rather than bespoke.
The goal was to close a known gap in the suite while expanding it into safety-critical city operations.
Design a two-part, solution tightly integrated with the Smart City offering
EMERGENCY RESPONDER COMPANION APP
a field-first mobile app supporting:
Incident context and navigation
Real-time situational awareness
Communication with dispatch
DISPATCHER
INTERFACE
an embedded command center interface for:
Incident intake and triage
Resource assignment and tracking
Live coordination with responders
Guiding principles for the solution:
🧩
Fits naturally within the Smart City Suite architecture
🌟
Differentiates from standalone emergency systems
🚒
Solves real emergency response problems
💎
Strengthened City Suite's positioning for emergency-focused deployments
👨✈️
Pilot live at one of our key customer site
📈
2 active deployments underway
🥇
Shortlisted internally as a candidate for patent filings
I planned and facilitated structured discovery sessions with product, engineering, SMEs, and customer stakeholders.
Key Activities
• Domain and workflow understanding
• Researched first responder environments and constraints
• Identification of pain-point for dispatchers and responders
• Solution ideation and prioritization
• Help define value proposition
• Product-in-a-box exercise
Field studies: Studied live dispatcher environments and command centres
Stakeholder mapping
Journey mapping
Defining Value Proposition
Design principles
⛑️
Field-resistant and PPE-friendly interactions
🗺️
Prioritise situational awareness
🧠
Reduced cognitive load under stress
⚡
Faster decision-making over feature clutter
Key Activities
• User story definition across responder and dispatcher journeys
• Rapid prototyping of critical workflows
• Continuous collaboration with SMEs for domain accuracy
• Iterative refinement based on usability testing field feedback
• Storyboarding
• Identified device, hardware and PPE limitations
• Refining value proposition & Product-in-a-box artefacts
Rapid prototyping
Storyboarding
I conducted usability testing with dispatchers and responders. The insights from the study directly shaped layouts, flows and interaction patterns.
Key learnings
Information had to be contextual and prioritised, not exhaustive
Responders needed glanceable confidence-building cues
Reducing tool-switching delivered more value than adding features
Responders won’t go through all the information present, it had to be curated – basically wait for them to ask for it or direct them what to look. Eg BIM info, pre-planning document
The app offering was altered to mainly aid in activities related to incident briefing and planning, and reporting; intentionally reducing focus from ‘incident-response’ phase