Applying insight to 911 technology changes

A 911 call comes in, a mother screaming that her baby isn’t breathing. The 911 dispatcher feels their adrenaline spike, their body and brain responding to the panic in the mother’s voice. This is what they are here for, emergencies and moments like this.

The dispatcher hits the new call launch button to make the call so they can initiate help and begin CPR instructions. But nothing happens. The dispatcher hits the button again, still nothing. The mother wailing into the phone asks if the dispatcher is still there and if help is coming. The dispatcher can’t tell the mother no one is coming yet, all because the button on the new software isn’t working like they were reassured it would.

This scenario is sadly not unique to specific agencies or any specific new technology. In our current time, agencies are implementing new technology, whether as software or hardware, at an unprecedented pace. Many would see the implementation of new technology in the world of 911 as a good thing. The thought is that things must be getting better and more efficient, which means help is quicker and more accurate. In only the best-case scenarios, this is a correct assumption. However, the scenario of smooth and seamless technological implementation is a unicorn in a field of mules.

Our 911 dispatchers already face a mountain of challenges when trying to do their jobs to the best of their abilities. They are grossly understaffed, underfunded, underserved and underappreciated. They are often told about the technology being implemented at their agency at the time of implementation. It is assumed they will simply figure things out and adapt to the new systems as dispatch has always done.

In NIST’s nationwide survey**,** 60–90% of 911 agency personnel reported core information problems at least sometimes, “respondents warned that adding text/video increases cognitive load and stress unless usability and staffing are addressed.” 911 dispatchers are excellent at making castles out of duct tape and popsicle sticks; therefore, they will adapt and overcome the technical challenges.

However, what if, rather than add more challenges to an already overtaxed dispatcher, we could plan the implementation of new technology with the health and welfare of the dispatcher in mind? This would not only lead to smoother technological application, but it would also mitigate significant portions of the stress and distress of those meant to implement said technology, therefore making public safety more safe.

To know how to find and apply appropriate solutions to the issues, we must first understand what the specific issues around implementation of new technology in the 911 realm are:

Lack of Dispatcher Involvement in Decision-Making

  • Tech is often chosen by IT or leadership without input from dispatchers who will use it daily.
  • Results in systems that are inefficient, unintuitive, or create more work.

Increased Cognitive Load

  • New platforms, especially those involving multimedia (e.g., video-to-911, real-time text), can overwhelm dispatchers already dealing with high call volumes and decision fatigue.
  • Multitasking across multiple screens, data sources, and systems can lead to errors or burnout.

Inadequate Training and Rollout Support

  • Dispatchers may receive rushed or minimal training.
  • Lack of hands-on practice before going live can erode confidence and performance.
  • Common pitfall: Learning critical features during real emergencies instead of in simulations.

Implementation Timelines that Ignore 24/7 Schedules

  • Unlike other departments, dispatch centers can’t just “pause” for upgrades or training.
  • Transition periods must be carefully managed to ensure coverage and minimize disruption.

Integration Issues with Existing Systems

  • New software often doesn’t “talk” well with legacy systems (e.g., CAD, RMS, phone, GIS).
  • Leads to delays, duplicate entries, or unreliable data handoff to field units.

Resistance to Change from Staff

  • Change fatigue is real, especially in centers with constant turnover or short staffing.
  • If new tools are seen as making the job harder or threatening job security (e.g., AI transcription), morale can drop.

Poor Evaluation of Operational Impact

  • Tools may look good on paper but fail to enhance situational awareness, speed, or clarity in real-world operations.
  • Metrics for success are often unclear or based on vendor promises instead of dispatcher feedback.

Funding Gaps or Hidden Costs

  • Grants or budgets might cover purchase but not long-term maintenance, training, or upgrades.
  • Centers may be forced to use outdated or “Frankenstein-ed” tech stacks when funds run dry.

Each of these issues introduces its own stressor for 911 dispatchers. The National 911 Program’s white paper on NG911 and mental health concludes NG911 (the next wave of 911 technology) will reasonably increase technostress.

Technostress creators (techno-overload, -complexity, -invasion, -insecurity, -uncertainty) predict worse well-being and satisfaction, and are linked to burnout and other strain outcomes. The challenges listed also add additional stress and trauma injuries, “reinforcing the need to design PSAP implementations that minimize overload/complexity and maximize support.”

There is often a significant, and of course necessary, focus on how the new implementations will affect the field units and the public. When the impact of these changes on dispatchers is ignored – whether through ignorance or indifference – public safety is at risk. How do the issues above affect the people wearing the headsets?

Lack of Dispatcher Involvement in Selection

  • Feelings of being undervalued or invisible within the agency.
  • Increases workplace resentment (“They don’t even ask us.”)
  • Heightens emotional detachment from the job and the mission.

