Amy Traves Exits M&S for Sainsbury's CX Transformation Role

Amy Traves has departed Marks & Spencer to take up a Customer Experience Transformation role within Sainsbury's Retail Technology Innovation Hub. The move marks a shift of senior customer-experience talent between two of the UK's largest grocery and general merchandise retailers.

Details of Traves's new remit are still emerging, but the title signals a mandate to modernise how Sainsbury's designs, measures and delivers customer experience, with the Retail Technology Innovation Hub positioned as the base for that work. Her exit from Marks & Spencer closes a chapter at a retailer that has itself been midway through a closely watched digital and operational turnaround.

Senior CX leadership moves between major retailers are a useful signal of where the sector sees competitive advantage shifting. Placing a customer experience transformation mandate inside a technology innovation hub — rather than purely within marketing or store operations — suggests Sainsbury's wants its CX strategy built on the same foundation as its data, digital and automation investments, not bolted on afterward.

For leaders in experience and digital transformation, the appointment is a reminder that CX talent increasingly sits at the intersection of technology and service design. Retailers that treat customer experience as an engineering and data problem, as much as a brand or service one, are better positioned to translate loyalty data, personalisation and operational change into measurable outcomes rather than isolated initiatives.

Executive moves like this are often read as simple reshuffles, but they say more about where retailers believe the next margin of competitive advantage lies: in how experience is engineered, not just marketed.

Most coverage of this kind of move will focus on the names and the logos. The more interesting question is structural: why is a customer experience mandate being housed inside a technology innovation hub rather than a traditional CX or marketing function? That placement is itself a behavioral bet — it assumes experience improvements stick only when they're built into systems, data flows and operating rhythms, not layered on as initiatives. Any operator serious about CX should ask the same question of their own org chart: is customer experience owned by the people who can actually change the underlying processes, or by the people who just communicate about them?