Innovation is the process of turning a new idea into something that delivers value to a real user — not the idea itself. Merriam-Webster draws the line cleanly: invention is a device or process originated after study and experiment, something that did not previously exist, while innovation can also mean a change made to an existing product or field. The dictionary's own example runs from the first telephone (invention) to the first smartphone (innovation).
That distinction carries real weight in defense technology, where the federal government funds thousands of prototypes and fields a much smaller number of systems. A working definition matters here because the word has become a budget justification in its own right. Innovation, used precisely, is a testable claim: that a new capability will reach an operator and change what the operator can do. Used loosely, it is a label applied to anything a program office wants funded.
This piece sets out a definition built on documented usage, then tests it against the defense research and development system, where the gap between invention and fielded capability is a standing institutional problem.
What separates invention from innovation?
Invention is the act of creating something that did not exist before. Innovation is the act of making that creation count — delivering it, scaling it, and changing practice with it. According to Merriam-Webster, the two words overlap semantically but are quite distinct: invention most often means a device, contrivance, or process originated after study and experiment, while innovation can refer to something new or to a change made to an existing product, idea, or field.
The dictionary's telephone example is useful because it shows the boundary is not a wall. The first cellular telephone could be called either an invention or an innovation, depending on whether the writer treats the underlying device or the change to an existing field as the subject. What stays constant is the value test. An invention that never reaches a user is a laboratory result. An innovation has changed how someone actually works. We covered a connected angle in How Milestone C Decides Whether a Weapons Program Reaches Production.
How do practitioners define the innovation process?
Executives and researchers tend to define innovation as a process rather than an event. According to Harvard Division of Continuing Education's Professional & Executive Development program, innovation is not just an idea or a tool but a process that guides organizations through developing products or services that deliver value in new ways — the ability to conceive, develop, deliver, and scale new offerings, and to take an idea from inception to impact.
That framing has three practical consequences. First, delivery is part of the definition, not a separate phase. Second, scaling is part of the definition, which is why a single working prototype does not qualify. Third, the process is repeatable: Harvard DCE describes stages of understanding the problem, exploring multiple candidate solutions in parallel, and then implementing — checking whether the features, design, technology, and operations can make the solution real and sustainable.
The parallel exploration point deserves emphasis. The Harvard DCE account quotes instructor Ben Little on the value of holding several good ideas open at once, preserving the option to move in more than one direction. Defense acquisition has an equivalent instinct: competitive prototyping exists precisely because committing to one design too early is expensive to reverse.
Why does the defense sector struggle to convert invention into innovation?
The defense research system is unusually good at invention and structurally strained at delivery. Requirements, funding cycles, and test regimes sit between a working prototype and a fielded system, and each can kill a promising design without any technical failure. The result is a conversion problem that has its own name in the trade press and in government reports.
The mechanism is documented elsewhere on this site. The Valley of Death: Why Promising Defense Prototypes Struggle to Become Fielded Gear examines the funding gap between research demonstrations and program-of-record money. How Milestone C Decides Whether a Weapons Program Reaches Production explains the formal gate — the approval point where a program demonstrates its design is ready for production — that stands between a prototype and procurement. For related coverage, see The Valley of Death: Why Promising Defense Prototypes Struggle to Become Fielded Gear.
The honest reading is that the Pentagon's innovation problem is not a shortage of ideas. It is a shortage of completed processes. An idea that dies at the prototype stage is an invention that never became an innovation, by the definition above.
What does genuine innovation look like in defense R&D?
Applying the definition produces a simple test with three questions. Has the capability reached an operator? Has it changed practice? Can it be sustained at scale? A program that answers all three is an innovation regardless of how mundane it looks in a press release. A program that answers none of them is a research effort, however exotic its technology.
Several areas covered by this publication sit at different points on that path. Directed-energy work is a clear case: as Laser Weapons at Sea documents, lower-power systems have reached ships while higher-power thresholds remain engineering targets — fielded at one level, still invention-adjacent at another. Software acquisition is the opposite case: The Software Acquisition Pathway Explained describes a deliberate restructuring of the process itself, an innovation in how the department buys rather than in what it buys.
Flight testing illustrates the boundary most sharply. Hypersonic Glide Bodies: What Actually Flew Versus What Was Claimed addresses the gap between a demonstrated flight and a claimed capability. The distinction matters because a test event is evidence of invention; a fielded, sustainably supported capability is evidence of innovation. Confusing the two is how rebranding happens.
How can a reader tell innovation from buzzword rebranding?
The vocabulary of innovation is easy to acquire and hard to verify. A disciplined reader can apply four checks drawn from the definition itself.
- Value to a named user. Real innovation claims identify who uses the capability and what changes for them. A claim with no user is a research objective at best.
- Delivery, not intention. The Harvard DCE definition places delivery and scaling inside the process. Language that stops at "exploring" or "developing" describes an earlier stage, not an innovation.
- Change to an existing field. Merriam-Webster's second sense of innovation — a change made to an existing product or field — gives a checkable standard. If nothing in current practice would be different, the word is decoration.
- Process evidence. Genuine innovation efforts can name their stages: problem definition, competing solutions, implementation. A slide that jumps from concept to transformation has skipped the process that makes the word mean anything.
None of this makes the buzzword usage fraudulent in a legal sense. It makes it uninformative. The reader's job is to ask which sense of the word is in play.
What this means for watching defense innovation claims
Our analysis is that the working definition does its best work as a filter on announcements. When a company or service claims innovation, the useful questions are: which user, what delivered capability, what change to existing practice, and what evidence the process continued past the prototype. Claims that cannot answer those questions are describing invention or aspiration — legitimate activities, but different ones.
The evidence assembled here supports one conclusion and leaves one gap. Supported: innovation, as the term is used by Merriam-Webster and by Harvard DCE's practitioners, is a completed process of delivery and scaling, not the generation of novelty. Unstated in the public record: how any specific defense program will fare at the conversion points where prototypes become programs. That is knowable only from program documents as they are released, and this publication will assess those claims on the definition above when they arrive.
