Transforming Military Power since the Cold War

Britain, France, and the United States, 1991–2012

by Theo Farrell, Sten Rynning, and Terry Terriff

Online Description

Transforming Military Power since the Cold War is a comparative study of how the American, British, and French armies changed after 1991 in response to strategic uncertainty, information technology, expeditionary operations, and the operational shocks of Iraq and Afghanistan. The book’s central analytical move is to treat “transformation” not as a slogan but as a set of concrete military innovations: networking the force, shifting toward modular or medium-weight expeditionary structures, and, in Britain and France, developing effects-based or holistic approaches to operations (pp. 1-14). Source PDF:

The book matters for SAASS 660 because it directly tests whether post-Cold War “transformation” produced genuine military innovation: changes in warfighting that significantly increased military effectiveness. Its answer is deliberately mixed. Networked forces and some doctrinal changes improved military effectiveness; modularity made the US Army more usable; but the US Future Combat Systems and British FRES programs show how technological enthusiasm, acquisition complexity, weak operational feedback, and budget pressure can turn “innovation” into expensive non-delivery (pp. 83-99, 150-154, 170-182, 283-299).

Author Background

Theo Farrell is identified in the PDF as Professor of War in the Modern World in the Department of War Studies at King’s College London. Sten Rynning is identified as Professor in the Department of Political Science and Head of the Center for War Studies at the University of Southern Denmark. Terry Terriff is identified as Arthur J. Child Chair of American Security Policy and Professor in the Department of Political Science at the University of Calgary (PDF p. 1).

60-Second Brief

• Core claim: The US, British, and French armies genuinely transformed after the Cold War, but not because technology deterministically produced an RMA. Transformation emerged from the interaction of organizational interests, ideas, leaders, operational experience, budgets, joint institutions, and alliance emulation (pp. 7-14, 283-299).
• Causal logic in a phrase: strategic shock + technological opportunity + organizational self-interest + operational feedback = uneven military innovation.
• Main level(s) of analysis / lens: comparative organizational analysis, filtered through military innovation theory, strategic culture, civil-military politics, defense acquisition, and operational adaptation.
• Why it matters for SAASS 660:
  • It distinguishes real military innovation from acquisition programs, rhetoric, or administrative reform (pp. 7-9, 283-284).
  • It shows why technological revolutions must be socially, doctrinally, and organizationally absorbed before they become military effectiveness (pp. 1-2, 295-299).
  • It complicates Rosen’s peacetime/wartime innovation distinction: all three armies began transformation in peace, but war redirected, validated, or killed major parts of those programs (pp. 290-292).
  • It supplies strong analogies for AI, autonomy, JADC2, ACE, contested logistics, and “system of systems” acquisition: the integration problem is usually harder than the invention problem (pp. 83-99, 138-144, 246-260).
• Best single takeaway: Transformation succeeds when technology, doctrine, organization, training, and operational feedback are integrated around a real warfighting problem; it fails when institutions mistake future-war visions, acquisition momentum, or interoperability aspirations for demonstrated battlefield effectiveness.

SAASS 660 Lens

This book sits closer to the social-construction side than the technological-determinist side, but it does not deny that technology matters. The authors treat the information revolution and precision-strike technologies as macro-drivers of military change, especially after the 1991 Gulf War suggested that a new RMA might be underway. But they insist that “technology alone” does not produce revolutionary change; doctrine, organization, social context, political purpose, and operational learning determine whether a technology actually changes warfighting (pp. 1-2, 7-14, 295-299).

On the sources of military innovation, the book offers a blended model. External change created pressure and opportunity: the end of the Cold War, the Gulf War, 9/11, Kosovo, Iraq, Afghanistan, and the diffusion of US transformation ideas. But the actual content of innovation was shaped internally by organizational interests, military culture, joint institutions, procurement agencies, defense industries, civilian leaders, service chiefs, and operational feedback (pp. 7-14, 284-294). The book’s implied theory is not “threat causes innovation” or “civilians force innovation.” It is that innovation is a contested institutional process in which actors interpret technological and strategic change through their own interests and beliefs.

The intervening factors that matter most are organizational interests, culture, cognition/belief, civil-military relations, joint institutions, politics, industry, and war experience. Organizational interests drove the US Army’s search for relevance after Kosovo and Afghanistan; British joint institutions enabled NEC and EBAO but contributed to FRES drift; French political ambition for European leadership and industrial policy shaped Scorpion and the PP30 planning process (pp. 37-41, 67-115, 130-154, 196-282). War experience was especially important in the US and British cases: Iraq and Afghanistan corrected, accelerated, or destroyed peacetime transformation concepts (pp. 155-191, 290-292).

On RMAs and future war, the book is skeptical of revolutionary claims that privilege technology over integration. It accepts that the information revolution changed what militaries could attempt, especially in networking, precision fires, surveillance, and command and control. But it warns that RMA thinking can overshoot: the US FCS assumed that information could replace mass, protection, and physical presence, while Iraq and Afghanistan showed the continuing importance of armor, manpower, human intelligence, political context, and civil-military integration (pp. 83-99, 287, 295-299).

The book helps a student think about military effectiveness rather than mere efficiency by repeatedly asking whether changes improve performance in the field. FCS, FRES, Bowman, Félin, Scorpion, modularity, NEC, and EBAO are not judged by novelty or budget size but by deployability, survivability, interoperability, operational tempo, command effectiveness, and usefulness in actual campaigns (pp. 138-144, 150-154, 170-182, 252-260, 283-299).

For contemporary technologies, the book is especially useful for AI, autonomy, cyber-enabled C2, JADC2, precision strike, ACE, and military-civil fusion. Its strongest warning is that “system of systems” architectures can become brittle, costly, and late when technology maturity, user training, doctrinal change, and operational testing lag behind the concept. The FCS, Bowman CIP, FRES, Félin, and Scorpion cases all show that the integration layer—software, networks, human-machine interface, doctrine, acquisition authority, and battlefield adaptation—is where innovation often breaks (pp. 83-99, 138-144, 150-154, 246-260).

Seminar Placement

