{"version":"1.0","type":"agent_native_article","locale":"en","slug":"pentagon-ai-transformation-companies-repeating-mistakes-mp42iv15","title":"The Pentagon Learned to Transform Itself with AI. Companies Keep Repeating Its Previous Mistakes","primary_category":"transformation","author":{"name":"Valeria Cruz","slug":"valeria-cruz"},"published_at":"2026-05-13T12:02:35.615Z","total_votes":88,"comment_count":0,"has_map":true,"urls":{"human":"https://sustainabl.net/en/articulo/pentagon-ai-transformation-companies-repeating-mistakes-mp42iv15","agent":"https://sustainabl.net/agent-native/en/articulo/pentagon-ai-transformation-companies-repeating-mistakes-mp42iv15"},"summary":{"one_line":"The U.S. ranks 24th in AI adoption despite leading in model development because organizations refuse to dismantle the decision-making structures that block real transformation — a mistake the Pentagon nearly made before Project Maven forced it to change.","core_question":"Why do organizations with access to advanced AI fail to transform operationally, and what does the Pentagon's experience with Project Maven reveal about what real AI adoption actually requires?","main_thesis":"AI adoption failure is a governance problem, not a technology problem. Organizations that layer AI onto existing structures without changing decision-making chains, ownership, and operational metrics will accumulate competitive disadvantage regardless of their investment levels. The Pentagon's Project Maven succeeded because it dismantled workflows, assigned executive ownership, and measured operational outcomes — a discipline most corporate AI programs deliberately avoid."},"content_markdown":"## The Pentagon Learned to Transform Itself with AI. Companies Keep Repeating Its Previous Mistakes\n\nThere is a data point that should make any executive who approved an artificial intelligence budget over the last two years deeply uncomfortable: the United States, the country that builds the most powerful models in the world, ranks 24th in global AI adoption. Its rate is 28.3%. Singapore stands at 61%. The United Arab Emirates, at 54%. Goldman Sachs recorded that investment in AI contributed \"practically zero\" to U.S. GDP growth during 2025. The problem is not technological. It never was.\n\nDrew Cukor knows this better than almost anyone. As a retired Marine colonel and founder of Project Maven — the program through which the Department of Defense integrated AI into its most complex operational workflows — Cukor built from the inside what many considered impossible: demonstrating that commercial software could function within the largest bureaucracy on the planet and produce results that previous systems could not achieve. Today, from his firm TWG AI, he watches as American companies commit, point by point, the same mistakes the Pentagon almost made before Maven worked.\n\nHis diagnosis, published in Fortune on May 11, 2026, coincides with a singular moment: two days later, the Department of Defense announced agreements with eight technology companies — Amazon Web Services, Google, Microsoft, OpenAI, SpaceX, NVIDIA, Reflection, and Oracle — to deploy frontier AI capabilities across its classified networks at the IL6 and IL7 levels. The Pentagon is not debating whether to adopt AI. It is executing.\n\n## The Gap That Separates Building from Integrating\n\nThe Stanford 2026 Index on artificial intelligence does not describe a research failure. It describes an implementation failure. The United States leads in benchmarks, in investment in models, and in computing capacity. But that advantage does not translate into operational use because the organizations that should be deploying this technology have not changed their internal architecture to receive it.\n\nCukor introduces here a distinction that is worth more than the majority of strategic frameworks circulating at C-suite conferences: the difference between an **AI-augmented organization** and an **AI-native organization**. This is not semantics. It is the difference between bolting a new engine onto an old structure and rebuilding the structure from the design stage with that engine in mind.\n\nWhen the Pentagon launched Maven, it did not treat it as a technological experiment or as a limited pilot. Senior leaders took personal ownership of it and fought for it within the bureaucracy. Workflows were dismantled — software was not simply layered on top of them. The only metric that mattered was operational: what could soldiers do that they previously could not do. That discipline is what made it work. And that discipline is precisely what is missing from the vast majority of corporate AI programs that exist today.\n\nChina's \"AI Plus\" initiative operates with a logic structurally similar to that of Maven, although from the opposite end of the political spectrum. Beijing is not building models to compete in rankings. It is embedding AI into manufacturing, logistics, scientific research, healthcare, and education with specific industrial datasets and agents designed for concrete workflows. It does not debate control or containment. It deploys. That difference in speed between the United States' power of invention and China's capacity for integration is the gap that Cukor identifies as the central competitive risk of this decade.\n\n## Three Failures the Pentagon Barely Survived\n\nCukor identifies with precision the three mistakes that turned Maven into a possible transformation — because they nearly prevented it from happening at all.\n\nThe first is delegation without ownership. In too many corporations, AI strategy is delegated to a Chief AI Officer or an innovation lab. Those structures are designed — though no one admits it — to signal progress without threatening the existing distribution of power. The result is what Cukor calls \"pilot purgatory\": projects that never die because no one killed them, but that never scale either because no one truly pushed them forward. Maven worked because senior leaders did not delegate ownership of the problem. They assumed it themselves.\n\nThe second mistake is layering AI on top of legacy processes. There is a way of using AI that guarantees mediocre results: take the current workflow and add a model to it. Efficiency gains will be marginal because the structure generating the bottleneck remains intact. If, after launching an AI initiative, the organizational chart, the approval chains, and the operational rhythm of the company are the same as before, no transformation has occurred. What has occurred is decoration.\n\nThe third mistake is measuring activity instead of outcomes. Models trained, proofs of concept completed, partnerships announced: these are indicators of movement, not of impact. Maven was measured by what operatives could do that they previously could not do. That is the only question that matters in an AI program that claims to change something.\n\nThese three mistakes are not engineering accidents. They are governance accidents. They arise from organizations that want the image of transformation without assuming the internal political cost that dismantling what already exists entails.\n\n## What the May 13th Announcement Reveals About Real Execution\n\nThe agreement that the Department of Defense announced on May 13, 2026, with eight technology companies to operate across classified IL6 and IL7 networks is not simply news about contracts. It is a signal about what kind of institution can scale AI under conditions of maximum complexity and restriction.\n\nThe fact that the Pentagon — historically known for its software acquisition failures — managed to articulate a functional AI platform in maximum-classification environments is, in itself, a case study in structural maturity. Not in technology. The Department of Defense's CTO unified the process under an enterprise alignment structure, as analyses of the program describe. That means someone made the decision to break down the silos that historically prevented the Pentagon's technological systems from functioning coherently.\n\n**The lesson that movement offers for the private sector is an uncomfortable one**: if a bureaucracy of that scale and that historical rigidity was capable of reorganizing itself to integrate AI operationally, then the most honest explanation for why private companies fail to do the same is not a lack of resources or a lack of talent. It is a lack of willingness to assume the internal political cost of changing who decides what, how, and at what speed.\n\nCukor's analysis of the difference between companies that run AI experiments and companies that run AI transformations points precisely to that issue. It is not a budget problem. It is a question of who at the top is willing to put their name on the intermediate failure that precedes any deep transformation.\n\n## Structural Maturity Is Not What the System Claims to Have\n\nThere is a specific fragility that appears before the problem becomes visible. Organizations that are going to fail at their AI transformation do not announce it. They have roadmaps, they have labs, they have Chief AI Officers with budgets. But if one looks closely at the decision-making chain, the pattern emerges: the difficult decisions — those that involve eliminating processes or changing power structures — never actually get made. They are postponed, piloted, studied. And the system keeps functioning, with an appearance of modernization, until the competitors who did make those decisions render the cost of inertia impossible to ignore.\n\nCukor describes this as a \"white-collar reckoning\" that could be worse than the wave of industrial offshoring in the 1970s, but faster and less forgivable. Not because AI is inevitably substitutive of employment, but because companies that do not reorganize their structures of decision-making, approval, and operation will find themselves in a position of cumulative disadvantage relative to competitors who did — whether those competitors are Western or come from Asian economies that have been treating AI as operational infrastructure from the outset.\n\nThe difference between the Pentagon before Maven and the Pentagon after it is not that it now has better models. It is that it learned to sustain a transformation with executive ownership, with the dismantling of what previously existed, and with metrics that measured results. That learning took years to consolidate and came close to collapsing several times. Private companies do not have the same tolerance for time, but neither do they have the same excuse for ignoring the pattern.\n\nA system that appears strong because it possesses advanced technology, but that has not touched its decision-making structure or its approval chain, is not a transformed system. It is a system that bought itself time. How much time depends on how long it takes its competitors to do what it has still not done.","article_map":{"title":"The Pentagon Learned to Transform Itself with AI. Companies Keep Repeating Its Previous Mistakes","entities":[{"name":"Drew Cukor","type":"person","role_in_article":"Primary expert source; founder of Project Maven at the DoD and founder of TWG AI; provides the diagnostic framework for corporate AI failure."},{"name":"Project Maven","type":"technology","role_in_article":"The DoD AI integration program used as the central case study of successful organizational AI transformation."},{"name":"Department of Defense","type":"institution","role_in_article":"Institutional case study demonstrating that even the most bureaucratic organizations can achieve structural AI maturity when governance conditions are met."},{"name":"TWG AI","type":"company","role_in_article":"Cukor's current firm, from which he observes and diagnoses corporate AI adoption failures."},{"name":"Stanford AI Index 2026","type":"institution","role_in_article":"Source of data describing U.S. AI adoption as an implementation failure rather than a research failure."},{"name":"Goldman Sachs","type":"company","role_in_article":"Source of the finding that AI investment contributed near-zero to U.S. GDP growth in 2025."},{"name":"Amazon Web Services","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."},{"name":"Google","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."},{"name":"Microsoft","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."},{"name":"OpenAI","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."},{"name":"SpaceX","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."},{"name":"NVIDIA","type":"company","role_in_article":"One of eight technology companies contracted by the DoD on May 13, 2026, for IL6/IL7 AI deployment."}],"tradeoffs":["Executive ownership of AI transformation vs. delegation to specialized roles: ownership produces results but requires senior leaders to absorb political risk; delegation signals progress without threatening existing power structures","Dismantling legacy workflows vs. layering AI on top: dismantling produces structural change but creates short-term disruption and political resistance; layering is faster to deploy but produces marginal and temporary gains","Speed of AI deployment vs. depth of organizational change: moving fast with existing structures preserves stability but accumulates competitive disadvantage; moving slower to rebuild structures creates interim vulnerability but sustainable capability","Measuring activity vs. measuring outcomes: activity metrics are easier to report and politically safer; outcome metrics are harder to achieve but are the only ones that indicate real transformation","Tolerating intermediate failure vs. avoiding visible risk: real transformation requires executives to put their name on failures that precede success; avoiding that risk preserves short-term reputation but prevents transformation"],"key_claims":[{"claim":"The United States ranks 24th globally in AI adoption with a 28.3% rate, despite leading in model development and investment.","confidence":"high","support_type":"reported_fact"},{"claim":"Goldman Sachs recorded that AI investment contributed practically zero to U.S. GDP growth during 2025.","confidence":"high","support_type":"reported_fact"},{"claim":"Singapore's AI adoption rate stands at 61% and the UAE's at 54%.","confidence":"high","support_type":"reported_fact"},{"claim":"Project Maven succeeded because senior leaders assumed personal ownership, dismantled workflows, and measured only operational outcomes.","confidence":"high","support_type":"reported_fact"},{"claim":"Most corporate AI programs exist in 'pilot purgatory' — never killed, never scaled — because no senior leader truly owns the outcome.","confidence":"medium","support_type":"inference"},{"claim":"China's 'AI Plus' initiative embeds AI into industrial workflows with sector-specific datasets rather than competing on benchmark rankings.","confidence":"high","support_type":"reported_fact"},{"claim":"The DoD announced agreements with eight technology companies on May 13, 2026, to deploy AI across IL6 and IL7 classified networks.","confidence":"high","support_type":"reported_fact"},{"claim":"The primary reason private companies fail to scale AI is unwillingness to assume the internal political cost of changing who decides what.","confidence":"medium","support_type":"editorial_judgment"}],"main_thesis":"AI adoption failure is a governance problem, not a technology problem. Organizations that layer AI onto existing structures without changing decision-making chains, ownership, and operational metrics will accumulate competitive disadvantage regardless of their investment levels. The Pentagon's Project Maven succeeded because it dismantled workflows, assigned executive ownership, and measured operational outcomes — a discipline most corporate AI programs deliberately avoid.","core_question":"Why do organizations with access to advanced AI fail to transform operationally, and what does the Pentagon's experience with Project Maven reveal about what real AI adoption actually requires?","core_tensions":["Invention power vs. integration capacity: the U.S. leads in building AI but lags in deploying it, while China prioritizes integration over invention","Executive visibility vs. political safety: real AI transformation requires senior leaders to own intermediate failures, which conflicts with incentive structures that reward visible progress and penalize visible failure","Organizational stability vs. structural change: dismantling workflows and power structures is necessary for AI transformation but threatens the existing distribution of authority that senior leaders depend on","Speed of technology vs. speed of governance: AI capabilities advance faster than organizations can restructure their decision-making chains to use them","Private sector agility vs. public sector precedent: the Pentagon — historically the slowest software adopter — has now outpaced many private companies in structural AI maturity, inverting the expected relationship"],"open_questions":["How long can organizations sustain the appearance of AI transformation through activity metrics before competitive disadvantage becomes irreversible?","What specific governance structures allow senior leaders to assume ownership of AI transformation without creating single points of failure?","Can the Maven model be replicated in organizations without the existential operational pressure that drove DoD adoption?","How does the 'white-collar reckoning' Cukor describes manifest differently across industries with different competitive dynamics and time horizons?","What is the minimum structural change required to cross from AI-augmented to AI-native — and can it be done incrementally or only through discontinuous redesign?","Does China's integration-first approach produce durable competitive advantage, or does it create brittleness by embedding AI before governance frameworks mature?"],"training_value":{"recommended_for":["CEOs and C-suite executives evaluating the gap between their AI investment and operational results","Chief AI Officers and Chief Digital Officers designing transformation governance structures","Strategy consultants advising on enterprise AI adoption and organizational change","Board members assessing AI transformation risk and executive accountability","Investors evaluating whether portfolio companies are achieving structural AI maturity or only surface-level adoption","Business school programs covering digital transformation, organizational change, and competitive strategy in the AI era"],"when_this_article_is_useful":["When evaluating whether an organization's AI program is producing real transformation or only the appearance of it","When designing governance structures for enterprise AI adoption and deciding where ownership should sit","When a board or executive team needs to understand why AI investment is not translating into operational results","When benchmarking an organization's AI maturity against a high-stakes, high-complexity real-world case","When assessing competitive risk from AI-native competitors in the same market","When building the business case for dismantling legacy workflows rather than augmenting them with AI"],"what_a_business_agent_can_learn":["How to distinguish between AI-augmented and AI-native organizational architectures and why the distinction determines transformation outcomes","The three specific governance failure modes that prevent AI programs from scaling: delegation without ownership, layering on legacy processes, and measuring activity instead of outcomes","Why the internal political cost of changing decision-making structures is the actual barrier to AI transformation, not budget or technology access","How to use operational outcome metrics (what can people do now that they could not do before) as the primary evaluation framework for AI programs","Why the Pentagon's Maven case is a replicable governance model, not just a military technology story","How competitive disadvantage from AI inertia compounds over time rather than accumulating linearly"]},"argument_outline":[{"label":"The adoption paradox","point":"The U.S. leads in AI model development but ranks 24th globally in adoption at 28.3%, while Singapore reaches 61% and the UAE 54%. Goldman Sachs found AI contributed near-zero to U.S. GDP growth in 2025.","why_it_matters":"Establishes that the gap between building AI and integrating AI is real, measurable, and economically consequential — not a theoretical concern."},{"label":"The Maven benchmark","point":"Drew Cukor, founder of Project Maven at the DoD, built a working AI integration inside the world's largest bureaucracy by enforcing executive ownership, dismantling legacy workflows, and measuring only operational outcomes.","why_it_matters":"Provides a concrete, high-stakes case study of successful AI transformation under conditions more restrictive than most private organizations face."},{"label":"Augmented vs. native organizations","point":"Cukor distinguishes between AI-augmented organizations (AI bolted onto existing structure) and AI-native organizations (structure rebuilt around AI from the design stage). Most corporate programs are the former.","why_it_matters":"This distinction explains why large AI budgets produce marginal results — the bottleneck is structural, not technological."},{"label":"Three governance failures","point":"Delegation without ownership (pilot purgatory), layering AI on legacy processes (decoration not transformation), and measuring activity instead of outcomes (models trained vs. what people can now do).","why_it_matters":"Names the specific failure modes so organizations can recognize them in their own programs before they become irreversible."},{"label":"The May 13 DoD signal","point":"The Pentagon signed agreements with AWS, Google, Microsoft, OpenAI, SpaceX, NVIDIA, Reflection, and Oracle to deploy frontier AI across IL6/IL7 classified networks — not as a pilot, but as operational infrastructure.","why_it_matters":"Demonstrates that the institution that historically failed at software acquisition has now achieved structural maturity in AI deployment, removing the excuse that complexity justifies inaction."},{"label":"The white-collar reckoning","point":"Cukor warns that companies failing to reorganize decision-making structures face cumulative competitive disadvantage that could be faster and less forgivable than 1970s industrial offshoring.","why_it_matters":"Frames the cost of inertia not as a future risk but as a compounding present liability relative to competitors — Western or Asian — who are treating AI as operational infrastructure now."}],"one_line_summary":"The U.S. ranks 24th in AI adoption despite leading in model development because organizations refuse to dismantle the decision-making structures that block real transformation — a mistake the Pentagon nearly made before Project Maven forced it to change.","related_articles":[{"reason":"Directly addresses the end of AI pilot programs without commitment in 2026, complementing the article's diagnosis of pilot purgatory and the shift from experimentation to operational transformation.","article_id":12421},{"reason":"Analyzes enterprise AI acquisition dynamics and the power structures embedded in AI platforms, relevant to understanding why organizations buy AI without achieving structural transformation.","article_id":12496},{"reason":"Examines why corporate AI agents fail before security issues arise, extending the governance failure argument into the specific domain of enterprise AI agent deployment.","article_id":12608},{"reason":"Covers the rapid proliferation of AI agents inside enterprise systems without corresponding identity and governance frameworks — a concrete instance of the structural maturity gap described in this article.","article_id":12386}],"business_patterns":["Pilot purgatory: AI projects that are never killed because no one owns the decision to kill them, but never scale because no one owns the decision to push them forward","Decoration transformation: launching AI initiatives without changing organizational charts, approval chains, or operational rhythms — producing the appearance of modernization without its substance","Governance-layer failure: AI programs that fail not because of engineering problems but because the decision-making structure above them was never changed to support them","Structural maturity gap: the difference between organizations that possess AI technology and organizations that have rebuilt their internal architecture to receive and operationalize it","Competitive compounding: organizations that delay structural AI transformation accumulate disadvantage relative to competitors at an accelerating rate, not a linear one"],"business_decisions":["Whether to assign executive ownership of AI transformation directly to C-suite leaders or delegate it to a Chief AI Officer or innovation lab","Whether to dismantle existing workflows before deploying AI or layer AI on top of current processes","Whether to measure AI program success by activity metrics (models trained, POCs completed) or operational outcomes (what employees can now do that they previously could not)","Whether to treat AI as a series of experiments or as a structural transformation requiring organizational redesign","Whether to accept the internal political cost of changing decision-making chains and approval structures as a prerequisite for AI scaling"]}}