Sainsbury’s Meal Planner

During a two-week design sprint my task was to create a microsite for Sainsbury’s where users could create their own meal plan, upload and order meals based on their own recipes, reorder previously selected meals and finally to stop users ordering items they may already have.

Tools & methods used:

· User interviews

· Card sorting

· Design studio

· Sketching

· User flows

· User Journeys

· OmniGraffle

· Invision


To get a better understanding of what is required, a competitive analysis was completed looking at some direct and indirect rivals of Sainsbury’s. This helped find that Tesco provided all the features that Sainsbury’s required.

Three personas were provided who all have different needs. The aim was to focus on one user, Jackie, whilst considering the needs of the rest. An interview was also conducted of someone who fits persona of Jackie to find out more information.

‘I already have some recipe ideas which I like to cook each week. Can I order these ingredients as well?’

Card sorting:

It was decided that an open card sort would be used to create the navigation scheme. This was done with three people to understand how they would categorise the cards provided to them. The were some common phrases which were used by all three participants. These headings were then used as part of the final navigation scheme.

Design studio:

A design studio of five people was organised to tackle the issue of the user reordering items they may already own. This was a 30-minute process where each participant sketched out 4 potential solutions to the problem at hand. Each idea was pitched to the group where each member developed another solution based on everyone’s feedback. The group then came up with one final solution which addressed this issue.


Multiple prototypes were developed and tested from low level sketches to mid-fidelity wireframes created in OmniGraffle.

The first stage of testing found an issue with the user not wanting to serve the same people for all the days they desire to cook on. Other issues which occurred was the use of iconography and the user misinterpreting the button.

‘What if I want to serve two people on Monday and six people on Friday?’
‘Why not just have an icon on items I have previously purchased?’

Through testing, another solution was provided to stop users repurchasing items they may already have. It was originally shown that the items would be shown along the side of the screen whilst one of my users suggested to have a notification icon on the items that may not need to be purchased.

Next steps:

To take the product forward it would be important to consider how the site could be made responsive. This would allow users to have a comfortable experience using the site on their mobiles & tablets.

A single golf clap? Or a long standing ovation?

By clapping more or less, you can signal to us which stories really stand out.