• Unit: Phase II — intervening factors, especially organizational transformation; also bridges Phase III because it assesses RMA and post-Cold War transformation.
• Seminar: Seminar Eight: Organizational Transformation.
• Why this book is in this seminar: It is the syllabus’s core comparative text on organizational transformation after the Cold War. It asks how armies convert technological and strategic disruption into actual force structure, doctrine, equipment, and operational practice—and why those processes produce uneven results (pp. 1-14, 283-299).
• Closest neighboring texts in the syllabus: Rosen on military innovation and organizational interests; Hone on learning systems; Hankins on culture and bureaucratic politics; Schneider and MacDonald on policy entrepreneurs and war experience; Krepinevich and Biddle on RMAs, technology, and military effectiveness.

Seminar Questions (from syllabus)

• How do we assess and identify “successful” innovations?
• Does Rosen’s distinction between wartime and peacetime innovation fail to satisfy in the post-Cold War world?
• Do the authors present a compelling argument for embracing complexity, or do theories of innovation provide a better starting point for approaching its practice?
• What transformations examined by the authors remain valuable in the GPC environment; which do not?

✅ Direct Responses to Seminar Questions

How do we assess and identify “successful” innovations?

The book’s answer is practical: an innovation is successful only if it changes how forces operate in the field, is significant in scope and impact, and increases military effectiveness. The authors adopt the military innovation literature’s baseline definition, then test “transformation” against actual operational results rather than rhetoric (pp. 7-9). On that standard, networked forces are the strongest cross-case success because all three armies improved command, control, communications, intelligence, and expeditionary interoperability, even if none achieved the full American vision of network-centric warfare (pp. 3-4, 283-284).

Success is also partial and domain-specific. US modularity improved the Army’s ability to generate deployable brigade combat teams during war, but it created concerns about combat power and reconnaissance because many heavy and light BCTs had only two maneuver battalions (pp. 67-80). British NEC and EBAO improved operational practice but Bowman CIP remained contested and FRES failed to deliver the intended medium-weight fleet (pp. 138-144, 150-154, 155-191). French Scorpion looked coherent as a future “contact force,” but it had not yet matured through major operational testing by 2012 (pp. 236-242, 252-260, 277-282).

The strongest diagnostic question is: did the change survive contact with operations? FCS did not. It depended on the assumption that superior information could replace mass, but Iraq and Afghanistan exposed the limits of battlefield knowledge, the vulnerability of medium-weight vehicles, and the continued need for protection and manpower (pp. 83-99, 113-115, 287).

Does Rosen’s distinction between wartime and peacetime innovation fail to satisfy in the post-Cold War world?

Yes, at least in its clean form. The authors explicitly argue that many innovations begin in peace and mature, change direction, or collapse in war. The US, British, and French transformations all began in relative peacetime, but operational experience shaped their actual trajectories (pp. 290-292).

The US case is the clearest. Force XXI and FCS originated before the Iraq insurgency, but war drove modularity, new COIN doctrine, MRAP acquisition, and the eventual cancellation of FCS (pp. 67-115, 291). The British case also blurs the distinction: NEC, EBAO, and FRES began as peacetime transformation programs, but Iraq and Afghanistan refocused NEC, refined effects-based thinking, and made FRES irrelevant compared to urgent protected mobility requirements (pp. 155-191, 291-292). France complicates the distinction differently: because its Afghan commitment was limited, operational experience did not force the same correction of Scorpion and the future “contact force” (pp. 277-282, 292).

So Rosen remains useful, but the post-Cold War environment is neither clean peace nor total war. It is a gray zone of expeditionary campaigns, coalition operations, defense reviews, budget churn, alliance emulation, and limited but persistent combat.

Do the authors present a compelling argument for embracing complexity, or do theories of innovation provide a better starting point for approaching its practice?

They present a compelling argument for analytical complexity, but not for abandoning theory. Their own method is “theory blending”: they use Posen, Rosen, Kier, Adamsky, and others to identify causal variables, but they reject single-factor explanations (pp. 284-285). Their cases show that no one theory can explain why FCS was pursued, why FRES failed, why EBAO survived in Britain in altered form, or why French transformation became modernization through Scorpion and PP30.

For practice, theory is a starting checklist, not a sufficient guide. Posen highlights external pressure and civilian intervention; Rosen highlights internal promotion pathways and organizational interests; cultural theories explain why Britain adopted “network-enabled” rather than “network-centric” capability; emulation theories explain why Britain and France copied some American ideas but adapted them to national constraints (pp. 285-294). The practical lesson is that innovation management must track multiple interacting variables: operational demand, organizational power, acquisition maturity, budget realism, culture, and feedback loops.

What transformations examined by the authors remain valuable in the GPC environment; which do not?

Still valuable: network-enabled command and control, modular force generation, deployable expeditionary logistics, coalition interoperability, protected mobility, tactical ISR, precision fires, mission command, and the ability to integrate military action with political effects. These remain important for GPC because peer competition increases the need for dispersed operations, joint integration, coalition operations, and resilient C2 (pp. 283-299).

Conditionally valuable: medium-weight forces. They offer deployability and operational agility, but the book shows that medium-weight platforms cannot simply replace heavy armor, protection, mass, or manpower. Iraq, Afghanistan, and the FCS/FRES experience warn against assuming that speed and information eliminate survivability requirements (pp. 83-99, 170-182, 295-296).

Less valuable or dangerous: the belief that near-perfect situational awareness can replace physical mass; quasi-scientific EBO that assumes political effects can be predicted and measured with precision; over-integrated “system of systems” programs dependent on immature networks, software, and acquisition optimism; and force designs optimized either only for COIN or only for high-end conventional war (pp. 83-99, 144-149, 287, 295-299).

Chapter-by-Chapter Breakdown

Chapter 1: Army Transformation: Imperatives and Innovations

