By Shane Halton and Adam Reiffen
“When companies spend millions of dollars on new information technologies but don’t change anything else, there are usually barely detectable productivity improvements. In contrast, when they also invest similar amounts in business process changes and in worker training, productivity can double or more.”-The Second Machine Age: Work, Progress, and Prosperity in a Time of Brilliant Technologies by Andrew McAfee and Erik Brynjolfsson
In the last year, Israel disabled all of Iran and Hezbollah’s senior military leadership at a stroke with a series of audacious precision strikes. Ukraine launched hundreds of small drones against Russia’s strategic air assets from clandestine launch locations deep inside Russian territory. Though the weaponry and tactics employed in these strikes varied wildly from explosive pagers to first person view (FPV) drones, one common thread tied these operations together – innovation in the realm of Information Warfare (IW). From the Levant to the Black Sea, the crucial role played by IW (hereafter used collectively to refer to the intelligence, cryptology, information technology, meteorology/oceanography, cyber, and space communities) has never been more impactful to warfighting than it is today.
The US Navy has adjusted accordingly to this changing character of war. In 2024, the Navy moved Information Warfare (IW) out of the Restricted Line officer category and into a newly minted Information Warfare Line (IWL) category, which serves to both acknowledge IW’s growing impact on operations and to open additional opportunities for leadership across the Fleet. This elevation offers the IW community an excellent chance to step back, assess its tactical strengths and weaknesses, and innovate where needed.
If called upon today, could the Navy’s IW community deliver the same level of support to operations that the IDF and Ukrainian military receive from their respective military intelligence communities today? Surely it has the resources. The IW community has a workforce in the tens of thousands and close working ties with the national intelligence community. The DoW is making huge capital investments in AI solutions that should positively impact IW workflows. With all these resources available, is innovation even necessary?
The answer is yes. Despite being well-stocked with talented personnel and appropriated funds, the Navy IW community aboard Carrier Strike Groups (CSGs), Amphibious Readiness Groups (ARGs), and at fleet-level Maritime Operations Centers (MOCs) still operate according to increasingly antiquated and inefficient business practices. Dozens of human analysts spend countless man-hours every day creating and editing PowerPoints. Others spend time using outdated search tools to answer requests for information (RFIs) from senior leadership, watchstanders, and other operators throughout the organization. Compounding these challenges is the structure of the information systems themselves, as critical information remains siloed in disparate databases, thwarting rapid retrieval, analysis, and automated fusion. The net effect of these overlapping issues is that the most data-centric part of the Navy, the Information Warfare Community, is today poorly postured to lead the Navy’s digital transformation and risks failing to effectively adapt to the modern maritime battlespace.
Luckily for the Navy and the country at-large, there are several innovative initiatives underway across the naval IW enterprise that are showing us the way forward. These efforts, coupled with the thoughtful integration of commercially available AI solutions, offer Navy IW a once in a generation opportunity to increase productivity and output for relatively little cost. The solutions can be grouped into three categories: workforce, organizational reform, and technological solutions.
Workforce: Identifying and Cultivating Digital Talent
Walk into any MOC in the Navy and you may find an intelligent, bright-eyed young individual who identifies themselves as the command’s Chief Data Officer, or maybe Chief Technology Officer, or perhaps lead for Artificial Intelligence or Data Science. Press them a little further and they will happily explain to you that they started off at the MOC doing something entirely different but at some point they shared with their leadership that they had a technical background and could do some coding and voila they received a new job, a new set of responsibilities, and a direct line of communication to senior leadership.
The positions of Chief Data Officer, Chief Technology Officer, AI Lead, etc. do not exist on any MOC manning documents. Still, those individuals are today found at every MOC in the Fleet. What is happening? The simplest answer is that the operational leadership at the MOCs realized they needed something that Big Navy was unable or unwilling to provide, then created new positions of their own accord by drawing from their own staffs. Every MOC did this independently, seemingly without coordinating across the Service. This is both an admirable example of deckplate innovation at the MOC-level and a fairly serious indictment of the Navy’s manpower challenges when it comes to manning a modern, digital workforce.
But the need for an innovative solution only highlights a Fleet-wide problem. The Navy lacks the ability to identify, employ, and retain digital talent (hereafter “digital” will refer to data science, data engineering, and artificial intelligence, broadly defined). There is one Navy Additional Qualifying Designator (AQD) for Data Science and it is only granted upon graduation from the Naval Postgraduate School’s (NPS) Data Science Program. There are no equivalent AQDs for artificial intelligence or other information- and data- related fields of study. The Navy currently has a much better understanding of which Sailors speak Hausa than which can code in Python, C++, or Java.
The easiest way for the Navy to address this issue is to leverage work already done by the DoW. The DoW’s Digital Workforce initiative, started by the DoW Chief Data and Analytics Office (CDAO) in 2022, generated multiple highly readable reports and useful insights for how to develop “digital talent” across the DoW. CDAO already did the hard work by creating language that could easily convert to Navy AQDs and Sub Specialty Codes (SSPs) related to data science, data engineering, software engineering, AI, etc. Once established, these AQDs and SSPs should be called out explicitly in board convening orders and other promotion criteria, making plain to both promoters and promotees that such skills are as much Navy priorities as Operations Research and Financial Management. The IW community can further lead in workforce development by serving as the community sponsor for innovative graduate certificate programs and “stackable” degrees delivered asymmetrically, including the recently-launched Master of Applied Computing program at NPS.
The AQD/SSP approach has the advantage of increasing the Navy’s oversight of who has which digital skills without unduly disturbing existing career paths, and allows detailers, commanders, and other senior leaders to quickly find and fit talent to key roles in the Fleet. Formally recognizing digital qualifications would have positive impacts on URL communities as well. For instance, an E-2D pilot with coding expertise can still be a pilot, but the Navy will also be aware that he or she has coding expertise, allowing that person to fill relevant billets, liaison roles, or collateral duties. Over time, this AQD/SSP approach will allow the formal creation of billets like the MOC Chief Data Officer and ensure that those billets are manned by qualified personnel. We believe the above recommendations are in alignment with the “Talent” section of the DoW’s January 9, 2026 AI guidance.
Organizational Reform Afloat and at the Fleets
In November 2022, Carrier Strike Group One (CSG-1), in collaboration with Project Overmatch, established the Navy’s first Data Science at Sea (DS@S) team empowered to use all available intelligence, battlespace, and operational data to address emerging warfare requirements. The DS@S team, cobbled together from volunteers around CSG-1 and its subordinate units, automated routine tasks and found novel ways to analyze, fuse, and visualize battlespace data over two deployments to the Western Pacific and the 2024 Rim of the Pacific (RIMPAC) exercise in Hawaii. This grassroots effort went on to inspire similar efforts through PACFLT and resulted in the generation of a classified TACMEMO from the Navy Information Warfare Development Center (NIWDC) detailing the initiative.1
Over the teams’ nearly three years of operations on CSG-1, it partially or fully automated many IW processes across the Strike Group. The major lesson learned was not that you can do more IW work with fewer people – although this is true – but rather that the DS@S approach creates more bandwidth and time for meaningful human analysis. The DS@S team also developed several novel battlespace awareness and planning tools that are now commonly used by units across the Pacific.2
These teams cannot continue to operate on an ad hoc basis, however, and must be codified, trained, and employed with the same eye towards standardization as at any ESG or MOC across the Fleet. Activating reservists and peeling civilian shipriders away from other tasks has worked well enough to date but is not sustainable over time due to an ever expanding list of operational requirements with ever limited material and personnel resources. To generate consistent decision advantage, build skills over time, and be maximally responsive to the needs of the CSG, ESG, or MOC Commander, data science teams must have a permanent home, dedicated billets, and funding for both training and equipment. In May 2025, the Naval Postgraduate School hosted a summit with a variety of stakeholders to tackle these issues and explore how best to scale the DS@S initiative across the Fleet and “productionalize” the tools that the deployed teams develop.
Until now, the CSG-1 DS@S team has been housed within the Admiral’s staff, but the most natural fit for such a group is within the Information Warfare Commander (IWC) afloat construct. At present, the IWC is the senior member of the IW community embarked with the CSG, but as a member of the Admiral’s staff is without ADCON of any personnel and OPCON of only a select few. The exact nature of the IWC’s roles and responsibilities varies between CSGs based on commander’s discretion. The lack of job standardization and formal authorities (i.e., budget, NJP) for IWCs across the Fleet has hamstrung the role.
There is an effort underway to address the structural weakness of the current IWC construct. In December 2025, Naval Information Forces (NAVIFOR), the TYCOM for IW across the fleet, established two Information Warfare Squadrons or IWRONs. These IWRONs are designed to “addresses the increasing complexity and sophistication of global threats, which actively seek to exploit vulnerabilities from seabed to space.”3 It is critical that these new IWRONs establish DS@S teams as a Department within the command. Should these pilot IWRON initiatives succeed, they should be replicated both ashore at the MOC (as previously discussed) and afloat at the Navy’s Amphibious Readiness Groups (ARGs). In this construct, the DS@S team would have the personnel, budget, hardware, and authorities to operate continuously as a digital innovation hub for the entire CSG. The IWC could even dispatch the team to work with allies and partners, as the CSG-1 DS@S team did with its French counterparts aboard ships within the CHARLES DE GAULLE Strike Group during the PACIFIC STELLER series of exercises in early 2025.4
Technological Transformation: Leveraging AI and Data
First airing in 1966, Gene Rodenberry’s Star Trek imagined a future where technology had completely redefined the human experience, allowing us to explore the universe with a fleet of massive spacecraft. One thing that the starship Enterprise did not have was an Intelligence Officer. If someone wanted to know a specific scientific fact, the capabilities of Klingon ships or the location of the nearest spaceport, they asked “Computer.” The US Navy is not quite there yet, but we’re much closer now than ever. In July 2025, the DoW announced it was granting contract awards of up to $200 million for artificial intelligence development at Anthropic, Google, OpenAI and xAI.5 Not all of that money will directly impact Navy priorities, nor will it be immediately available to afloat units, but we are getting very close to the day when almost all classified RFIs can be answered by a Large Language Model (LLM) connected to every SIPR and JWICS on a ship. Secretary Hegseth’s December announcement of GenAi.mil is a welcome step towards realizing this vision.6
The deployment of LLMs on classified datasets across the Fleet is unlikely to lead to the wholesale replacement of IW personnel but will likely change the nature of their work. LLMs on warships will need to be optimized to operate in denied or degraded communications environments, meaning they likely need to be installed and run locally onboard ships. This will improve daily performance by removing the need for an internet connection, but it also means that over the course of a deployment the datasets feeding the LLM will become out of date and questions like “when is the last time Country X’s ship operated here” will go from being accurate and useful to inaccurate and misleading after a few weeks.
This means that the role of deployed IW personnel will be ensuring that the datasets feeding LLMs are accurate and up to date. This includes the tactical data that is collected by the ship during the course of a deployment, whether that is intelligence, METOC, or SIGINT data. As this data management and LLM curation will be a cross-IW enterprise it should become a core function of the nascent IWRON structure discussed above. Some learning and experimentation will be required as the knowledge management practices onboard most ships today do not extend beyond maintaining Sharepoint sites, Collaboration at Sea (CaS) pages, or share drive folders.
Of course ships themselves must also be considered in the execution of this concept, particularly regarding space available for hardware and power output to run LLMs as described. Operating the aforementioned equipment requires specialized–or at least dedicated–compute, which will have to be installed likely in classified spaces already at a premium on smaller classes of warship. Furthermore, both the ship’s Engineering and Information Warfare teams must be engaged to determine what capabilities could be lost or degraded if LLMs are integrated into the ship’s technology stack, including hardware, software, power supply, maintainers, and operators. These conversations and their solutions fall squarely in the wheelhouse of NAVIFOR’s IWRON program, currently being piloted on both the east and west coasts. IW Commodores and their staffs should work directly with both operational and training DESRONs, along with AIRLANT/PAC and CSG staffs, to ensure hardware, software, and manpower training and operational needs are met going into workup and deployment cycles. Integrating these solutions into routine operations as quickly as possible will be key to fully implementing an AI strategy that is set up for success.
Innovation is Necessary to Retain IW’s Warfighting Edge
As McAfee and Brynjolfsson note, investments in both workforce training and improved business practices are more impactful than technological investment alone. The Navy IW community must therefore be proactive in addressing its productivity challenges by taking a round turn on training and innovation. We must organize our forces both afloat and ashore to identify current talent, train new innovators, and ensure they are accounted for throughout their time in uniform. We must prioritize our operational forces both afloat and ashore. This means the IWC must be resourced, staffed, and authorized appropriately to operate afloat, while their MOC counterparts must be similarly taken care of ashore. And we must incentivize our most innovative personnel–the Navy’s greatest strength–to learn, train, fight, and stay Navy.
Taken together, these improvements are critical to the Navy’s future and certainly greater than the sum of their parts. The journey of a thousand miles begins with a single step, after all. The Navy has reorganized itself to adapt to technological change time and again – steel over wood, steam over wind. Now the Navy must absorb, understand, and harness the power of the digital technologies to maintain its warfighting edge.
Lieutenant Commander Shane Halton is an Intelligence Officer currently serving in Washington DC. He previously served as a Requirements Officer at the Navy’s Digital Warfare Office and helped create the Navy’s first Data Science at Sea team aboard CSG-1.
Lieutenant Commander Adam Reiffen is an Intelligence Officer currently serving as a Federal Executive Fellow at Brown University’s Watson School of International and Public Affairs. He previously served as a Requirements Officer at OPNAV N2N6 and was Officer-in-Charge of the Navy’s Data Science at Sea team aboard CSG-1 from 2024-25.
The opinions expressed are those of the authors and do not reflect the views or policy of the U.S. Department of War, the Department of the Navy, or the U.S. government. No federal endorsement is implied or intended.
References
1. Rear Admiral Carlos Sardiello and Lieutenant Commander Shane Halton, U.S. Navy, and Annie Voigt, CNA, “The Case for Data Science at Sea,” CNA In-Depth, June 2024, https://www.cna.org/our-media/indepth/2024/06/the-case-for-data-science-at-sea.
2. Lieutenant Commanders Adam Reiffen and Shane Halton, U.S. Navy, “Lessons Learned in Year One of Data Science at Sea,” Proceedings, May 2024, https://www.usni.org/magazines/proceedings/2024/may/lessons-learned-year-one-data-science-sea.
3. Joshua Rodriguez, U.S. Navy, “A Paradigm Shift: Navy Establishes First Information Warfare Squadron, ” navy.mil, Dec 2025, https://www.navy.mil/Press-Office/News-Stories/display-news/Article/4353901/a-paradigm-shift-navy-establishes-first-information-warfare-squadron/
4. Ensign Rachael Jones, U.S. Navy, “U.S. and French Host First-Ever Military Hackathon at Sea,” DVIDS, May 2024, https://www.dvidshub.net/news/492989/us-french-host-first-ever-military-hackathon-sea.
5. Sydney J. Freedberg, Jr., “Anthropic, Google and xAI win $200M each from Pentagon AI chief for ‘agentic AI’,” Breaking Defense, July 14, 2025, https://breakingdefense.com/2025/07/anthropic-google-and-xai-win-200m-each-from-pentagon-ai-chief-for-agentic-ai/
6. C. Todd Lopez, ”Hegseth Introduces Department to New AI Tool,” war.gov, Dec 2025, https://www.war.gov/News/News-Stories/Article/Article/4355797/hegseth-introduces-department-to-new-ai-tool/.
Featured Image: GULF OF ALASKA (Aug. 23, 2025) Lt. Michael Zittrauer works on a terminal in the combat information center (CIC) aboard the Arleigh Burke-class guided-missile destroyer USS Frank E. Petersen Jr. (DDG 121) during exercise Northern Edge 2025 (NE25). (U.S. Navy photo by Mass Communication Specialist 3rd Class Christian Kibler)

