At Sea-Air-Space 2026, something unusual happened. For the first time, the Director of the Office of Management and Budget, Russell Vought, took the stage. That alone is worth noting. OMB doesn’t typically show up in industry forums like this unless there’s intent behind it. Credit likely goes, at least in part, to Jerry Hendrix, who understands that shipbuilding isn’t just a Navy problem. It’s a national industrial base problem.

Vought’s message was clear and provocative: backlog in shipbuilding is a sign of failure. It’s a clean soundbite, but an incomplete one.

However, Vought is right.

Backlog can signal dysfunction. In defense shipbuilding, when programs stretch, costs grow, and schedules slip, backlog becomes a visible artifact of deeper problems: unstable designs, midstream requirement changes, and stop-start funding. In that sense, backlog isn’t the problem. It’s the symptom.

Where the Argument Breaks Down

In most industrial sectors, backlog isn’t failure—it’s oxygen. It provides demand visibility, stabilizes the workforce, and gives suppliers confidence to invest. Without it, you don’t get efficiency, you get fragility. The U.S. government remains one of the least predictable customers in the industrial world, driving hesitation rather than optimization.

There’s a cost curve we’re ignoring…

The Zumwalt-class destroyer was cut at three ships when costs crossed ~$3B. Today, Arleigh Burke-class destroyers exceed that threshold. A new Ford-class carrier comes in around $13B, while early concepts of a ‘Trump-class’ battleship approach $17B per hull. What was once unacceptable is now baseline.

Six months ago, the conversation centered on marginal increases. Today, we’re discussing a 50% increase in the defense budget, a $65B shipbuilding target, and a ‘Golden Fleet.’ These are structural ambitions, but the system hasn’t materially changed.

Speed at the Top, Friction Below

Decision-making is accelerating at senior levels, but execution still happens through contracting officers, program managers, engineers, and suppliers.

When decisions move faster than execution can absorb, the result is confusion. The Chevrolet Vega is a reminder: accelerated decisions without engineering discipline led to failure. The corporate parent, General Motors, was far too involved in deciding things with poor information and visibility on the actual business processes.

Narrative velocity moves fast: soundbites, social media, press conferences. Structural velocity is slower: design maturity, contracting pathways, workforce capacity, and budget alignment. Right now, narrative velocity is outpacing structural velocity.

The ‘Golden Fleet’ emerged quickly and reset expectations, but it caught the Navy and industry off guard. It risks consuming a significant portion of future shipbuilding accounts. Similarly, the ‘Golden Dome’ initiative is still forming while carrying major cost implications.

The force remains under strain from extended deployments, deferred maintenance, and munitions expenditure. Yet we are proposing to do more. The issue isn’t ambition, it’s alignment between ambition and execution capacity.

A System Years in the Making

Tech companies like Google, Amazon, OpenAI, and Microsoft carry massive backlogs measured in hundreds of billions. These are not seen as failures, but as visibility and growth signals. Backlog works when the system works.

It’s also worth stating plainly: this didn’t happen overnight.

The challenges we’re seeing in shipbuilding, and in the broader defense acquisition system, span multiple administrations, multiple leadership teams, and in many cases, entire careers.

• Requirements have shifted faster than designs could stabilize
• Budgets have fluctuated faster than industry could adapt
• Priorities have evolved faster than programs could execute

No single decision created this environment. No single office will fix it. That’s what makes the characterization of backlog as “failure” feel incomplete. Because backlog, in many cases, is not the origin of the problem.

It’s what the system produces when alignment breaks down over time.

We don’t have a backlog problem. We have an alignment problem.

Too often, industry is left to absorb it. Until that changes, backlog won’t disappear. It will persist—as the system’s way of coping with it.

Backlog is diagnostic. We are accelerating ambition and decision-making faster than we are fixing execution. If we are serious about building the fleet we describe, the question is not whether backlog exists, but whether the system behind it is ready to deliver.

We don’t have a backlog problem. We have an alignment problem.

We are accelerating ambition and decision-making faster than we are fixing execution. If we are serious about building the fleet we describe, the question is not whether backlog exists, but whether the system behind it is ready to deliver.

Have You Checked Under the Hood Lately?

Plenty of auto parts stores will plug a tester up to your car for a free diagnosis. The tester may reveal a code or, occasionally, tell you exactly what the dummy light on your dashboard means. If you’re in defense, you:

• Might need a more sophisticated tool
• Likely need to use sharper language across your team
• Most certainly need to be moving faster than you were one year ago

If someone used the wrong term to describe your systems or capabilities, who would hear those flawed words? Your customer? Your team?

Who would call it out?