• One-sentence thesis: Western army transformation after 1991 was driven by strategic change, information technology, and expeditionary operations, but real military innovation required organizational, doctrinal, cultural, and operational adaptation—not technology alone (pp. 1-14).
• What happens / what the author argues:
  • The authors define the post-Cold War problem: Western armies built for continental war against the Warsaw Pact now needed agility, deployability, and networked effectiveness in uncertain regional crises, failed states, terrorism, and expeditionary operations (pp. 1-4).
  • The 1991 Gulf War suggested that precision strike and ICT could transform warfare, but the authors resist technological determinism: past RMAs also required social, organizational, and doctrinal change (pp. 1-2).
  • The three armies all moved toward expeditionary, modular or medium-weight, networked forces; Britain and France also developed effects-based approaches to operations (pp. 3-4, 7-9).
  • The authors identify four factors shaping innovation: organizational interests, ideas and military culture, civilian and military leaders, and operational experience (pp. 7-14).
• Key concepts introduced:
  • military innovation
  • transformation
  • sustaining versus disruptive innovation
  • networked force
  • modular and medium-weight forces
  • effects-based operations
  • organizational interests
  • military culture
  • operational feedback
• Evidence / cases used:
  • The 1991 Gulf War as RMA signal and demonstration effect (pp. 1-2).
  • NATO and Western expeditionary operations in the Balkans, Afghanistan, and Iraq (pp. 3-7).
  • The military innovation literature: Posen, Rosen, Kier, Zisk, Adamsky, Murray, and others (pp. 7-14).
• Why it matters for SAASS 660:
  • It explicitly links technology, social construction, organizational mediation, and RMA claims.
  • It frames the book around the central SAASS question: when does technological change become warfighting effectiveness?
• Links to seminar questions:
  • The chapter defines the criteria for judging successful innovation (pp. 7-9).
  • It sets up why peacetime/wartime distinctions may be inadequate because operations continuously shape transformation (pp. 12-14).
• Notable quotes:
  • See final quotes section.

Chapter 2: Transformation from the Top Down: The United States Army, 1991–2012

• One-sentence thesis: The US Army transformed because it feared strategic irrelevance in a post-Cold War, expeditionary, airpower- and information-centric world, but its most ambitious technological project—FCS—failed because it overestimated the ability of networks and information to substitute for mass, protection, and operational reality (pp. 15-115).
• What happens / what the author argues:
  • The US Army entered the 1990s as a techno-centric Cold War force optimized for major combat in Europe and vindicated by Desert Storm (pp. 15-21).
  • General Gordon Sullivan launched the Modern Louisiana Maneuvers, Battle Labs, Force XXI, and digitization experiments to move the Army toward information-enabled warfare, but Army XXI largely enhanced the existing heavy division rather than redesigning it (pp. 21-36).
  • Kosovo created a relevance crisis. Task Force Hawk’s slow and politically fraught deployment showed that the Army was “too light to fight” and “too fat to fly,” while airpower appeared more strategically usable (pp. 37-41).
  • General Shinseki accelerated the Army After Next into the Interim Force, Stryker brigades, Objective Force, and Future Combat Systems (pp. 42-59).
  • Rumsfeld made transformation official policy but clashed with the Army over how radical transformation should be, especially in the Crusader fight and the push for lighter, more deployable forces (pp. 60-66).
  • Schoomaker’s modularity restructured the Army around brigade combat teams to generate more deployable units during Iraq and Afghanistan, but this introduced concerns over combat power, reconnaissance, and two-battalion BCT design (pp. 67-80).
  • FCS collapsed because of immature technologies, rising costs, software/network complexity, vulnerability in Iraq and Afghanistan, and the flawed premise that superior information could replace armor and mass (pp. 83-99).
  • The Army learned COIN under pressure, especially through FM 3-24 and the Iraq surge, but remained torn between high-end conventional war, irregular warfare, and future relevance in an air-sea strategic environment (pp. 102-115).
• Key concepts introduced:
  • Force XXI
  • Modern Louisiana Maneuvers
  • Army After Next
  • Stryker Brigade Combat Team
  • Future Combat Systems
  • modularity
  • network-centric warfare
  • information dominance
  • Objective Force
  • “full spectrum” force
• Evidence / cases used:
  • Gulf War deployment and logistics lessons (pp. 16-24).
  • Force XXI and Advanced Warfighting Experiments (pp. 25-36).
  • Kosovo and Task Force Hawk (pp. 37-41).
  • Stryker brigades and FCS acquisition architecture (pp. 51-59).
  • Iraq and Afghanistan operational experience, including COIN and MRAPs (pp. 67-115).
  • JTRS, WIN-T, SOSCOE, and software/network integration failures (pp. 83-99).
• Why it matters for SAASS 660:
  • The US chapter is the book’s best case for distinguishing innovation from acquisition ambition.
  • Modularity was a real organizational innovation; FCS was an ambitious technological transformation that failed to become effective warfighting capability.
• Links to seminar questions:
  • Successful innovation must be judged by deployability, combat effectiveness, and operational learning—not by the sophistication of the concept (pp. 83-99, 108-115).
  • Rosen’s peacetime/wartime distinction blurs because FCS began in peace, modularity matured in war, and COIN adaptation emerged under operational duress (pp. 67-115, 290-291).
• Notable quotes:
  • See final quotes section.

Chapter 3: Transformation in Contact: The British Army, 1991–2012

• One-sentence thesis: British transformation was quieter, more joint, more human-centric, and more operationally corrected than American transformation: NEC and EBAO survived in adapted form, while FRES was crushed by budget pressure and the urgent demands of Iraq and Afghanistan (pp. 116-191).
• What happens / what the author argues:
  • Britain entered the post-Cold War era with strong executive control over defense, weak parliamentary influence, and periodic defense reviews that gradually pushed the Army toward expeditionary and joint operations (pp. 117-121).
  • The 1991 Gulf War validated British combined-arms competence but exposed weak reconnaissance, communications, logistics, and air-land integration (pp. 121-125).
  • Bosnia, Kosovo, Sierra Leone, and Blair’s “force for good” interventionism gave the British Army a new expeditionary and humanitarian strategic role (pp. 125-130).
  • The 2003 Defence White Paper gave the British program its core transformation components: network-enabled capability, effects-based operations, and medium-weight expeditionary forces centered on FRES (pp. 130-135).
  • NEC developed through joint capability institutions and programs such as Bowman CIP, DII, Skynet 5, and battlespace digitization. Bowman improved secure communications and tracking but suffered from weight, reliability, bandwidth, training, and integration problems (pp. 137-144, 155-161).
  • EBAO was adapted from US EBO but made more British: less quasi-scientific, more philosophical, commander-led, and compatible with mission command and the maneuverist approach (pp. 144-150).
  • FRES was intended to modernize Britain’s medium-weight fleet but became overcomplicated by joint procurement, changing requirements, C-130 transportability assumptions, technological ambition, ministerial indecision, and slippage (pp. 150-154).
  • Iraq and Afghanistan validated some transformation ideas but also exposed gaps. NEC was refocused on urgent surveillance and communications, EBAO became more practical, and protected mobility UORs—Mastiff, Ridgeback, and other MRAP-style vehicles—overtook FRES (pp. 155-174).
  • Budget cuts, SDSR 2010, Army 2020, and the Levene reforms reshaped the Army again, giving services more responsibility while preserving some joint structures (pp. 175-191).
