Built to Mission vs Spec

“Built to mission vs. built to spec” is one of the recurring threads Kyle pulls out of Skunk Works (Ben R. Rich), and the book’s single most-repeated principle: “Trust the customer to know the problem but not the solution” — i.e., build to the mission, not to the spec. Building to spec rewards adherence to bureaucracy and produces “exquisite platforms”: impressive, expensive single-points-of-failure that get invalidated once warfare evolves around them. Kyle’s inline notes restate this twice — “Build to the mission” against the automated stealth-fighter program, and “Built to spec vs built to missions — again, focused on exquisite platforms” against the B-2 contest.

The thread connects directly to the book’s other arcs: the Founders Mentality / missionary-vs-mercenary drift (Kelly Johnson’s founder-led innovation vs. “build for the buck rather than the mission”), Managed Monopoly (anti-Darwinian primes rewarded for adherence rather than results), and the modern thesis that Anduril is the skunk-works answer — buying off-the-shelf where possible and building custom only where the mission requires it, rather than gold-plating to a spec.

Where this appears

• Skunk Works — core thread: “trust the customer to know the problem but not the solution”; built-to-spec produces exquisite single-point-of-failure platforms, built-to-mission wins