The Ukrainian conflict demonstrates the power of a fast, iterative cycle: deploy technology, see if it works, and adapt quickly. This agile approach, common in startups but alien to traditional defense, is essential for the U.S. to maintain its technological edge and avoid being outpaced.

Unlike traditional software where problems are solved by debugging code, improving AI systems is an organic process. Getting from an 80% effective prototype to a 99% production-ready system requires a new development loop focused on collecting user feedback and signals to retrain the model.

For leaders overwhelmed by AI, a practical first step is to apply a lean startup methodology. Mobilize a bright, cross-functional team, encourage rapid, messy iteration without fear, and systematically document failures to enhance what works. This approach prioritizes learning and adaptability over a perfect initial plan.

Instead of waiting for AI models to be perfect, design your application from the start to allow for human correction. This pragmatic approach acknowledges AI's inherent uncertainty and allows you to deliver value sooner by leveraging human oversight to handle edge cases.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

Google has shifted from a perceived "fear to ship" by adopting a "relentless shipping" mindset for its AI products. The company now views public releases as a crucial learning mechanism, recognizing that real-world user interaction and even adversarial use are vital for rapid improvement.

Admiral Whitworth, initially a major critic concerned about accountability, became a true believer after taking charge of Project Maven. His conversion was driven by the software's pliability—its ability to be updated rapidly to meet battlefield needs—which he found more valuable than algorithmic perfection.

Traditional software development iterates on a known product based on user feedback. In contrast, agent development is more fundamentally iterative because you don't fully know an agent's capabilities or failure modes until you ship it. The initial goal of iteration is simply to understand and shape what the agent *does*.

Building a product too quickly with AI, without incremental user feedback, is like growing a tree indoors without wind. It appears fully formed but lacks the structural integrity and deep intuition gained from being exposed to real-world forces and user friction at each stage of growth.