• Key concepts introduced:
  • Network-Enabled Capability
  • Bowman CIP
  • Defence Information Infrastructure
  • effects-based approach to operations
  • Comprehensive Approach
  • Future Rapid Effects System
  • Urgent Operational Requirement
  • Army 2020
  • Levene reforms
• Evidence / cases used:
  • UK defense reviews from Options for Change to SDSR 2010 (pp. 120, 175-182).
  • Gulf War, Bosnia, Kosovo, Sierra Leone, Iraq, and Afghanistan (pp. 121-130, 155-174).
  • Figures 3.1 and 3.2: officer survey data showing broad belief that ICT would change operations but skepticism that networks would be the most important future asset (p. 142).
  • Figure 3.3: support for holistic operations involving military and non-military instruments (p. 147).
  • Bowman CIP and FRES program histories (pp. 137-144, 150-154, 170-182).
• Why it matters for SAASS 660:
  • Britain shows how emulation is filtered by national culture: it borrowed US NCW/EBO ideas but translated them into NEC/EBAO to fit British mission command, techno-skepticism, and resource limits.
  • It also shows how war can correct peacetime transformation: Helmand and Iraq made operational relevance the test.
• Links to seminar questions:
  • Successful innovation can be partial: NEC and EBAO improved practice even with major technical and bureaucratic limits; FRES failed as fielded capability (pp. 155-191).
  • The case strongly supports complexity over single-cause theories because joint agencies, operations, budgets, service autonomy, civilian policy, and culture all interacted (pp. 182-191).
• Notable quotes:
  • See final quotes section.

Chapter 4: Transformation as Modernization: The French Army, 1991–2012

• One-sentence thesis: French transformation became modernization: a coherent but contested effort to preserve French military relevance and European leadership through jointness, expeditionary forces, network-enabled operations, and Scorpion, while avoiding wholesale imitation of the American transformation model (pp. 192-282).
• What happens / what the author argues:
  • The French Army approached transformation with ambition and skepticism: it wanted a modern, networked, deployable force, but French military thought remained deeply aware that land warfare is about people, politics, and legitimacy, not machines alone (pp. 192-196).
  • The 1991 Gulf War was a strategic shock because France realized its forces were not adequately connected, interoperable, or prepared for major coalition operations (pp. 198-205).
  • Chirac’s “Model 2015” was revolutionary in two respects: professionalization and expeditionary force projection. But it left unresolved problems in infrastructure, budgets, jointness, and force modernization (pp. 205-212).
  • The late 1990s and early 2000s produced planning tools such as PP30 and increased joint thinking, but cohabitation, budgets, service rivalries, and legacy systems slowed reform (pp. 212-227).
  • French transformation after 2001 was catalyzed by US transformation and Afghanistan, but France deliberately pursued a federation of bottom-up initiatives rather than a US-style top-down grand design (pp. 227-233).
  • The Army’s 2005 blueprint organized transformation around network-enabled capability, expeditionary warfare, and effects-based operations. This produced NEB, FTF 2025, Scorpion, the Future Contact System, and “synergy of effects” doctrine (pp. 233-242).
  • French planning from 2006-2012 was shaped by PP30, DGA, industry, the central staff, service cultures, and political ambition. Figure 4.3 depicts the French planning process linking officers of service coherence, officers of operational coherence, DGA force-system architects, leadership committees, and PP30 (p. 246).
  • Table 4.6 captures the human-centric doctrinal core: French land doctrine emphasizes that technology can protect and facilitate, but the individual soldier remains central in dense human environments (p. 252).
  • Félin revealed the tension between industrial/technical coherence and operational usability: it connected the soldier to networked combat but was criticized as heavy, bulky, and not always suited to Afghan terrain (pp. 260-261).
  • Afghanistan enhanced French expeditionary capacity but did not force a deep reckoning because France’s commitment was limited and Scorpion had not yet been seriously tested in war (pp. 277-282).
• Key concepts introduced:
  • Model 2015
  • PP30
  • DGA
  • NEB
  • Scorpion
  • Future Contact System
  • Félin
  • framework nation
  • strategic axis
  • synergy of effects
  • contact force
• Evidence / cases used:
  • The 1991 Gulf War and French force-projection weakness (pp. 198-205).
  • 1994 White Paper, Chirac reforms, professionalization, and Model 2015 (pp. 198-212).
  • PP30 and joint capability planning (pp. 220-222, 242-246).
  • NEB exercises, Scorpion, VBMR, EBRC, VBCI, Leclerc modernization, Félin, and DGA/industry dynamics (pp. 233-260).
  • Sarkozy’s 2008 White Paper, strategic axis, NATO reintegration, and Afghanistan/Kapisa experience (pp. 255-282).
• Why it matters for SAASS 660:
  • France shows that transformation can be politically and culturally rebranded as modernization while still pursuing many RMA-associated capabilities.
  • It is also the strongest case for industry and state planning as intervening variables in military innovation.
• Links to seminar questions:
  • French transformation’s success remained uncertain by 2012 because Scorpion had coherence and political support but lacked operational maturation (pp. 277-282).
  • The case reinforces the book’s complexity argument: political ambition, European leadership, industrial policy, jointness, service culture, and limited operational feedback all interacted (pp. 242-282).
• Notable quotes:
  • See final quotes section.

Chapter 5: Conclusion: Innovation and Military Power

