A brand new feature designed for iRiS suite of products helping to maximise F&B performance with recommendations linked to an item.

UX Design Lead

UI design

User research

Prototyping & Testing

related items hero.png


A related item is a paired menu item that is presented to a user in different parts of the journey.


The new feature has been designed for all iRiS Guest products in order to maximise F&B revenues.

related items research.png


While the back-end team started the works on implementing the new feature on iRiS Guest platform, I researched popular F&B solutions focusing my attention on how they have implemented this upselling tool and the semantic in place.


Based on conducted research I mocked up 2o Lo-Fi prototypes and analysed 2 scenarios:

(1) Related items presented to the user at ‘Item’ level


(2) Related items presented to the user at ‘Cart’ level


I decided to run a user testing session to validate assumptions and gather feedback on the way the RI feature was presented on iRiS Guest mobile app. 

22 participants, paired in 2, were presented with a Hi-Fi prototype I built and asked to complete 2 orders in 10 minutes adding related items. 

cart with related item.png
related items user testing.png


After reviewing and sorting users feedback, it was clear that Scenario 1 was the winner. From conducted researches and Lo-Fi wireframes, all the signs pointed at introducing this feature at ‘Cart’ level but, as it turned out, users understood better the concept of related items at item level. They declared that the semantic made more sense in the scenario 1 were the upselling selection was in fact ‘related’ to the item they were viewing.

It was suggested that the cart would be a good place to see offers or promotions on generic items.

related items findings.png

Take aways

  • The importance of validate findings with user testing is paramount. 

  • Recording a user session (and asking for permission first) is fundamental. There were many things that escaped my attention and I was only able to capture them when I listened to the session later on.

  • Never assume what the participants to the session might (or might not) know about the feature you are testing.