The U.S. military space business is being pushed toward a blunt new standard: deliver useful capability faster, then improve it later.
That message is coming most clearly from the Space Force, where senior leaders have been describing speed not as a procurement preference, but as an operational requirement. In a fast-moving threat environment, the old bargain of waiting years for a more complete system is losing ground to a different one: put something workable in orbit, learn from it, and upgrade in increments.
A doctrine, not a slogan
Chief of Space Operations Gen. B. Chance Saltzman has put the shift in direct terms. At a November 2025 event hosted by the Center for Strategic and International Studies and the Hudson Institute, he said cost, schedule, and performance still matter, but that speed is now “first amongst equals,” according to National Defense Magazine.
Saltzman’s summary of the new posture was even sharper: “A capability that is good enough and ready now will always be better than a perfect solution that arrives too late for the fight, or one that never arrives at all.”
That line captures the pressure now facing satellite builders. The Space Force is moving away from a fixed, all-or-nothing acceptance model and toward smaller, more frequent delivery increments. The goal is to field a minimum viable capability sooner, then improve it with lessons from real-world operations.
Why the schedule matters
The strategic logic is simple. Space systems can take years to design, contract, test, and field. Threats do not move on the same schedule.
Saltzman has argued that long development timelines can leave the military building systems against assumptions that are already outdated by the time the hardware reaches operators. GovCIO Media & Research reported that he framed the problem around the military’s observe, orient, decide, and act loop, warning that if decision and action take too long, the original observations can change before the system is fielded.
That is why “minimum viable capability” has become more than a software-world phrase. In April 2026, Saltzman used a Commander’s Note to urge Space Force acquirers and operators to work together on defining and rapidly delivering minimum viable capabilities rather than waiting for every operational requirement to be met, according to Breaking Defense.
In that note, he argued that an 80 percent solution in the warfighter’s hands today is more valuable than a 100 percent solution that arrives late. That does not mean abandoning technical rigor. It means changing which risks the service is willing to accept.
Spiral development replaces the requirements binder
The acquisition philosophy underneath the shift is spiral development: field a usable baseline, operate it, learn from it, and improve it through later increments.
That is a deliberate break from the traditional model in which large programs can spend years refining requirements before meaningful capability reaches operators. Under the new approach, contractors are being asked to show that they can deliver working systems on tighter timelines, not merely promise performance on paper.
For satellite companies, the practical question is changing. It is no longer just, “Can you meet every requirement?” It is increasingly, “What can you field quickly, what will it do on day one, and how fast can the next increment follow?”
The Defense Department’s broader acquisition reform push points in the same direction. In November 2025 remarks on acquisition transformation, Defense Secretary Pete Hegseth said the department would eliminate unnecessary technical standards and compliance requirements that add little or no value to fielding lethal capability, while still seeking technical rigor without sacrificing speed, according to the department’s published transcript.
The NRO shows what speed can look like
The National Reconnaissance Office has become the obvious comparison point. Its proliferated satellite architecture, built around many smaller spacecraft rather than a handful of exquisite platforms, has moved quickly from first launches into operational use.
Air & Space Forces Magazine reported in December 2025 that the NRO launched the constellation’s first spacecraft in 2024 and had nearly 200 satellites in orbit by late 2025, making it the largest government-operated satellite fleet. The constellation had already generated more than 160,000 imagery and data collections, according to the report.
The point is not that every Space Force program can copy the NRO model exactly. Intelligence satellites, missile-warning systems, communications layers, ground software, and command-and-control systems all carry different risks. But the NRO example has strengthened the argument that national security space programs can move faster when architectures are more modular, more proliferated, and less dependent on one perfect spacecraft.
Funding has raised the pressure
The shift is happening against a much larger spending backdrop. A recent American Enterprise Institute analysis found that overall funding for space in the Defense Department budget more than doubled from $12.6 billion in fiscal 2018 to $32.9 billion in fiscal 2024.
That money has helped fund more resilient space architectures and a more unified military space chain of command. It has also raised expectations. If the United States is spending far more on national security space, senior leaders need to show that the money is producing operational capability quickly enough to matter.
That is where speed becomes political as well as military. Congress, the Pentagon, and the services have all heard acquisition reform promises before. The difference now is that Space Force leaders are tying acquisition speed directly to warfighting outcomes.
What it means for contractors
The contracting base is being sorted by a new kind of credibility.
Companies with existing flight hardware, modular designs, mature production lines, and supply chains that can support rapid delivery are better positioned. Companies built around long milestone reviews, bespoke designs, and years of requirements refinement face more pressure to prove that their model still fits the moment.
The change also creates a new risk. A contractor that promises speed and misses may suffer more reputational damage than one that promised a slower schedule from the start. If program offices build operational plans around faster delivery, schedule slips become more than an inconvenience. They become a strategic problem.
That does not mean every requirement can be waived or every test shortened. Space hardware still operates in an unforgiving environment, and national security missions can carry consequences that commercial systems do not. The harder task is deciding which requirements protect the mission and which ones simply preserve the old process.
For now, the direction from senior leadership is clear. The Pentagon wants satellite builders to treat time as part of the capability itself. In the old model, “good enough” could sound like an admission of compromise. In the new one, it may be the only way to get useful hardware into the fight before the fight has changed.
Photo by Mahmoud Yahyaoui on Pexels
