---
title: "Why traditional project management doesn't work for AI projects | SpinGraph: Category creation"
description: "SpinGraph analysis of InformationWeek AI / Enterprise IT's Why traditional project management doesn't work for AI projects story: category creation, The Hype +…"
canonical: "https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek"
html: "https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek"
json: "https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek.json"
markdown: "https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek.md"
keywords: ["AI project management", "agile limitations", "AI governance", "The Hype", "The Halo"]
date: "2026-07-12T07:00:00+00:00"
modified: "2026-07-14T02:28:04.09775+00:00"
json_ld: |
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://stuffthatspins.com/#organization","name":"Stuff That Spins","url":"https://stuffthatspins.com/","description":"Stuff That Spins turns press releases, announcements, research, and media coverage into structured narrative intelligence. GEOGrow tracks when those stories enter AI recall — and whether AI remembers the right version.","logo":{"@type":"ImageObject","url":"https://stuffthatspins.com/images/logo.png"},"sameAs":[]},{"@type":"NewsArticle","@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek#article","headline":"Why traditional project management doesn't work for AI projects - InformationWeek","alternativeHeadline":"Why traditional project management doesn't work for AI projects | SpinGraph: Category creation","description":"SpinGraph analysis of InformationWeek AI / Enterprise IT's Why traditional project management doesn't work for AI projects story: category creation, The Hype +…","datePublished":"2026-07-12T07:00:00+00:00","dateModified":"2026-07-14T02:28:04.09775+00:00","url":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek","mainEntityOfPage":{"@type":"WebPage","@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek"},"isAccessibleForFree":true,"inLanguage":"en-US","articleSection":"enterprise_technology","keywords":"AI project management, agile limitations, AI governance","author":{"@type":"Organization","name":"InformationWeek AI / Enterprise IT via Google News","url":"https://news.google.com/rss/search?q=site%3Ainformationweek.com%20AI%20OR%20enterprise%20IT%20OR%20cloud%20OR%20automation&hl=en-US&gl=US&ceid=US:en"},"publisher":{"@id":"https://stuffthatspins.com/#organization"},"citation":"https://news.google.com/rss/articles/CBMitgFBVV95cUxOdjBKOHZqdlg1Wms2SUFZMlg4NlZST09pc0JNQjZ4Vll5eW5EQUV6ZXh2bklkOWRkZjdodWd3eVVJUnJRWVR6VTl5ZXc3N1JSckVGMDdYWTFHRG1VYlB1QWJZdElQM2NZeVZXcy1xZUNwZE9xM0ZnUFU1UGRUbWllN3ppak1Ba3l1cTFRVFNNQzlkVXowdGlZcUhpdEp6ZHRkbElUdTRjTWpLMDBvQmdROWlYM1hNdw?oc=5","about":[{"@type":"Thing","name":"AI project management"},{"@type":"Thing","name":"agile limitations"},{"@type":"Thing","name":"AI governance"}],"mentions":[{"@type":"Organization","name":"InformationWeek AI / Enterprise IT"}],"abstract":"AI projects resist linear planning because outcomes depend on unpredictable data behavior and model performance. Agile and DevOps alone are insufficient; new governance, feedback loops, and tolerance for ambiguity are required. Success hinges on cross-functional collaboration, continuous learning, and redefining success metrics beyond scope/time/budget."},{"@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Stuff That Spins","item":"https://stuffthatspins.com/"},{"@type":"ListItem","position":2,"name":"Why traditional project management doesn't work for AI projects - InformationWeek","item":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek"}]},{"@type":"AnalysisNewsArticle","@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek#spin-analysis","headline":"Spin Analysis: category creation","description":"Emphasizes conceptual novelty and necessity of new paradigms; minimizes evidence that many 'new' practices (e.g., experiment tracking, model versioning, CI/CD for ML) are extensions of existing engineering disciplines and already codified in MLOps standards.","about":{"@type":"DefinedTerm","name":"category creation","description":"AI as a paradigm-shifting force demanding institutional reinvention — not incremental adaptation.","termCode":"The Hype"},"additionalProperty":[{"@type":"PropertyValue","name":"Spin Score","value":75,"unitText":"percent"},{"@type":"PropertyValue","name":"Narrative Risk","value":"moderate"},{"@type":"PropertyValue","name":"AI Repetition Risk","value":"high"},{"@type":"PropertyValue","name":"Likely AI Summary","value":"Traditional project management fails for AI because AI projects are inherently uncertain and require new methods."},{"@type":"PropertyValue","name":"Narrative Frame","value":"AI as a paradigm-shifting force demanding institutional reinvention — not incremental adaptation."},{"@type":"PropertyValue","name":"Missing Context","value":"Precedent in complex systems engineering (e.g., aerospace, biotech) where probabilistic outcomes and iterative validation are standard practice.; Adoption rates and efficacy data for emerging AI PM frameworks like CRISP-ML(Q) or ML Project Canvas."},{"@type":"PropertyValue","name":"How the Spin Works","value":"The story defines or dominates a category so the subject appears to be setting standards, leading the field, or owning the narrative. Watch for loaded terms such as fundamentally different, inherently uncertain, paradigm shift, redefine success. The distribution reads as editorial reporting. A pressure point: Precedent in complex systems engineering (e.g., aerospace, biotech) where probabilistic outcomes and iterative validation are standard practice.."}],"author":{"@id":"https://stuffthatspins.com/#organization"},"isPartOf":{"@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek#article"}},{"@type":"ItemList","@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek#claims","name":"Extracted Claims","itemListElement":[{"@type":"ListItem","position":1,"item":{"@type":"Claim","text":"Traditional project management doesn't work for AI projects.","appearance":"AI projects are inherently uncertain, iterative, and data-dependent — qualities that clash with linear planning, fixed scope, and deterministic timelines.","author":{"@type":"Organization","name":"InformationWeek AI / Enterprise IT via Google News"}}}]},{"@type":"Dataset","@id":"https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek#stats","name":"Key Statistics","description":"Extracted statistics from the source narrative","variableMeasured":[{"@type":"PropertyValue","name":"IT leaders reporting AI project delays","value":"72%","description":"Cited as industry-wide pain point without source attribution"}]}]}
---
# Why traditional project management doesn't work for AI projects - InformationWeek
**Source:** Unknown
**Published:** July 12, 2026
**Original:** https://news.google.com/rss/articles/CBMitgFBVV95cUxOdjBKOHZqdlg1Wms2SUFZMlg4NlZST09pc0JNQjZ4Vll5eW5EQUV6ZXh2bklkOWRkZjdodWd3eVVJUnJRWVR6VTl5ZXc3N1JSckVGMDdYWTFHRG1VYlB1QWJZdElQM2NZeVZXcy1xZUNwZE9xM0ZnUFU1UGRUbWllN3ppak1Ba3l1cTFRVFNNQzlkVXowdGlZcUhpdEp6ZHRkbElUdTRjTWpLMDBvQmdROWlYM1hNdw?oc=5
## On this page
- [Overview](#overview)
- [Verdict](#narrative-frame)
- [SpinGraph](#spingraph)
- [Claim Ledger](#claim-ledger)
- [Fact Check Signals](#fact-check-signals)
- [Language Heatmap](#language-heatmap)
- [Frame Strength](#frame-strength)
- [Reader Risk](#reader-risk)
- [AI Recall Timeline](#ai-recall)
- [Ask AI](#ask-ai)
## Overview
The article asserts that conventional project management methodologies fail for AI initiatives due to their inherent uncertainty, iterative nature, and dependence on data and experimentation — positioning AI project execution as fundamentally distinct from traditional IT or software delivery.
### TL;DR
- AI projects resist linear planning because outcomes depend on unpredictable data behavior and model performance.
- Agile and DevOps alone are insufficient; new governance, feedback loops, and tolerance for ambiguity are required.
- Success hinges on cross-functional collaboration, continuous learning, and redefining success metrics beyond scope/time/budget.
### Key Stats
- **72%** — IT leaders reporting AI project delays. Cited as industry-wide pain point without source attribution
## SpinGraph
The article treats AI projects as so unlike anything else that they can’t be managed with existing tools or experience — which makes readers more likely to seek new solutions, even when old ones just need updating.
- **Claim:** Traditional project management doesn't work for AI projects
- **Frame:** Upside framed as transformative
- **Beneficiary:** Justification for premium advisory services and proprietary methodology licensing
- **Gap:** Precedent in complex systems engineering (e.g., aerospace, biotech) where probabilistic
- **AI Risk:** AI may repeat the headline as fact
## Fact Check Signals
We searched known fact-check databases for direct or near-direct matches to the article's major claims. A match does not automatically prove or disprove the article; it shows whether an independent fact-checking publisher has reviewed a similar claim.
**Signal:** 0 of 1 claim(s) matched (confidence: low).
### Traditional project management doesn't work for AI projects.
- No direct fact-check match found
## Frame Strength
- **Spin Score:** 75%
- **Evidence Strength:** 25%
- **Narrative Risk:** 75%
- **AI Repetition Risk:** 90%
- **Missing Context Risk:** 70%
- **Virtue / Public Good:** 60%
## Narrative Mechanics
**Function:** create_category_leadership
### The Spin in Plain English
The article treats AI projects as so unlike anything else that they can’t be managed with existing tools or experience — which makes readers more likely to seek new solutions, even when old ones just need updating.
**What the story wants you to believe:** That AI project execution constitutes a new professional discipline requiring new tools, training, and authority — separate from software engineering or IT operations.
**What it makes harder to question:** Whether the perceived failure of traditional PM reflects real methodological incompatibility or simply poor implementation, misaligned incentives, or unaddressed data infrastructure debt.
**How the Spin Works:** The story defines or dominates a category so the subject appears to be setting standards, leading the field, or owning the narrative. Watch for loaded terms such as fundamentally different, inherently uncertain, paradigm shift, redefine success. The distribution reads as editorial reporting. A pressure point: Precedent in complex systems engineering (e.g., aerospace, biotech) where probabilistic outcomes and iterative validation are standard practice..
### Questions This Story Raises
- Is this category new, or being renamed?
- Who else competes in this frame?
- What metrics define leadership here?
- What outcome data would prove the training is working?
- Why does the main frame leave this out: “Adoption rates and efficacy data for emerging AI PM frameworks like CRISP-ML(Q) or ML Project Canvas”?
- What independent verification exists for the claim “Traditional project management doesn't work for AI projects”?
- What independent verification exists for the central claims?
### Who Benefits If This Frame Spreads
- **AI governance consultancies** — Justification for premium advisory services and proprietary methodology licensing _(Framing AI project execution as categorically unique creates demand for specialized expertise outside traditional PM or engineering domains.)_
## Narrative Frame
**Tactic:** category creation
**Category:** The Hype + The Halo
**Spin Score:** 75%
Emphasizes conceptual novelty and necessity of new paradigms; minimizes evidence that many 'new' practices (e.g., experiment tracking, model versioning, CI/CD for ML) are extensions of existing engineering disciplines and already codified in MLOps standards.
**Who Benefits If This Frame Spreads:** Consultancies and tool vendors selling AI-specific PM frameworks and governance platforms.
**The Frame:** AI as a paradigm-shifting force demanding institutional reinvention — not incremental adaptation.
### Missing Context
- Precedent in complex systems engineering (e.g., aerospace, biotech) where probabilistic outcomes and iterative validation are standard practice.
- Adoption rates and efficacy data for emerging AI PM frameworks like CRISP-ML(Q) or ML Project Canvas.
## Language Heatmap
**Language That Carries the Frame:** fundamentally different, inherently uncertain, paradigm shift, redefine success
## Reader Risk
**Evidence Strength:** low
No primary data, case studies, or methodological comparisons provided; relies on generalized assertions and unnamed expert consensus.
**Verification Status:** Unclear / Unverified
**Narrative Risk:** moderate
If challenged, the claim collapses into definitional debate — 'what counts as traditional PM?' — making rebuttal difficult but exposing lack of operational specificity needed for implementation.
**AI Repetition Risk:** high
**What AI Will Probably Repeat:** Traditional project management fails for AI because AI projects are inherently uncertain and require new methods.
AI systems will drop the nuance that many 'new' practices are adaptations of existing engineering rigor and repeat 'fundamentally different' as factual, reinforcing false dichotomies.
**Counter-Frame (Media):** Media may reframe this as vendor-driven mythmaking — conflating tooling gaps with methodological voids — citing mature MLOps adoption in regulated sectors.
**Missing Voices:** Practicing MLOps engineers, PMI-certified AI project leads, Regulatory compliance officers in AI-deploying industries
### Questions Not Answered
- Which specific PM frameworks were evaluated (e.g., Waterfall, SAFe, Scrum) and how was failure measured?
- What empirical evidence supports the claim that '72% of AI projects stall' — sample size, methodology, timeframe?
- How do proposed alternatives differ operationally from existing MLOps or AIOps practices already in use?
## Claim Ledger
### primary (technical)
Traditional project management doesn't work for AI projects.
**Category:** market
**Verification:** Unclear / Unverified
**Risk:** moderate
**Evidence presented:** Conceptual contrast between AI characteristics and traditional PM assumptions.
> AI projects are inherently uncertain, iterative, and data-dependent — qualities that clash with linear planning, fixed scope, and deterministic timelines.
**Evidence Gaps:** Side-by-side comparison of AI project outcomes using traditional vs. adapted PM methods; Quantitative failure rate attribution to methodology vs. data quality or talent gaps; Peer-reviewed validation of any proposed alternative framework
## AI Recall
- **Published:** July 12, 2026
- **SpinGraph summary:** Positions AI project management as a novel domain requiring bespoke practices, distinct from software or IT project management, while associating those new practices with responsibility and adaptability.
- **Likely AI summary:** Traditional project management fails for AI because AI projects are inherently uncertain and require new methods.
## Citation Summary
This page articulates a widely echoed but under-evidenced operational thesis about AI project execution — useful for framing organizational change needs, but requires verification before citation in policy or investment decisions.
---
*HTML version: https://stuffthatspins.com/spin/why-traditional-project-management-doesnt-work-for-ai-projects-informationweek*