Top 5 Inventions that came too Early...

The first case study uses Rene Lorin's 1913 ramjet idea to show how a promising invention can wait on metallurgy and materials science.

A procurement-law section explains why sensible cost-growth triggers still collide with contractors, lobbyists, alternatives, and management incentives.

The U.S. Army's Future Combat Systems case contrasts a concrete common-chassis proposal with a broader modernization program whose vagueness avoids firm promises.

A shipyard manager's scheduling rule and prewar aircraft practice illustrate why platforms should not be promised before their core machinery works.

The EFV-to-ACV replacement story sets a costly new amphibious vehicle against a much larger fleet of aging AAV7s and a constrained Marine Corps budget.

The EFV becomes a lesson in how adding requirements builds a program's political coalition until its scale begins to endanger other priorities.

The rationale for dispensing with a long-range amphibious vehicle rests on unopposed landings or other services clearing coastal missile threats first.

The Zumwalt discussion separates the destroyer from its immature railgun and asks whether only a nuclear surface combatant could sustain the weapon's electrical demand.

A critique of Zumwalt's peripheral launch cells shows how insisting that every feature be novel can turn an interesting destroyer into a perceived failure.

The nuclear-pumped laser at the heart of Project Excalibur illustrates the gap between a dramatic missile-defense concept and materials capable of making it work.

Autonomous tungsten interceptors and their sensor network make Brilliant Pebbles the SDI proposal presented as closest to conventional deployment.

The closing case separates Littoral Combat Ship execution from modular-warship theory and points to Denmark's older StanFlex system as a counterexample.

A hypothetical U.S.-Danish development path uses StanFlex interfaces and Danish contract discipline to imagine a more useful American frigate.