Dynamic Coverage Map

Dynamic Coverage Map

Designing Real-Time Geospatial Monitoring for Public Safety Radio Systems

Designing Real-Time Geospatial Monitoring for Public Safety Radio Systems
Designing Real-Time Geospatial Monitoring for Public Safety Radio Systems
A screenshot of a mockup of the map with difference view turned on, fair and poor Call Quality selected in the legend, and a drilldown visualization showing details of an individual cell.
A screenshot of a mockup of the map with difference view turned on, fair and poor Call Quality selected in the legend, and a drilldown visualization showing details of an individual cell.
A screenshot of a mockup of the map with difference view turned on, fair and poor Call Quality selected in the legend, and a drilldown visualization showing details of an individual cell.

Summary

Summary

Made radio-frequency performance visible in real time. I led end-to-end UX for a map-based analytics feature that plots call quality and signal strength across time and geography. The design unified multiple stakeholder needs—proactive monitoring and historical comparison—into one intuitive view with difference overlays, thresholds, and drill-downs. Released as part of a cloud platform for public-safety communications infrastructure, the feature now helps agencies detect coverage gaps faster and validate fixes with live telemetry instead of delayed reports.

Role: Sole Product/UX Designer

Users: System admins, RF engineers, operations teams

Problem: Coverage issues surfaced late through anecdotal reports; no clear spatial visibility into live signal quality

Solution: Real-time and historical RF monitoring in a single interactive map experience

Key Features: Continuously updated map, date-range filtering, Difference View, threshold alerts, drill-down panels, color-blind-safe palette, responsive layouts

My Contributions: Research, stakeholder workshops, IA/flows, Figma prototyping, design-system components, user validation

Tools: Figma, FigJam, design-system library, ArcGIS, Google Workspace

Outcomes: Shipped as a live feature used in production; internal evaluations showed faster root-cause identification and reduced reliance on manual drive tests

At a Glance

At a Glance

At a Glance

Role: Sole Product/UX Designer

Users: System admins, RF engineers, operations teams

Problem: Coverage issues surfaced late through anecdotal reports; no clear spatial visibility into live signal quality

Solution: Real-time and historical RF monitoring in a single interactive map experience

Key Features: Continuously updated map, date-range filtering, Difference View, threshold alerts, drill-down panels, color-blind-safe palette, responsive layouts

My Contributions: Research, stakeholder workshops, IA/flows, Figma prototyping, design-system components, user validation

Tools: Figma, FigJam, design-system library, ArcGIS, Google Workspace

Outcomes: Shipped as a live feature used in production; internal evaluations showed faster root-cause identification and reduced reliance on manual drive tests

The Opportunity: Visualize What’s Invisible

The Opportunity: Visualize What’s Invisible

In public safety, a missed radio call can mean a missed moment to save a life. Yet admins often learned about RF coverage issues after the fact, through delayed tickets or anecdotal reports, if they were reported at all. Despite rich telemetry from thousands of devices, there wasn’t an intuitive way to see performance on a map and compare how it changed over time.

Different stakeholder groups prioritized different lenses for RF data: some needed configurable, aggregate analysis to spot patterns, while others needed a continuously updated, mobile-friendly view for operational awareness. I aligned these needs into a single map experience that supports both proactive monitoring and historical comparison.

My Mission

My Mission
  • Lead the end-to-end UX for a dynamic, map-based analytics feature that continuously plots radio performance (RSSI, BER) across geography and time.

  • Align stakeholder needs and deliver clarity for users operating in complex, high-risk environments.

Discovery & Research: Grounding in Real User Needs

Discovery & Research: Grounding in Real User Needs

Secondary Research

Secondary Research

I reviewed stakeholder input, prior learnings, and public references. The patterns were consistent:

  • Admins struggled to pinpoint when and where issues occurred.

  • Reports were delayed, inconsistent, or anecdotal.

  • Drive testing was costly and reactive.

  • These gaps made it hard to separate device issues from network coverage problems, which led to guesswork and delayed fixes.

Journey Mapping

