<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>Project Failure Intelligence</title><description>Source-grounded enterprise technology project failure analysis.</description><link>https://project-failure-intelligence.pages.dev/</link><language>en-us</language><item><title>Revlon SAP disruption</title><link>https://project-failure-intelligence.pages.dev/revlon-sap-disruption/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/revlon-sap-disruption/</guid><description>Draft record created from reporting on alleged SAP-related disruption in inventory, receivables, and order processes. The case needs analyst refinement before publication.</description><pubDate>Sat, 22 Aug 2026 03:05:00 GMT</pubDate><category>ERP Implementation</category><category>SAP ERP</category><category>Consumer Goods</category><category>weak governance</category><category>data migration quality</category></item><item><title>Mission Produce ERP go-live disruption</title><link>https://project-failure-intelligence.pages.dev/mission-produce-erp-go-live-disruption/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/mission-produce-erp-go-live-disruption/</guid><description>Mission Produce’s November 2021 ERP go-live disrupted core avocado operations, leaving the company unable to reliably track inventory volumes and ripeness, which caused spoilage, supply gaps, and invoicing delays. To keep customer commitments, it had to buy fruit from other suppliers and create workaround processes while bringing in outside consultants to stabilize the system. The failure mattered because it materially damaged margins and was cited as the primary driver behind a $22.2 million year-over-year drop in quarterly gross profit, exposing weaknesses in implementation planning, risk sizing, and post-go-live stabilization.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>ERP Implementation</category><category>ERP modernization</category><category>Food Distribution</category><category>stabilization gaps</category><category>integration complexity</category><category>operational disruption</category></item><item><title>NHS National Programme for IT</title><link>https://project-failure-intelligence.pages.dev/nhs-national-programme-for-it/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/nhs-national-programme-for-it/</guid><description>The programme aimed to centralize major NHS information systems, but it became a prolonged megaproject marked by unclear scope, weak stakeholder buy-in, contract imbalance, and persistent delivery failure. The effort became a reference case for top-down public-sector technology transformation failure.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>Digital Transformation Program</category><category>National health IT and electronic care records</category><category>Healthcare</category><category>conflicting priorities</category><category>weak governance</category><category>communication gaps</category><category>vendor dependency</category><category>late risk escalation</category></item><item><title>Hershey order and distribution system rollout</title><link>https://project-failure-intelligence.pages.dev/hershey-sap-order-and-distribution-failure/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/hershey-sap-order-and-distribution-failure/</guid><description>Hershey&apos;s late-1999 rollout tied together ERP, CRM, and supply-chain platforms but disrupted order fulfillment at the worst possible point in the retail calendar. The company later recovered, but the initial launch became a standard example of how tightly coupled go-lives can hurt the business before process change is absorbed.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>ERP Implementation</category><category>SAP ERP, Siebel CRM, Manugistics supply chain</category><category>Manufacturing</category><category>process redesign failure</category><category>integration complexity</category><category>insufficient contingency planning</category><category>communication gaps</category></item><item><title>AT&amp;T Wireless CRM upgrade breakdown</title><link>https://project-failure-intelligence.pages.dev/att-wireless-crm-upgrade-breakdown/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/att-wireless-crm-upgrade-breakdown/</guid><description>AT&amp;T Wireless upgraded Siebel CRM under severe business pressure while also navigating outsourcing rumors, layoffs, number-portability deadlines, and deep back-end integration work. The result was a visible customer-service collapse that damaged revenue and reputation.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>CRM Implementation</category><category>Siebel CRM upgrade and telecom integrations</category><category>Telecommunications</category><category>unrealistic timeline</category><category>integration complexity</category><category>staffing shortages</category><category>insufficient contingency planning</category><category>leadership turnover</category></item><item><title>TSB core banking migration disaster</title><link>https://project-failure-intelligence.pages.dev/tsb-core-banking-migration-disaster/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/tsb-core-banking-migration-disaster/</guid><description>TSB&apos;s migration of millions of customer accounts from Lloyds-hosted systems to Sabadell&apos;s platform failed publicly and immediately. Customers lost access, saw incorrect information, and the bank later faced heavy regulatory penalties tied to governance and outsourcing failures.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>Infrastructure Modernization</category><category>Core banking migration</category><category>Financial Services</category><category>weak governance</category><category>vendor dependency</category><category>legacy dependencies</category><category>testing gaps</category><category>late risk escalation</category></item><item><title>Lidl SAP HANA merchandise management abandonment</title><link>https://project-failure-intelligence.pages.dev/lidl-sap-hana-abandonment/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/lidl-sap-hana-abandonment/</guid><description>Lidl abandoned a €500 million SAP merchandise-management programme after going live and investing in broad rollout. The programme illustrates the cost of forcing a new enterprise platform into a business model whose economics and operational assumptions were not truly aligned.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>ERP Implementation</category><category>SAP Retail on HANA</category><category>Retail</category><category>budget constraints</category><category>legacy dependencies</category><category>unclear success metrics</category><category>undefined ownership</category></item><item><title>Birmingham City Council Oracle ERP failure</title><link>https://project-failure-intelligence.pages.dev/birmingham-oracle-erp-failure/</link><guid isPermaLink="true">https://project-failure-intelligence.pages.dev/birmingham-oracle-erp-failure/</guid><description>Birmingham City Council replaced its long-standing SAP environment with Oracle Cloud in a programme that became a governance and execution failure. Costs more than doubled, critical finance functions remained impaired, and the council entered reimplementation while still dealing with operational fallout.</description><pubDate>Sun, 19 Jul 2026 16:02:56 GMT</pubDate><category>ERP Implementation</category><category>Oracle Cloud ERP and HCM</category><category>Public Sector</category><category>skill gaps</category><category>excessive customization</category><category>integration complexity</category><category>late risk escalation</category><category>vendor dependency</category></item></channel></rss>