By Erik Heftye
Words matter. They frame thoughts and influence concepts by shaping perceptions, preferences, and priorities in the form of tacitly embedded assumptions.[1] Unfortunately, military conceptual frameworks are often encapsulated in jargon and buzzwords that periodically dominate the landscape of Pentagon briefing slides. Notable past examples of these operational concept catchphrases include: Active Defense, AirLand Battle, Full-Spectrum Dominance, Network-Centric Warfare, Effects-Based Operations, Anti-Access/Area Denial, and AirSea Battle. The latest conceptual phrase to command the spotlight is Multi-Domain Battle, which was officially unveiled by the US Army’s Training and Doctrine Commander, General David Perkins, at the Association of the U.S. Army’s Annual Meeting and Exposition on October 4, 2016.[2] This announcement was foreshadowed a month earlier in an article by Albert Palazzo and David P. McClain in which they touted “multi-domain battle will allow the joint force commander to dominate the targeted domains” because it “breaks down the traditional environmental boundaries between domains that have previously limited who does what where.”[3] The advent of multi-domain battle begs a question that remains unanswered: what constitutes a military domain and why make this distinction?
Over the past two decades the use of the word domain has attained wide acceptance in the military lexicon. Vague when described in doctrine, it exerts a strong influence by establishing the most basic boundaries of military functional identities. As described in an essay by Frank Hoffman and Michael Davies, domains “create a frame of reference that defines the preparation and conduct of war. Each military institution and Service crafts doctrine and platforms that are designed to operate or maneuver in their dominant domain. Little preparation is made to conduct war beyond them.”[4] Despite the unquestioned usage of domain-centric terminology, the exact meaning of domain remains largely undefined without consideration of etymological origins. However, the word contains some built-in assumptions regarding how we view warfare that can limit our thinking. An ambiguous categorization of separate operating domains in warfare could actually pose an intractable conceptual threat to an integrated joint force, which is ironically the stated purpose of multi-domain battle.