Journey Mapping
An image of a representative journey map that is similar to those created in the process of mapping the user journey for thi product.
An image of a representative journey map that is similar to those created in the process of mapping the user journey for thi product.
An image of a representative journey map that is similar to those created in the process of mapping the user journey for thi product.

A typical path looked like this: a first responder misses a call; it’s reported much later (if at all); a technician tries to infer location/time/cause, then drives out to test, often without reproducing the issue. We needed a tool that proactively surfaces and validates signal anomalies, without waiting for user complaints.

Stakeholder Alignment

Stakeholder Alignment

Different groups prioritized different lenses for RF data:

  • Trend & analysis: configurable, aggregate views to spot patterns.

  • Operational awareness: a continuously updated, mobile-friendly view for day-to-day monitoring.

I facilitated workshops to synthesize these needs and defined a unified interaction model so the same map supports both historical comparison and ongoing monitoring.

Design Process: Building a Map That Matters

Design Process: Building a Map That Matters

An image of a spreadsheet containing user stories that is representative of the type of user stories and prioritizations that were made as a part of the process to ship this product.
An image of a spreadsheet containing user stories that is representative of the type of user stories and prioritizations that were made as a part of the process to ship this product.
An image of a spreadsheet containing user stories that is representative of the type of user stories and prioritizations that were made as a part of the process to ship this product.

User Stories

User Stories

Grounded in user and organizational goals:

  • “I need to see where signal quality drops below acceptable levels in a continuously updated view.”

  • “I want to compare this week’s coverage to last week’s to spot changes.”

  • “I need to drill into an area to understand what’s driving issues there.”

Wireframes & System Architecture

Wireframes & System Architecture
An image of a pencil drawing that is representative of low fidelity sketches used in the process of designing this product.
An image of a pencil drawing that is representative of low fidelity sketches used in the process of designing this product.
An image of a pencil drawing that is representative of low fidelity sketches used in the process of designing this product.
Early concepts explored:
  • Time-range filters and quick presets

  • Zoomable geospatial overlays (hex-tiled regions)

  • A clear legend for signal-quality states (Good / Fair / Poor)

  • Threshold toggles to highlight areas breaching defined limits

Cross-Functional Collaboration

Cross-Functional Collaboration

I partnered with:

  • Subject-matter experts to calibrate meaningful ranges for key RF indicators in the UI

  • Product managers to prioritize scenarios

  • Engineering leads to validate feasibility and delivery paths

  • Design-system owners to establish reusable, accessible mapping patterns

  • Data partners to explore geospatial signals that could enrich the experience

Prototyping in Figma

Prototyping in Figma
A screenshot of a Figma file canvas with dozens of screens from the recreataed prototype of this project.
A screenshot of a Figma file canvas with dozens of screens from the recreataed prototype of this project.
A screenshot of a Figma file canvas with dozens of screens from the recreataed prototype of this project.

I produced multiple clickable prototypes in Figma to evaluate:

  • Heatmap overlays vs. segmented region tiles

  • Static vs. adjustable thresholds

  • Desktop vs. mobile interaction models

Design System Contributions

Design System Contributions

Because interactive mapping patterns were limited, I:

  • Designed the legend and filter interactions for map views

  • Created color-blind-safe visualization palettes

  • Documented components for reuse across products

Testing & Validation: Iterating Toward Confidence

Testing & Validation: Iterating Toward Confidence

Testing & Validation: Iterating Toward Confidence

Internal Reviews

Internal Reviews

Walkthroughs with product and engineering validated feasibility and surfaced early refinements.

UX Peer Testing

UX Peer Testing
A screenshot of the map legend showing the before and after design of adding information icons that describe each element in the legend to help users contextually as a part of feedback from UX peer testing.
A screenshot of the map legend showing the before and after design of adding information icons that describe each element in the legend to help users contextually as a part of feedback from UX peer testing.
A screenshot of the map legend showing the before and after design of adding information icons that describe each element in the legend to help users contextually as a part of feedback from UX peer testing.

Design peers stress-tested readability, flow, and terminology. We learned:

  • Legends needed clearer explanations (e.g., RF measures)

  • Threshold controls benefited from presets plus manual input

