Argos - Android
Solving one of Argos' most requested issues - Implementing Inventory availability, and enhancing the shopping experience for all our customers.
Timeframe - Jan 2018 - Mar 2019 Role - Senior Product Designer
Timeframe - Jan 2018 - Mar 2019
Role - Senior Product Designer
I immediately began by auditing the existing Android build with UX architect Carl hattley, looking thoroughly at the app and where pain points existed in the experience. We mapped out the entire app and discussed with project managers and developers at ideas we wanted to work on and include in the app to enhance the experience.
At the same time, I was building the Argos android design system and component library consistent with our newly defined rules. This would make designing new features and handing over to development so much easier and efficient.
One of the biggest problems at Argos was stock and product availability, and our customer's thought this was a massive issue. Because of the infrastructure and logistics of Argos, a customer assumed that there shouldn't be a problem in getting products faster, but in reality, it was far more complex than this.
Product availability was one of the biggest tasks to implement in the Argos android app, and this would be a trial to see if we could reduce what we called internally as PDP bounce back, where the user was tapping into a product description page and exiting quickly because the product was out of stock. We needed to inform our customer's that the product was in or out of stock earlier in the journey to minimise repetition and enhance the shopping experience.
Along with UX support, we created many ideas and concepts for how product availability could work from only showing in-stock items, to having a toggle switch within the search filters. None of these ideas was acceptable as they're hidden or degraded our search results, so we opted to make our search and product listing pages smarter.
What we proposed was when a user searched for a product and landed on the search results, they would also see a small module which asked them if they wanted the item delivered or if they wanted to collect it. Depending on which option was selected, they were then asked to either enter their postcode for delivery or to select a store for collection.
Once the user had made a selection, the search results would instantly update with a new colour-coded label on the product cells, which highlighted whether the item was in stock, out of stock or low accordingly.
Our proposed method was designed, built and released within the space of 3 months after many user testing sessions and iterations we significantly reduced PDP bounce back.
Anthony Eamens 2021©
Anthony Eamens 2020©