
Sainsbury's
Key projects
Enhance in-store customer and colleague experiences to improve self-serve offerings, including self-checkout and the Smartshop mobile app.
Designing new tools and systems to empower Sainsbury’s Colleagues and easier onboarding and maintain Suppliers relationships
Decommissioning an out of date tool, by introducing improvements and enhancements to an existing platform to enable colleagues to easier input and manage information about stores
Product Design • UX Design • UI Design • Research • Story boarding • Prototyping • User Testing
Self checkout and SmartShop
Creating a future vision for the self checkout experience for Customers and Colleagues to improve ease of checkout and Colleague support.
Validating the design proposal through customer testing and implementing a new design
Implementing Nectar prices across instore customer self service tools.
Enhancing the SmartShop app to create a more seamless instore shopping experience.
The future vision and designs for self checkout

Customer
Colleague




Sainsbury's and Our Suppliers
Understand the requirements for onboarding new Suppliers to Sainsbury's, by recommending better systems and tools to streamline and improve the existing experience.

Through reviewing the onboarding process the key problems were identified as around the duplication of data entry across multiple different tools and systems, each requiring new login details.
The goal was identified to build one platform for Colleagues and Suppliers to be able to easily collaborate, input data, manage their relationships and maintain products throughout their shelf life.
Creating storyboards
Storyboarding the scenarios highlighted the interactions between the Suppliers and Colleagues and identified the key features and requirements for the product.


Store Locator
Create a new internal tool to allow Colleagues to better manage store data and therefore be able to support customers by improving how this information is displayed.

The Problem
RMS is an unstable, legacy system which does not provide the capabilities the business needs to be able to fulfil stores management. The opportunity exists to leverage an existing platform SLA to enhance the application to provide the necessary experience fit for user needs
Discovery
Through analysing the existing tool (RMS) it was identified that the current process was complex, time consuming and involved a lot of interaction between different teams throughout the process.
The stores creation process involved a lot of manual entry with little data validation, questioning the quality of the information that is available to customers and colleagues.
Testing
Working closely with a UX designer we analysed the existing terminology used to convey the instore services and facilities. The usage of a service and a facility was complex, with the same item appearing across multiple types making it confusing to understand what it actually was.
I set up an initial card sort test to get customers to bucket the items into sections that made the most sense to them. Taking the results from this and what already made sense from the existing layout, I created a Tree Jack test on User Zoom. This asked a different set of customers a number of questions to see if they could find the correct location.
Analysing both test results we produced a new structure that we validated with Colleagues to ensure that what made sense for Customers was also clear for Colleagues. These enables us to ensure the two experiences are aligned, but also helps with a future vision of bringing.
Designing an experience that works for Colleagues
From understanding the existing experience it was possible to identify at a field level the data required. This then made it easy to design a streamlined user experience to minimise the manual input, by removing the need to input fixed information and therefore reducing the risk of data error.
Knowing the data requirements allowed me to move into a design iterations process, looking at the interactions for the user on how they would create a new store. It was important to understand the way the system was currently used in order to make sure this new process would worked alongside this. The two primary uses were identified as being able to search for an existing store or to create a new one.

