A self-inflicted tech disaster has left Asda, the UK's third-largest supermarket, reeling. The ambitious plan to upgrade its SAP ERP system and separate from Walmart's technology has backfired, causing a significant drop in quarterly revenue. But here's the twist: Asda's chairman, Allan Leighton, admits it's their own doing.
The project, dubbed 'Project Future', aimed to modernize Asda's IT infrastructure and move away from Walmart's back-office SAP systems. However, delays and disruptions have set back the financial revival by six months, with a 2.8% revenue decline to £5.1 billion year-on-year. And this is where it gets controversial—the tech separation, nearing £1 billion, was expected to be a smooth transition.
Leighton boldly stated that the sales downturn and market share issues are solely due to Project Future, not competitive activity. He attributed the IT fiasco to poor integration, inadequate testing, and a lack of capacity planning. But was this truly a self-inflicted wound, or did external factors play a role?
The project's complexity is staggering: it involved separating over 2,500 legacy systems and migrating Asda's entire operations to new IT platforms. In 2024, Asda moved to a new S/4HANA instance on Microsoft Azure, but the troubles didn't end there. The total cost of Project Future soared to £430 million, and the retailer struggled with system integration.
Asda's tech transition faced further setbacks, with postponed cutover dates and delayed tech rollouts. Despite these challenges, the company claims to have stabilized all systems, boasting an eight-year high in availability. But the question remains: could this disaster have been avoided, and what lessons can be learned from Asda's costly SAP mess?
What do you think? Was Asda's SAP upgrade a necessary risk, or a costly mistake? Share your thoughts in the comments below, and let's discuss the fine line between ambitious tech upgrades and potential self-inflicted disasters.