• One-sentence thesis: Military power depends on how states mobilize, organize, and employ resources; therefore, army transformation must be understood as a complex, iterative process linking humans, machines, organizations, politics, and operational experience (pp. 283-299).
• What happens / what the author argues:
  • The authors identify networked forces as the clearest cross-case innovation; British and French effects-based doctrine as another significant innovation; and medium-weight integrated ground systems as the most ambitious but least successful area (pp. 283-284).
  • They argue for “theory blending”: military innovation cannot be explained by external threats, organizational interests, culture, civilian intervention, leaders, war experience, or emulation alone (pp. 284-285).
  • Interests and ideas both matter. US organizational relevance drove FCS and modularity; British “force for good” and the special relationship shaped expeditionary transformation; French European leadership and relevance shaped Scorpion and joint modernization (pp. 285-288).
  • Individuals matter at key junctures, but only inside institutional contexts: Sullivan, Shinseki, Schoomaker, Gates, Petraeus, Blair, Cook, Fulton, Parry, Dannatt, Sarkozy, and French planning actors all shaped innovation pathways (pp. 288-290).
  • War and peace blur. The US and Britain began transformation in peace, but Iraq and Afghanistan forced adaptation. France remained in a war/peace gray zone because limited operations did not discipline Scorpion the same way (pp. 290-292).
  • Emulation matters, but it is partial. Britain and France borrowed US ideas through military cooperation, alliance ties, and the wider Atlantic defense community, not simply because NATO ACT transmitted them (pp. 292-294).
  • Future military power requires integrating land forces with joint, multinational, and civilian partners while avoiding both techno-utopian and anti-technology extremes (pp. 295-299).
• Key concepts introduced:
  • theory blending
  • emulation
  • absorption capacity
  • future military power
  • joint integration
  • multinational integration
  • Comprehensive Approach
  • “Bonsai armies”
• Evidence / cases used:
  • Comparative synthesis across the US, British, and French cases (pp. 283-299).
  • Iraq and Afghanistan as operational correctives (pp. 290-292, 295-299).
  • US transformation diffusion to Britain and France (pp. 292-294).
  • Future challenges: Air-Sea Battle, Libya, Mali, NATO Smart Defence, Connected Forces Initiative, and civil-military integration (pp. 297-299).
• Why it matters for SAASS 660:
  • The conclusion directly answers the course’s central question: technology changes possibilities, but military effectiveness depends on the institutional ability to connect machines, people, doctrine, and political purpose.
• Links to seminar questions:
  • It gives the strongest direct answer on complexity, success, and the limits of peacetime/wartime innovation categories (pp. 283-299).
• Notable quotes:
  • See final quotes section.

Theory / Framework Map

• Central problem: How did the US, British, and French armies transform after the Cold War, and why did similar strategic and technological pressures produce different innovation pathways and outcomes?
• Dependent variable(s):
  • Army transformation outcomes.
  • Specific military innovations: networked forces, modular/medium-weight expeditionary force structures, effects-based or holistic operational approaches.
  • Military effectiveness as expressed in deployability, command effectiveness, survivability, operational agility, interoperability, and campaign performance.
• Key independent variable(s):
  • Strategic change after the Cold War.
  • Information and communication technologies.
  • Organizational interests and service relevance.
  • Ideas, culture, and identity.
  • Civilian and military leadership.
  • Operational experience.
  • Joint institutions.
  • Defense industry and procurement systems.
  • Alliance emulation, especially of the United States.
  • Budgets and resource constraints.
• Causal mechanism(s):
  • Strategic shock creates pressure to change.
  • Technology creates perceived opportunity.
  • Organizational actors interpret opportunity through institutional interests and culture.
  • Leaders create, protect, accelerate, or terminate innovation pathways.
  • Joint and procurement institutions translate ideas into programs.
  • Operations test, correct, or invalidate concepts.
  • Budget pressure forces prioritization and sometimes kills programs.
  • Alliance relationships diffuse ideas but national cultures adapt them.
• Scope conditions:
  • Advanced Western armies.
  • Post-Cold War expeditionary environment.
  • Armies operating in coalition settings.
  • Information-age transformation programs before the full onset of today’s drone, AI, cyber, and peer-contested sensor environment.
• Rival explanations or competing schools:
  • Technological determinism: ICT and precision strike drove transformation.
  • Posen-style external-threat/civilian-intervention theories.
  • Rosen-style internal military leadership and promotion-path theories.
  • Cultural theories emphasizing strategic culture and military identity.
  • Acquisition/industrial explanations emphasizing firms, procurement agencies, and budgets.
  • Operational learning theories emphasizing wartime adaptation.
• Observable implications:
  • If technology were sufficient, all three armies would converge more closely and successful fielded systems would follow from technical promise.
  • If civilian intervention were decisive, civilian leaders would consistently define the direction and content of innovation.
  • If organizational interests dominate, services will preserve roles, missions, and budget share even while adopting transformation language.
  • If operational experience matters, war should redirect or invalidate peacetime transformation programs.
  • If emulation is partial, Britain and France should borrow US concepts but translate them into national forms.
• What would weaken the author’s argument?
  • Evidence that FCS/FRES failed primarily because of isolated acquisition mismanagement rather than deeper conceptual, operational, and institutional mismatch.
  • Strong evidence that NEC/EBAO/Scorpion had negligible operational effect.
  • Evidence that civilian intervention alone drove transformation outcomes across all three cases.
  • A case showing comparable transformation success without doctrinal, organizational, training, or operational adaptation.
  • Better measurement showing that the transformed armies were no more militarily effective than their Cold War predecessors.

Key Concepts & Definitions (author’s usage)

