May 22, 2025
Subscribe and listen to the Fed Gov Today Podcast anytime on Apple Podcasts, Spotify, or at FedGovToday.com.
In today’s digital battlefield, the strength of a nation’s defense no longer rests solely on tanks, ships, or aircraft. According to retired
Vida brings a rare blend of experience to the conversation, from flying helicopters like the CH-46 Sea Knight and H-60 Seahawk, to shaping technology strategy at the Pentagon, and later collaborating with industry. This diverse background gives her a grounded understanding of what’s at stake when software fails—and what’s possible when it performs as it should.
At the heart of her message is trust. Warfighters, she says, don’t have time to wonder if the latest software update will work when they’re on a mission. “They’re not software engineers—they’re pilots. They need to know the tech will do its job, every time,” Vida explains. The idea that a cockpit is now as much a software environment as a physical machine isn’t just theoretical. It’s the new reality, and it demands software that is secure, resilient, and invisible to the user—because it just works.
Vida emphasizes that developing for a denied environment—where GPS, communication networks, or other critical tools may be jammed or unavailable—should be the default mindset. Today’s software must assume worst-case scenarios from the outset. She points to ongoing efforts in AI and quantum-enhanced navigation as promising examples, noting that leading defense tech companies are already designing tools that don’t rely on traditional GPS.
Another major theme in Vida’s conversation is the need for deep collaboration between government and industry. She argues that industry is often willing and capable of delivering game-changing solutions, but government reluctance to engage—often citing vague fears about procurement rules—prevents the open dialogue necessary to build effective tools. “Without hearing directly from warfighters, industry is limited to what it knows,” she says, urging government leaders to open their doors and talk more freely with those building the tools they depend on.
She recalls a telling example from her flying days: a survival radio that was so poorly designed it couldn’t be operated easily under stress. The device had clearly been built without meaningful pilot input. “That kind of misalignment can’t happen with software,” she says. “It wastes time, money, and most dangerously, it puts lives at risk.”
While Vida believes the Pentagon is making progress, especially with the creation of a formal software acquisition pathway and policies promoting commercial software adoption, she warns that the pace of change must accelerate. With rapid advances in technology—and growing threats from adversaries—trust, communication, and realistic assumptions must form the foundation of future software systems.
Her final message is clear: keep talking, keep building partnerships, and above all, build software that warfighters can trust with their lives.