A warrant officer I worked with once submitted a budget justification for military working dog food. Finance asked him to explain the operational requirement. He wrote back three words: "Dog no food. Dog die."
They said his level of professionalism was appalling.
The dogs were fed.
I came into defense from the private sector. Nine years running a small business where if I needed something, I bought it. Same day. Done. I doubled revenue from $600K to $1.2M by making fast decisions with real money on the line.
Then I entered the Navy's budget process.
I needed 6 signatures, a POM submission, and what felt like divine intervention to buy dog food.
The Warrant Officer Was Right
He wasn't being unprofessional. He was being efficient. He communicated the requirement, the risk, and the urgency in three words. The system just wasn't designed to hear it.
This is the tension at the heart of defense acquisition: the people executing the mission are forced to justify obvious operational needs through layers of bureaucracy designed for billion-dollar weapons programs. The same PPBE process that funds an aircraft carrier also funds kibble.
The same budget process that takes 2+ years to field a counter-drone system also takes 2+ years to fund dog food. One of those timelines is forgivable. Neither should be acceptable.
Sustainment Is the Real Valley of Death
Everyone talks about the "acquisition valley of death" — the gap between a prototype and a production contract. But there's a second valley nobody talks about: the sustainment valley.
We spend billions developing and procuring autonomous systems. Then we starve them of the funding they need to operate, maintain, and iterate.
A system that can't be sustained is a system that doesn't exist. It doesn't matter how advanced the technology is if you can't keep the lights on, train the operators, or update the software when the threat changes.
Why Defense Startups Are Winning
Companies like Saronic and Anduril don't make you write a whitepaper to feed the dog. They ship the product, and the sustainment model is baked into the contract from Day 1.
That's not because they're smarter than the traditional defense primes. It's because their business model requires a working product, not just a delivered product. When your revenue depends on operational performance, sustainment isn't an afterthought — it's the product.
The traditional acquisition model separates development from production from sustainment. Three different budget lines. Three different organizations. Three different timelines. By the time sustainment funding catches up, the original engineers have moved on and the threat has evolved.
The Question Nobody Wants to Answer
The question isn't whether the DoD acquisition system needs reform. Everyone agrees it does. The question is whether we'll reform it before the next "dog no food" moment is something more consequential than kibble.
Because right now, somewhere in the Navy, there's a system that's been delivered but can't be maintained. A capability that exists on paper but not in practice. A program that got the funding to buy the dog but not to feed it.
The warrant officer had it right. Sometimes the simplest communication is the most effective.
Dog no food. Dog die.
That's not unprofessional. That's honest.
Every defense professional has a "dog no food" story. The system won't fix itself until enough of us stop treating obvious operational needs as optional.
Sources: GAO Defense Acquisition Reports, DoD PPBE Process Documentation, Congressional Budget Office Defense Sustainment Analysis