Cognitive Overload from Overlapping or Complex Systems

  • Constant multitasking with unclear systems leads to mental fatigue, decision paralysis, and errors.
  • Overwhelm contributes to chronic stress and burnout.
  • Triggers anxiety during high-priority calls, especially if navigating unfamiliar interfaces.

Inadequate Training and Support

  • Fear of failure due to lack of preparedness (“What if I mess up on a real call?”)
  • Leads to imposter syndrome, especially in new or already-stressed employees.
  • Increases feelings of isolation or frustration with leadership.

Unrealistic Rollout Timelines

  • Creates panic and urgency in an already high-pressure environment.
  • Can cause sleep disruptions, especially with off-shift or overnight training demands.
  • Contributes to a sense of chaos, eroding trust in agency planning.

Poor System Integration

  • Double entry, broken links, or unreliable data causes frustration and helplessness.
  • Creates a sense that their work is inefficient or futile (“Why am I even doing this if it doesn’t work?”)
  • Slows down workflow and erodes their confidence in field safety.

Change Resistance and Morale Concerns

  • Repeated changes without consideration of impact cause emotional exhaustion and resistance.
  • Feeds a culture of cynicism or “survival mode,” which reduces engagement and motivation.
  • Can deepen divisions between dispatch and field units (“They don’t understand what this does to us.”)

No Evaluation of Impact

  • When dispatchers feel ignored or not heard post-implementation, it reinforces a sense of futility.
  • Lack of feedback opportunities leaves stress unaddressed and unprocessed, which compounds over time.
  • Perceived disconnect between frontline experiences and leadership decision-making.

Underfunded Long-Term Support

  • When systems break or updates are delayed, dispatchers are forced to “just deal with it.”
  • Creates a sense of abandonment and “make-do culture.”
  • Lack of stability in tools leads to chronic workplace stress – never knowing what will or won’t work that day.

These effects can drive turnover, reduce performance accuracy, and harm inter-agency collaboration – all of which ultimately compromise public safety. Rather than being focused only on problems, we, as first responders, are always working on solutions. How then, as a collective first responder culture, can we adapt our technology implementations to be the least traumatic experience possible? These solutions also create better agency unity and ultimately better responder and public safety.

Involve Dispatchers in Decision-Making

  • Create a tech advisory group of frontline dispatchers to review new systems before decisions are made.
  • Allow hands-on testing in a sandbox environment with stress scenarios.
  • Provide incentives or stipends for those who participate in vetting/testing processes.

Manage Cognitive Load with Interface Coaching and Workflow Mapping

  • Before go-live, offer a shift-friendly workshop focused on workflow simplification (e.g., how to reduce clicks or screen switches).
  • Integrate mindfulness-based focus techniques and time-blocked recovery practices during long shifts.
  • Assign “tech buddies” or super-users for peer support during high-stress calls.

Offer Trauma-Informed, Tiered Training Models

  • Use simulation-based learning with peer coaching instead of rushed slide decks.
  • Offer separate modules for high-anxiety users and build in optional repetition-based learning.
  • Integrate short wellness pauses into training days (breathing, body scan, stress-reset tools).

Respect 24/7 Coverage with Flexible Rollouts

  • Provide recorded micro-trainings and live Q&A across multiple shifts (with snacks, if possible!)
  • Schedule downtime recovery windows after major updates – avoid stacking big changes back-to-back.
  • Survey each shift’s concerns separately before rollout.

Ensure Cross-System Integration Has Field-Tested Workflows

  • Assign a dispatcher-FTO or trainer to validate end-to-end call flow with each new system added.
  • Offer wellness check-ins post-launch to discuss pain points and update integration plans.

Address Change Resistance with Empathy and Transparency

  • Hold briefings before any rollout that explain why the change matters and how it was chosen.
  • Share stories from other centers and include peer-led discussions on adaptation.
  • Acknowledge loss/grief as part of the transition (“this system worked well for years – we hear that.”)

Evaluate the Human Impact, Not Just Tech Metrics

  • Conduct anonymous wellness pulse surveys before and after implementation.
  • Track performance and perceived stress level on a per-shift basis.
  • Debrief rollout in small groups with mental health-informed facilitators.

Plan for Long-Term Support and Prevent “Tech Fatigue”

  • Include maintenance, mental health impact reviews, and retraining in the tech budget.
  • Schedule regular system “tune-ups” and feedback loops at 30, 60, and 90 days post-launch.
  • Celebrate system wins and dispatcher adaptability with recognition or downtime bonuses.

New technology in 911 should reduce noise, not raise it. The path is clear: involve dispatchers before decisions are made, budget for tiered training that respects 24/7 schedules, test integrations end-to-end, build wellness guardrails for multimedia, and measure the human impact, not just vendor metrics.

When we design rollouts around our lifeline dispatchers, we cut errors, ease cognitive load, and strengthen public trust. Then, when a mother calls because her baby isn’t breathing, the only button that matters works the first time.