From Awareness to Action - Leading Through Barriers
In Part 1, we outlined how fire service leaders can guide their departments through the early phases of technology adoption—from vision casting to pilot deployment. But the path to progress is rarely linear. Even with strong leadership and a clear roadmap, departments often run into real-world barriers that slow or stall innovation. That's where Part 2 picks up.
This section provides a grounded examination of the friction points, such as budget, legacy mindset, and talent, that departments across the country have encountered when integrating emerging technology into fireground operations, training programs, and administrative systems. From limited funds and steep learning curves to cybersecurity risks and cultural pushback, these challenges are real—but they're not insurmountable.
Our goal here isn't just to name the obstacles; it's to offer practical, experience-informed approaches that departments can use to build resilience and stay the course. Whether you're preparing a grant application, navigating legacy system integration, or coaching your crew through their first XR drill, this guide equips you to lead through resistance and sustain momentum.
Adopting new technology is rarely a smooth ride. Fire service leaders should anticipate common hurdles and have mitigation plans:
Budget Constraints:
Funding is often the first barrier to making a major purchase. Fire chiefs usually face tight municipal budgets and must compete with other departments for funds. A new technology might have a high upfront cost (equipment, software licenses, infrastructure upgrades). To address this, leaders can pursue creative funding avenues. Grants are a significant one – FEMA’s Assistance to Firefighters Grants (AFG) have traditionally funded new equipment, especially when tied to safety improvements. Many departments have successfully funded drone programs, advanced PPE, and communication systems through grants rather than local tax dollars.
The key is writing strong grant applications that show clear need and benefit – remember that the story enabled through data from your needs assessment will shine here. If grants aren’t available, consider phased budgeting: break the project into incremental rollouts across fiscal years. Perhaps in year one, you fund a pilot program and use its proven results to justify a larger allocation next year. Partnering with other agencies or regional cost-sharing is another tactic: a few neighboring departments might jointly apply for a grant or share one specialty tech (like a regional training center or a mobile command vehicle with high-end comms; future Firefighter Tracking, Physiology Monitoring, and Extended Reality focused efforts can be developed under JPAs).
Additionally, consider engaging the community or local businesses – some may be willing to sponsor lifesaving technology (examples include community foundations funding items such as rescue boats or thermal imagers for departments). While pursuing these initiatives, be upfront with firefighters about the budget realities. If you can’t buy everyone a new tablet this year and must rotate one per station or rig, explain that it’s a stepping stone and you’re seeking additional funding.
Staffing and Workload:
Implementing tech can strain personnel. There’s training time (taking crews out of service or adding to overtime) and often ongoing administrative work (managing new data systems, etc.). Leaders should plan for this in advance. Can training be integrated into normal shifts to avoid overtime? Or is it worth seeking overtime funds for thorough training (often yes, because properly trained personnel can produce better tech adoption results).
If a new system requires data entry or maintenance (like managing a Captium fleet dashboard or updating digital pre-plan software), consider assigning or hiring a specialist. Some departments create a position or assign an existing officer as the “Technology Officer” or a similar title, who is responsible for managing these systems. Agencies that have yet to consider the need for a formal Chief Technology Officer would be well-positioned to do so today.
Clear leadership and digital integration ownership help move beyond the legacy system. Alternatively, outsource some elements: perhaps the city's IT department can assist with server maintenance or a vendor contract can include periodic system check-ups. Leaders must ensure that adopting tech supports their people – be mindful of the training load and give adequate time for knowledge assimilation.
Learning Curve and User Resistance:
Even with good communication, some individuals will resist or struggle with the new tools. You might have veteran firefighters who are uncomfortable with computers or younger members who are impatient if the tech seems clunky. To address varying tech aptitude, tailor your training by providing extra one-on-one help for tech-averse staff and consider pairing them with a tech-comfortable “buddy.”
Solicit the input of skeptics during pilots, sometimes giving them an active role, turns them into advocates. Also, set realistic expectations: acknowledge that the first few times using the new accountability software at a big incident might feel slower as everyone gets used to it, but emphasize that this is normal and speed will improve over time. Encouragement and patience from officers are essential during this period.
If a mistake happens, treat it as a learning moment rather than immediately blaming the tech or user. Establish a culture where tech adoption learning curves are embraced, in favor of long-term improvement. Busy agencies, where a “chauffeur” is also a scribe for the IC, are already considering the role of an on-scene technology assistant.
Integration with Legacy Systems:
Fire departments rarely get to start from scratch – they often have legacy radios, dispatch systems, and record management systems which need consideration. New tech often has to fit into this puzzle with careful API, UX and UI consideration. Compatibility issues can be a challenge: e.g., a new tablet app for incident reporting might not talk to the decades-old Records Management System the department uses, meaning double entry of data unless a solution is built.
Leaders should involve IT professionals early to map out integration. Sometimes, middleware or custom code can bridge systems; other times, it might be worth upgrading an old system as part of the project scope. When Phoenix Fire adopted digital dispatch boards, they also updated their dispatch center software to ensure a smooth link. If integration is impossible, decide if the new tech can stand alone or if a different approach is needed. Always have a backup plan – maintain parallel use of the old method until the new one is reliable and provides consistent improvements.
Cybersecurity and Data Privacy: With connected technology comes the risk of cyberattacks or data breaches. Fire departments are having increased ransomware and hacks, and threats efforts aimed at municipal governments. Leaders must ensure new connected system (be it an IoT sensor network or cloud-based platform like Captium) is secure.
Work with vendors regarding encryption, authenticate users (without default passwords), and coordinate with the city or county IT security. Establish policies for device integration, including with constituents of SMART Communities, while taking due regard for securing access to sensitive information, there needs to be a professional policy, procedure, and equipment management.
Training should include at least awareness training of cybersecurity, like Haz Mat First Responder Operations, but for digital tools. We must also consider privacy: data like physiology vitals or performance stats could be sensitive. Ensure firefighters that the data collected (such as heart rate during fires) is for safety and training purposes, not punitive measures. Develop clear guidelines on who can access what data. This challenge is relatively new for fire leaders, but borrowing expertise from IT and consider how NFPA standards like NFPA 1851 has data guidelines for PPE, will need upgrading as the advent of intelligent fabrics is upon us.
Investing in security upfront is part of the cost of doing business with tech; far better than dealing with a breach later. With teams like NIST publishing the Special Publichation 1500-29 on Artifical Intelligence in the Fire Service, it makes clear our cyber systems need to be secure, including from intelligent systems designed for nefarious reasons.
Cultural Shift and Myths: Beyond tangible issues, there’s the intangible culture. Some might feel that using tablets, XR, or AI is making the fire service “too high-tech” and moving away from its legitimate, gritty roots. Leaders should respect the pride in tradition but also demonstrate that technology and tradition are not mutually exclusive.
Use historical examples: remind folks that even the revered leather helmet, fire hose, and “fire plugs” were once new “technologies” or that self-contained breathing apparatus (SCBA) met huge resistance decades ago from veterans who thought they were unnecessary – now no one should question the importance of SCBAs. The point is the fire service has always advanced safety equipment, and today’s innovations are a continuation of that legacy.
Celebrate both the past and future: for example, when implementing smart PPE sensors, you might concurrently hold a brief presentation on the evolution of firefighter PPE, connecting the dots that this is just the latest chapter in improving firefighter safety. By framing it as an evolution of craft, you can often neutralize the “this new stuff is ruining the job” sentiment.
Leadership Lens on the Obstacles Ahead
These challenges are familiar to many departments—and they're not going away. But neither is the imperative to evolve. The very presence of these roadblocks is proof that the fire service stands at a critical inflection point. As new tools and expectations reshape the emergency landscape, we can either react defensively (while risking relevance) or lead proactively.
Fortunately, the fire service has always been defined by its ability to adapt under pressure. By taking a clear-eyed approach to budgeting, training, staffing, integration, and cultural alignment, today's leaders can convert friction into fuel. Whether it's securing Public-Private-Partnerships, staff buy-in for new software, or protecting your network from cyber threats, what matters most is having a plan and staying engaged.
In Part 3, we move from navigating barriers to building capacity. We'll explore concrete solutions: how to leverage grant opportunities, forge effective partnerships, and cultivate internal leadership that can carry innovation forward. If Part 2 was about facing challenges head-on, Part 3 is about constructing the frameworks that allow progress to endure.
