Discussion about this post

User's avatar
David's avatar
Feb 1Edited

Outstanding episode. One framing that really came through for me, especially in Eric Labs’ answers, is that the CBO isn’t best understood as a “budget referee” or a Navy counterweight, but as an institutional memory node inside the federal system.

Program offices rotate, strategies reset, requirements churn, and narratives evolve. The CBO doesn’t. Its comparative advantage isn’t pessimism, it is CBO’s persistence. By aggregating historical ship costs, industrial base behavior, and long-run sustainment realities, the CBO forces the system to confront second-order effects that no single program, PEO, or sponsor is incentivized to model, or even capable.

In that sense, the CBO plays a critical role in the distributed innovation process within government: not as an innovator or advocate, but as the mechanism that enforces learning across time. Fleet debates that ignore sustainment, workforce inertia, or industrial throughput aren’t “bold,” they are incomplete. The CBO’s work doesn’t kill programs; it sets the boundary conditions under which they can remain credible.

This episode is a valuable reminder that affordability isn’t an accounting exercise—it’s a strategic constraint, and honest arithmetic is a prerequisite for serious naval planning.

Nicely done!

Americans for a Stronger Navy's avatar

Interesting, thank you.

3 more comments...

No posts

Ready for more?