• Military innovation: A significant change in how a military functions in the field, with meaningful scope and impact, associated with increased military effectiveness (pp. 7-8).
• Transformation: A broad post-Cold War process of changing force structure, doctrine, equipment, and concepts to exploit new technologies and meet new strategic demands; not necessarily a single program or endpoint (pp. 1-7).
• Sustaining innovation: Innovation that improves traditionally valued ways of war and fits existing organizational interests (pp. 8-9).
• Disruptive innovation: Innovation that improves undervalued or new ways of war and challenges existing organizational interests, doctrine, and identity (pp. 8-9).
• Networked force: A force whose sensors, shooters, commanders, platforms, and information systems are connected to increase situational awareness, speed, precision, and coordination (pp. 3-4, 33-36, 137-144, 233-236).
• Network-centric warfare: The more ambitious US concept that networking itself becomes the center of warfighting advantage; strongest in the US transformation discourse (pp. 60-64, 130-144).
• Network-enabled capability: The British and French more modest concept that networks enable better operations without replacing human judgment, mission command, or national doctrine (pp. 134-144, 233-236, 294).
• Modularity: Reorganizing forces into more standardized, deployable, self-contained formations, especially brigade combat teams in the US case (pp. 67-80).
• Medium-weight force: A force positioned between heavy armor and light infantry, intended to improve deployability while retaining enough protection, mobility, and firepower for serious operations (pp. 3, 51-59, 150-154, 236-239).
• Effects-based operations: A planning approach focused on achieving desired military and political effects rather than simply destroying enemy forces or seizing terrain (pp. 144-150, 239-242).
• Effects-based approach to operations: The British adaptation of EBO into a less mechanical, more commander-led way of thinking compatible with mission command (pp. 145-150).
• Jointness / jointery: Organizational structures, doctrine, and practices that integrate the services. It is a major force in Britain and France, less decisive in the US Army’s own innovation process (pp. 9-10, 128-137, 196-198, 220-222, 287-288).
• Organizational interests: A service’s desire to preserve missions, budgets, autonomy, identity, and relevance. These interests can drive innovation or block disruptive change (pp. 9-10, 285-288).
• Operational experience: War and deployments as feedback mechanisms that test doctrine, expose gaps, validate concepts, or force adaptation (pp. 12-14, 290-292).
• Emulation: Partial copying of another military’s innovations, filtered through national resources, culture, alliances, and absorption capacity (pp. 292-294).
• Contact force: The French concept for forces that close with or otherwise establish contact with adversaries, later organized through Scorpion and related programs (pp. 236-239).

Key Arguments & Evidence

• Technology creates opportunity, not automatic innovation. The 1991 Gulf War suggested a major information-age RMA, but the authors stress that technology had to be absorbed through social, organizational, and doctrinal change (pp. 1-2, 7-14).
• US transformation was driven by relevance anxiety as much as by technology. Kosovo and Task Force Hawk raised doubts about the Army’s utility compared to airpower, helping propel Shinseki’s push for Stryker and FCS (pp. 37-41, 42-59).
• The FCS failed because its core concept outran operational and technological reality. It required immature networks, software, radios, unmanned systems, and vehicles, while Iraq and Afghanistan showed that information could not replace protection, mass, or human understanding (pp. 83-99, 113-115, 287).
• British transformation succeeded most where it adapted US ideas to British culture. NEC and EBAO survived because Britain translated NCW and EBO into more modest, human-centric, mission-command-compatible forms (pp. 137-150, 294).
• British FRES shows how joint procurement and future-force ambition can undermine an Army’s operational needs. FRES began as the Army’s centerpiece medium-weight program but became delayed, overcomplicated, and irrelevant to urgent protected mobility requirements in Iraq and Afghanistan (pp. 150-154, 170-182).
• French transformation was a modernization project tied to political relevance. The Gulf War, European leadership ambitions, NATO/US interoperability, professionalization, PP30, DGA, and Scorpion all shaped a coherent but contested effort to maintain France as a capable framework nation (pp. 192-282).
• War is a powerful corrective—but only if exposure is deep enough. Iraq and Afghanistan reshaped US and British transformation; France’s more limited commitment provided relevance and some adaptation but did not force the same reckoning with Scorpion (pp. 277-282, 290-292).
• Future military power requires integration across human-machine, joint, coalition, and civil-military boundaries. The book’s final warning is that technology-heavy and human-only approaches are both insufficient (pp. 295-299).

Barriers, Determinants, and Causal Logic

What drives innovation?

Innovation is driven by a combination of strategic shock, technological opportunity, organizational self-interest, leaders, and operational experience. The end of the Cold War removed the old continental-war template. The 1991 Gulf War showed the apparent promise of precision strike and ICT. Kosovo raised questions about the relevance of land power. Iraq and Afghanistan exposed the limits of high-tech transformation and forced adaptation toward COIN, protected mobility, tactical ISR, and civil-military integration (pp. 1-14, 37-41, 67-115, 155-191, 290-292).

What blocks innovation?

The main blockers are bureaucratic inertia, service parochialism, cultural commitments, acquisition complexity, immature technology, budget instability, and weak operational feedback. The US Army’s techno-centric conventional culture sustained FCS beyond what operations justified. British joint procurement diluted Army control over FRES. French DGA/industry influence made Scorpion coherent but risked disconnecting design from operational users, as Félin showed (pp. 83-99, 150-154, 246-260, 287-288).

Which actors matter most?

Senior military leaders matter because they can create protected innovation channels: Sullivan’s Modern Louisiana Maneuvers, Shinseki’s FCS push, Schoomaker’s Task Force Modularity, Dannatt’s FRES advocacy, Fulton’s NEC work, and Parry’s EBAO development (pp. 25-36, 42-59, 67-80, 137-150, 288-290). Civilian leaders matter when they provide strategic purpose, resources, or termination authority: Blair and Cook gave Britain the “force for good” logic; Rumsfeld shaped US transformation politics; Gates killed the FCS vehicle program; Sarkozy reframed French security policy and NATO posture (pp. 60-66, 97-99, 125-130, 255-282, 288-290).

What role do organizations, service cultures, bureaucracies, politicians, scientists, firms, and operational experience play?

Organizations translate strategic and technological change into programs. Service cultures filter what counts as legitimate warfighting. Bureaucracies allocate authority and can either protect innovation or cause drift. Politicians define strategic ambition and budget constraints. Firms and procurement agencies shape what gets built, often by privileging technical coherence and exportability. Operational experience supplies the hardest test: it exposes whether programs actually solve field problems (pp. 7-14, 83-99, 138-154, 246-260, 290-299).

What distinguishes success from failure?

