CS-107failure
Waste Management, Inc.
SAP Waste and Recycling revenue-management system (licensed October 2005, New Mexico pilot 2006-2007), terminated and litigated (2008-2010)
- Region
- North America
- Country
- United States
- Industry
- Other (cross-industry)
- Functions
- IT, ERP & Digital, Sales & Revenue Operations, Finance & FP&A, Customer Experience & Support
- Topics
- Legacy ERP and fragmented systems block execution; Technology spending is growing without business returns; Cross-functional processes are slow and broken; Pricing and customer profitability are deteriorating
- Starting situation
- In-flight initiative
- Period
- 2005–2010
- Last verified
- 4 November 2026
Executive summary
In 2005 Waste Management, the largest US waste hauler with about US$13bn of revenue, licensed SAP's waste-and-recycling industry solution to replace its billing, collections, pricing and customer set-up systems under a programme it called Customer First [C02, C04, C14, C16].
The pilot in New Mexico, promised for December 2006, was still not working through 2007; the company terminated it, switched the system off, returned to its old one and sued SAP for more than US$100m [C01, C03, C05, C07]. Its own filings said SAP had to write new code and extensively customise the software, which did not deliver a usable and supportable application [C09]. SAP counterclaimed that the customer had failed to define its requirements, staff the project and migrate its data [C13].
The company wrote off US$51m of the US$70m it had capitalised, chose to improve its existing system instead, and settled in April 2010 for a confidential cash payment [C11]. The lesson: an industry solution that has not run at a company like yours is a development project, and should be bought, governed and priced as one.
Outcome: failure
The initiative was abandoned, exited or written down, or an official finding called it a failure.
Basis of the outcome
Waste Management terminated the pilot of the revenue-management application it had run through 2007, said the problems impeded the margin gains it expected (S01), switched the system off and returned to its old system (S03), and sued SAP for more than US$100m of project costs (S02). It then decided to improve its existing revenue-management system instead and recorded a non-cash charge of US$51m in 2009 for abandoning the licensed software, against US$70m capitalised (S14). The dispute was settled in April 2010 with a one-time cash payment by SAP, terms undisclosed (S14, S06). Abandonment with a write-off meets the failure criterion.
Key figures
| Phase | Figure | Value | When | Verification |
|---|---|---|---|---|
| Before | Operating revenue | US$13,310m | 2007 | regulatory_filing_unaudited |
| Before | Licence signed | 3 October 2005 | 2005 | press_reported |
| Before | Planned implementation | about 18 months | 2005 | press_reported |
| During | Pilot due | 15 December 2006 | 2006 | press_reported |
| During | Abandonment charge range disclosed | US$45m-55m | 2008 | regulatory_filing_unaudited |
| After | Project expense claimed | more than US$100m | 2008 | multiple_independent |
| After | Abandonment charge | US$51m | 2009 | regulatory_filing_unaudited |
| After | Benefits claimed lost | more than US$350m | 2010 | press_reported |
| After | Employees | about 45,900 | Dec 2008 | regulatory_filing_unaudited |
- regulatory_filing_unaudited
- Text in an 8-K, 6-K or 10-Q, which is filed with a regulator but not audited.
- press_reported
- A journalist's own reporting.
- multiple_independent
- Two or more independent sources agree.
Practices this case bears on
- SupportsDecide what truly differentiates before buying standard software; change the process for everything else BP-002
- SupportsRoll out operational and system change in waves, each proven before the next BP-006
- SupportsWhen the thesis has failed, exit in one decisive move and say what is kept BP-007
- SupportsMake line managers and the front line own the change, and train users before they get access BP-009
- SupportsSequence customer-facing cutovers last, rehearse failure at full scale, and make resilience a programme outcome BP-014
- SupportsMake a business executive, not IT, the owner of a technology-led transformation BP-015
- SupportsTreat vendor attestations, awards and executive testimony as claims to test, not as assurance BP-019
- SupportsWrite exit and pause criteria at approval, and treat impairments as triggers to re-test the strategy BP-042
- SupportsValidate the proposition with the target customers' own evidence and a control-market pilot before a national launch BP-057
- SupportsDecide what litigation or a dispute is for, and settle against its full cost and duration BP-067
- SupportsProtect the integrity of procurement and appointments, and test feasibility before signing long contracts BP-068
Sources
- S01 Waste Management, Inc. Form 10-K for fiscal year 2008 · Waste Management, Inc., Waste Management, Inc. (SEC EDGAR), 2009-02 · accessed 2026-11-04
- S02 SAP sued by trash hauler Waste Management · Linda Loyd, The Philadelphia Inquirer, 2008-03-27 · accessed 2026-11-04
- S03 US waste management firm sues SAP over 'failed system' · not stated, Manufacturing Management, 2008-03 · accessed 2026-11-04
- S04 Biggest ERP failures of 2010 · not stated, Computerwoche (IDG News Service), 2010-12-17 · accessed 2026-11-04
- S05 Waste Management lawsuit against SAP (headline not shown) · not stated, ITBusiness.ca, 2008-03 · accessed 2026-11-04
- S06 SAP, Waste Management settle lawsuit · Chris Kanaracus, Computerworld (IDG News Service), 2010-05-03 · accessed 2026-11-04
- S07 Update: SAP fires back at Waste Management · Chris Kanaracus, Computerworld (IDG News Service), 2008-08-14 · accessed 2026-11-04
- S08 Accusations flying in SAP-Waste Management suit · Chris Kanaracus, InfoWorld (IDG News Service), 2008-10-24 · accessed 2026-11-04
- S09 'Rigged' product demo in SAP suit goes missing · Chris Kanaracus, Network World (IDG News Service), 2009-05-28 · accessed 2026-11-04
- S10 SAP software a 'complete failure,' lawsuit claims · Mary Hayes Weier, InformationWeek, 2008-03-27 · accessed 2026-11-04
- S11 Lessons learned from the Waste Management ERP failure · Bill Baumann, Panorama Consulting Group, 2021-04-14 · accessed 2026-11-04
- S12 Waste Management sues SAP over ERP implementation · Chris Kanaracus, InfoWorld (IDG News Service), 2008-03-27 · accessed 2026-11-04
- S13 Waste Management, Inc. Form 10-Q for the quarter ended 31 March 2008 · Waste Management, Inc., Waste Management, Inc. (SEC EDGAR), 2008-04 · accessed 2026-11-04
- S14 Waste Management, Inc. Form 10-Q for the quarter ended 31 March 2010 · Waste Management, Inc., Waste Management, Inc. (SEC EDGAR), 2010-04 · accessed 2026-11-04
- S15 Waste Management, Inc. Form 10-Q for the quarter ended 30 September 2008 · Waste Management, Inc., Waste Management, Inc. (SEC EDGAR), 2008-10 · accessed 2026-11-04
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026 · Last verified 4 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

