newsfilter.io
Interview, Fireside Chat

Can the Military Move at Startup Speed? How the Army and Navy Are Rebuilding

  • Core Challenge: The Department of Defense (DoD) is described as a "black box" created by legacy Cold War-era statutes (Packard Commission, Clinger-Cohen) and risk-minimizing implementation, resulting in a culture of "duct tape and bubble gum" rather than a technology problem.
  • Strategic Shift: DoD leadership is actively dismantling "Program of Record" inertia (75 Program Executive Offices) in favor of "Military Moneyball," shifting focus from fixed long-term budgets to buying capability per dollar and decoupling divestment from acquisition cycles.
  • Acquisition Reform: The Army and Navy are utilizing "Software Acquisition Pathways" and "Other Transaction Authorities" (OTAs) to bypass traditional 18-month requirement cycles, fast-tracking capabilities like mission command from 18 months down to three months via "Capability Need Statements" instead of 4,000-page documents.
  • Cultural Pivot: Leaders emphasize a transition from "hedge against failure" risk management to "outcome-driven" metrics, arguing that 10-year procurement cycles are incompatible with the speed of AI and software development; success is measured by "overmatch" (orders of magnitude leaps) rather than incremental 15% improvements.
  • Forward-Looking Initiatives (Army):
    • Next Gen Command & Control: A consortium is moving from piloting to a program phase to replace 20-year-old tablets in M1A2 tanks with Android-based tactical apps.
    • Project Flytrap: A new initiative to scale counter-drone solutions using non-conventional sensors and automation, inspired by Ukraine's conflict, to automate electromagnetic and acoustic threat detection.
    • Autonomy: Moving toward autonomous vehicle formations and toolchains (SIM to VNV) to replace archaic microcontroller-based systems, aiming to reduce human exposure to combat ("blood for iron").
  • Forward-Looking Initiatives (Navy):
    • Digital On-Ramp: The Defense Innovation Unit (DIU) is streamlining access for horizontal capabilities (e.g., edge compute, AI) to enable enterprise-wide buys rather than siloed procurement.
    • Portfolio Management: The Navy is converting Program Executive Offices to portfolios to allow "sunset" of legacy systems (e.g., 17 separate map servers) in favor of shared enterprise services.
    • Marine Innovation Unit: A program retaining talented Marines in reserves with full-time venture jobs to scout technology and bridge the gap between commercial innovation and military needs.
  • Startup Engagement Strategy:
    • Direct Access: The Army is inviting startups to engage directly with units and Army Futures Command for rapid field testing, bypassing traditional PEO barriers where possible.
    • Proximity Requirement: Startups are advised to locate near warfighters (e.g., San Diego) to understand the ecosystem rather than hiring sales teams prematurely; "translation" costs are reduced by having founders engage directly with operators.
    • Dual-Use Focus: 25 outside dollars for every federal dollar in In-Q-Tel investments highlight the viability of dual-use models; the goal is "outcomes overmatch" to justify the rapid divestment of legacy tech.
  • Key Metrics & Outcomes:
    • Valley of Death Funds: New mechanisms like AFT (Accelerating Procurement for Innovative Technology) are being used to fund breakthroughs from R&D to Operations & Maintenance, though funding remains insufficient.
    • Risk Realignment: Leaders compare current government risk metrics (waste/fraud) to venture metrics (speed/outcome), noting that "not making mistakes" is an incoherent goal against disruptive technology.
    • Scale Goal: The objective is to have 90% of the portfolio consist of new, scaled capabilities, with innovation activities currently comprising less than 1% of the budget but showing exponential impact.
  • Specific Examples of Change:
    • Identity Management: Consolidating 1,000+ identity management solutions into a single Navy Identity Service to repurpose budget for harder problems.
    • Electronic Warfare: A 3-month, $300k pilot to paint a solution "brown" and field it on a Humvee, succeeding where a traditional $10M+ RFP would have stalled.
    • AI/LLM Strategy: Recognizing that unique data sets and mission application, not base models, drive value; the DoD is leveraging commercial models (Llama, Claude, ChatGPT) with unique military data.
  • Startup Red Flags (What to Avoid):
    • Building products solely for the DoD (loss of dual-use nature and commercial viability).
    • Attempting to tailor products to obscure, long-winded requirement documents instead of top-level capability needs.
    • Ignoring the need to validate 10x-100x value propositions with data.
  • Startup Green Flags (What to Pursue):
    • Maintaining a "north star" product vision while seeking early field validation with warfighters.
    • Demonstrating how a solution enables "speed" (as a dependent variable) rather than just adhering to cost schedules.
    • Leveraging "consortiums" of multiple small companies to solve complex problems rather than a single vendor delivering everything.
  • Historical Context: The current acquisition system was fundamentally altered in 1968 with "Miniman 3" (line-item budgeting), creating rigid 3-year spend cycles that force the military to predict the future 5+ years ahead; this is now recognized as a failure mode given modern tech velocity.
  • Leadership Commitment: Secretary of Defense and top Army/Navy leadership are providing policy exceptions (12 granted by the Army alone) based on data-driven arguments, signaling a rare alignment of public interest, commercial innovation, and national security.