Success requires a real operational problem, a feasible technological solution, doctrinal adaptation, training, organizational absorption, political support, and budget discipline. Failure occurs when the concept depends on unproven assumptions, cannot survive operational testing, or becomes detached from the user. FCS failed because its “information replaces mass” logic was too brittle. FRES failed because it did not arrive when the Army needed protected mobility. NEC and EBAO succeeded more modestly because they adapted, narrowed, and survived operational use (pp. 83-99, 138-154, 155-191, 283-299).

⚖️ Assumptions & Critical Tensions

• Technology vs organization: The book assumes technology matters, but only through institutions. FCS is the cautionary case: powerful technology claims did not produce military effectiveness without mature networks, doctrine, and operational fit (pp. 83-99).
• Information vs mass: The US Army’s assumption that superior information could replace armor, manpower, and protection was exposed by Iraq and Afghanistan (pp. 83-99, 287).
• Expeditionary agility vs survivability: Medium-weight forces promise deployability but can be too vulnerable for IEDs, urban combat, and close terrain (pp. 93-99, 170-174, 295-296).
• Centralization vs decentralization: Joint institutions can impose coherence, but they can also detach capability development from service expertise. Britain’s FRES and France’s PP30/Scorpion show both sides (pp. 150-154, 246-260, 280).
• Civilian intervention vs military autonomy: Civilian leaders sometimes provide strategic direction or force correction, but most detailed innovation work comes from military organizations and specialist communities (pp. 288-290).
• Doctrine vs matériel: The book treats doctrine as a genuine site of innovation. British EBAO and French “synergy of effects” matter because they shaped planning, not just procurement (pp. 144-150, 239-242).
• Warfighting effectiveness vs political/ethical constraints: British and French effects-based thinking and comprehensive approaches aimed to connect tactical action to political outcomes, especially in humanitarian, stabilization, and COIN contexts (pp. 125-130, 144-150, 239-242, 295-299).
• National ambition vs resources: France wanted European leadership; Britain wanted to fight alongside the US; the US Army wanted global relevance. In each case, budgets constrained what ambition could become (pp. 175-182, 265-282, 297-299).
• Emulation vs adaptation: Britain and France borrowed US ideas but changed them to fit national cultures, resource constraints, and alliance needs (pp. 292-294).

Critique Points

• Strongest contribution: The book’s strongest contribution is its comparative, empirically rich account of transformation as a process rather than an outcome. It does not collapse innovation into technology, procurement, or rhetoric; it follows how ideas become programs and how programs survive or fail under operations and budgets (pp. 1-14, 283-299).
• Biggest blind spot: The book sometimes uses “transformation” broadly enough that partial, incomplete, or failed changes can still be grouped under the same umbrella. That is analytically useful, but it risks softening the threshold between real innovation and attempted innovation.
• Where the evidence is strongest: The evidence is strongest in the US FCS/modularity case, the British NEC/EBAO/FRES case, and the French PP30/Scorpion/DGA case. These sections tie concepts, institutions, procurement, and operations together in concrete detail (pp. 67-115, 137-191, 220-282).
• Where the evidence is thin or contestable: The book is less strong in measuring net military effectiveness. It shows that armies changed and that some capabilities improved, but it does not offer a rigorous comparative metric for how much more effective each army became. The French case is also partly prospective because Scorpion had not yet matured operationally by the book’s endpoint (pp. 277-282).
• What kind of evidence would change your mind: Detailed operational performance data showing that NEC, modularity, EBAO, NEB, or Scorpion decisively improved—or failed to improve—mission outcomes would sharpen the innovation assessment. A stronger counterfactual showing what would have happened without FCS, FRES, or Scorpion would also clarify whether these programs represented necessary experimentation or avoidable waste.

Policy & Strategy Takeaways

• Do not confuse innovation with acquisition. A fielded, usable, trained, doctrinally integrated capability matters more than a visionary program.
• Build transformation around operational problems, not future-war aesthetics. FCS and FRES show the danger of designing around imagined futures while current wars expose different requirements.
• Treat networks as enablers, not magic. Bandwidth, interoperability, user training, cyber resilience, and human cognition determine whether networked forces improve combat effectiveness.
• Preserve feedback loops between operators and designers. Félin, Bowman, FRES, and FCS all show what happens when user experience lags behind engineering ambition.
• Make modularity honest about tradeoffs. More deployable units can come at the cost of combat power, reconnaissance, sustainment, or command flexibility.
• Emulate selectively. Borrowing from the dominant military power is rational, but absorption capacity, culture, budgets, and operational needs must shape adaptation.
• Future land power requires integration with joint, coalition, and civilian partners. The book’s final argument is not “more land power” but better-integrated land power (pp. 297-299).

660 Final Brief Utility

• Most useful historical analogies or cases from this book:
  • US FCS: best analogy for AI/JADC2/autonomy overreach when a system-of-systems concept depends on immature networks, software, sensors, and assumptions about perfect awareness (pp. 83-99).
  • British FRES: best analogy for a future-force program overtaken by urgent operational requirements and budget pressure (pp. 150-154, 170-182).
  • French Scorpion/Félin: best analogy for technically coherent modernization that risks user-interface and operational-fit problems when industry and procurement dominate design (pp. 246-260, 277-282).
  • Kosovo/Task Force Hawk: useful analogy for service relevance shocks in an era where another domain appears to deliver political results faster and cheaper (pp. 37-41).
  • British EBAO: useful analogy for adapting a foreign doctrine into national culture rather than copying it wholesale (pp. 144-150).
• What emerging idea, technology, or technological system this book helps analyze:
  • AI-enabled C2 and decision advantage.
  • JADC2 / ABMS / Project Convergence-style networks.
  • Autonomous teaming and unmanned systems.
  • Precision strike plus sensor fusion.
  • ACE and distributed operations.
  • Contested logistics and expeditionary posture.
  • Military-civil fusion and defense industrial ecosystems.
• Shapers of events / adoption:
  • Strategic shock.
  • Operational embarrassment.
  • Service relevance and budget competition.
  • Senior leader sponsorship.
  • Joint institutions.
  • Defense industry and procurement agencies.
  • Alliance interoperability.
  • War feedback.
  • National strategic culture.