User Evaluation

User Evaluation

With representative users in mission-critical contexts, we evaluated scenarios like:

  • “Spot coverage regressions over the past month.”

  • “Find areas with elevated call failures last week.”

  • “Compare performance before and after a tower change.”

Key refinements

  • Added a Difference View to compare two timeframes visually

  • Introduced drill-down panels with area-level trends and stats

  • Made filters resettable with one click

“Seeing coverage like this makes it easier to justify where we spend our time. We’ve wanted something like this for years.” — System administrator

A GIF that shows a mockup of a map zooming into a region where a user clicks through a recreated prototype representative of the shipped version of this product.
A GIF that shows a mockup of a map zooming into a region where a user clicks through a recreated prototype representative of the shipped version of this product.
A GIF that shows a mockup of a map zooming into a region where a user clicks through a recreated prototype representative of the shipped version of this product.

Final Design Highlights

Final Design Highlights

Feature What it does Why it matters
Continuously Updated Map Plots call-quality and signal-strength data on a geographic map. Surfaces problems as they emerge.
Historical Views Select time windows (e.g., last 7 days) to view trends over time. Helps detect slow degradation and validate long-term fixes.
Difference View Compare any two date ranges visually on the map. Powerful for regression detection or post-fix verification.
Threshold Alerts Emphasize areas breaching defined limits. Enables proactive, user-defined monitoring.
Drill-Down Panels Reveal contextual details and trends for the selected region. Makes the map actionable with less guesswork.
Accessible Palette Color-blind-friendly visualization. Ensures every admin can interpret signal quality at a glance.
Responsive Layouts Optimized for desktop and field use. Enables monitoring outside the control room.
Feature
Continuously Updated Map
What it does
Plots call-quality and signal-strength data on a geographic map.
Why it matters
Surfaces problems as they emerge.
Feature
Historical Views
What it does
Select time windows (e.g., last 7 days) to view trends over time.
Why it matters
Helps detect slow degradation and validate long-term fixes.
Feature
Difference View
What it does
Compare any two date ranges visually on the map.
Why it matters
Powerful for regression detection or post-fix verification.
Feature
Threshold Alerts
What it does
Emphasize areas breaching defined limits.
Why it matters
Enables proactive, user-defined monitoring.
Feature
Drill-Down Panels
What it does
Reveal contextual details and trends for the selected region.
Why it matters
Makes the map actionable with less guesswork.
Feature
Accessible Palette
What it does
Color-blind-friendly visualization.
Why it matters
Ensures every admin can interpret signal quality at a glance.
Feature
Responsive Layouts
What it does
Optimized for desktop and field use.
Why it matters
Enables monitoring outside the control room.

Impact & Outcomes

Impact & Outcomes

Delivered production designs and specifications adopted into the live release of the RF Analytics Map. Early user evaluations and internal telemetry reviews indicated:

  • Faster pinpointing of coverage gaps

  • Fewer manual drive tests and anecdotal tickets

  • Clearer visibility into network health trends

  • Improved collaboration between RF engineers and operations teams

System-Level Outcomes

System-Level Outcomes
  • Established reusable geospatial patterns for future products

  • Raised accessibility standards for map-based data visualization

  • Aligned stakeholders via shared scenarios and a single interaction model

Reflections

Reflections

This project transformed an ambiguous, data-rich problem into a live, high-impact product.
It sharpened how I:

  • Align divergent needs through shared user stories

  • Translate domain-specific data (RF metrics) into actionable UI

  • Design for accessibility, scale, and clarity in complex tools

Ultimately, thoughtful map-based UX made RF performance observable and actionable when it mattered most—now powering live visibility across thousands of radio systems.

Authenticity & Confidentiality
This case study reflects real design work. Certain labels, visuals, and data are anonymized, generalized, or reconstructed from public references. No non-public, confidential, or proprietary information, nor any third-party proprietary information, is disclosed.

© 2025 by Joe Balich — All Rights Reserved

© 2025 by Joe Balich — All Rights Reserved

© 2025 by Joe Balich — All Rights Reserved