• Barriers to integration:
  • Immature technology.
  • Software and network complexity.
  • Bandwidth and interoperability limits.
  • Overweight or unusable equipment.
  • Unclear doctrine.
  • Weak training.
  • Service parochialism.
  • Budget instability.
  • Civil-military and interagency friction.
• Determinants of success or failure:
  • Clear operational use case.
  • Mature enough technology.
  • Organizational ownership.
  • Adaptive doctrine.
  • User feedback.
  • Realistic budget and timeline.
  • Compatibility with coalition operations.
  • Ability to survive wartime correction.
• Limits of the analogy:
  • The book covers Western armies from 1991-2012, not today’s drone-saturated, cyber-contested, AI-enabled, peer-threat environment.
  • Iraq and Afghanistan dominate the operational correction mechanism; future GPC may involve more lethal ISR-strike complexes, electronic warfare, space denial, and homeland cyber pressure.
  • The cases are land-force heavy; applying them to air, space, cyber, or maritime innovation requires care.
• Best way to use this book in a 20-minute SAASS 660 brief:
  • Use it as the “integration and adoption” framework. Pair one emerging technology with one historical case: for example, AI-enabled JADC2 with FCS. Argue that the decisive question is not whether the technology is revolutionary, but whether institutions can convert it into fielded, trained, resilient, doctrinally integrated warfighting effectiveness under budget and operational pressure.

⚔️ Cross-Text Synthesis (SAASS 660)

McNeill / Evron & Bitzinger / King

This book reinforces McNeill’s broad claim that technology and power are historically linked, but it rejects any simple “technology causes power” reading. The armies with the greatest resources still had to solve organizational, doctrinal, and cultural problems before technology became military effectiveness (pp. 1-14, 283-299). Against Evron and Bitzinger’s military-civil fusion frame, the French DGA/Scorpion case is especially useful: industry and state planning can support modernization, but they can also bias design toward exportability, technical coherence, and procurement logic rather than user needs (pp. 246-260). For King’s AI/automation concerns, FCS is a pre-AI warning: autonomy and information systems do not remove the need for human judgment, protection, and political context (pp. 83-99, 295-299).

Posen / Rosen / Hone

The book complicates Posen. Civilian intervention matters—Gates killing FCS, Blair giving Britain a “force for good” purpose, Sarkozy reframing French strategy—but civilians do not consistently originate or manage the detailed innovation (pp. 125-130, 255-282, 288-290). It reinforces Rosen by showing the importance of internal military leaders and promotion-path politics, but it also complicates Rosen’s peacetime/wartime distinction because transformation began in peace and matured or failed in war (pp. 288-292). It also speaks strongly to Hone: learning systems, experimentation, feedback, and operational adaptation matter. The US Modern Louisiana Maneuvers, British EBAO refinement, and wartime MRAP/UOR adaptation all show that innovation is a learning architecture, not just a decision (pp. 25-36, 144-150, 155-174).

Mackenzie / Bridger / Hankins / Farrell-Rynning-Terriff / Schneider-MacDonald

Against a deterministic account of technology, this book strongly reinforces Mackenzie’s social-construction logic. “Accuracy,” “networking,” and “transformation” are not neutral technical facts; they are built through organizations, cultures, users, budgets, and political meanings (pp. 83-99, 138-154, 246-260). Bridger is less directly relevant, but the British and French effects-based and comprehensive-approach discussions show that political and ethical constraints shape doctrine, especially when force is used for humanitarian, stabilization, or population-centric purposes (pp. 125-130, 144-150, 239-242). Hankins is relevant because culture and bureaucratic politics shape what technologies become: FCS, FRES, and Scorpion all reflect communities fighting over relevance, expertise, and authority. Schneider and MacDonald’s policy entrepreneurs map well onto this book’s leaders: Sullivan, Shinseki, Schoomaker, Fulton, Parry, Dannatt, Sarkozy, Gates, and Petraeus all function as innovation champions at key points (pp. 288-290).

Krepinevich / Biddle

The book challenges hard RMA determinism. It agrees that post-Cold War information technologies mattered, but it shows that their effects were evolutionary, uneven, and socially mediated (pp. 1-14, 295-299). It aligns with Biddle’s skepticism about Gulf War lessons: the authors repeatedly stress skill, organization, doctrine, and human performance rather than technology alone. FCS is almost a Biddle-compatible cautionary tale: information superiority could not replace the modern system’s demands for cover, concealment, dispersion, suppression, combined arms, and competent execution (pp. 83-99, 295-296).

❓ Open Questions for Seminar / Briefing

1. If FCS failed, was it a failed innovation or a necessary experiment that generated useful spin-offs for later networked warfare?
2. Does modularity count as a military innovation if it increases deployability but may reduce combat power at the brigade level?
3. Did Britain’s human-centric translation of NCW into NEC represent wisdom, limited resources, or both?
4. How much operational exposure is necessary before a future-force concept receives meaningful feedback? Did France avoid failure or merely postpone testing?
5. Are joint institutions more likely to improve innovation by enforcing integration, or weaken it by separating capability design from service users?
6. What is the right balance between preparing for current wars and avoiding Gates’s “next-war-itis” critique?
7. How should we assess innovations whose effects are mostly enabling—C2, interoperability, logistics, doctrine—rather than directly destructive?
8. What is the contemporary equivalent of FCS: AI-enabled C2, autonomous swarms, JADC2, long-range precision fires, or something else?

✍️ Notable Quotes & Thoughts

• “technology alone” / “revolutionary change” (p. 2).
  This captures the book’s anti-determinist core: technology matters, but it does not become an RMA without social, doctrinal, and organizational change.
• “too light to fight, too fat to fly” (pp. 21, 41).
  This is the US Army’s post-Cold War dilemma in one phrase: deployability and combat power pulled in opposite directions.
• “near perfect situational awareness” (p. 287).
  This phrase marks the FCS failure point: the Army’s belief in information superiority became a conceptual trap.
• “force for good” (pp. 127-130).
  This phrase explains the British shift from Cold War territorial defense toward expeditionary intervention and stabilization.
• “Bonsai” armies (p. 298).
  This is the book’s warning for austerity-era force design: small, elegant forces can become operationally useless if cuts are not tied to strategic choices.