openfoodfoundation / product-pipe

A place for product circle to organize their tasks
0 stars 0 forks source link

Checkout & next button usertesting 12 / 2020 #21

Closed Erioldoesdesign closed 3 years ago

Erioldoesdesign commented 3 years ago

This issue will capture the Usertesting process and script for testing the checkout with user-testers with a particular focus on discovering how the 'Next' buttons are used, perceived and whether they could/should be removed or re-worked.

The checkout for OFN is likely to be refactored to be a stepped (1 - 2 - 3 etc.) process: "Matt has raised that splitting the checkout into 2 steps would help him working on adjustments
we are not sure yet we will do it, we are just exploring options and estimates"

We'll carry on with the user-testing in order to discover meaningful information for people on how they progress from a shop product list through the checkout details.

The script is located here in notion: https://www.notion.so/openfoodnetwork/Check-out-next-buttons-08ed15c9ecd44d6ba458bbb1967517d7

The digital notes will be located here in comments and anonymised.

The recordings (if the user tester agrees) will be located in a secure drive accessible only by people with access to OFN storage spaces.

Erioldoesdesign commented 3 years ago

@jaycmb Here's the user-testing issue with a link to the script for review :)

Erioldoesdesign commented 3 years ago

Usertesting and synthesis completed for this! https://www.notion.so/openfoodnetwork/Check-out-next-buttons-08ed15c9ecd44d6ba458bbb1967517d7

RachL commented 3 years ago

@Erioldoesdesign thanks! It looks super interesting. I'm wondering about the use of notion for that: do we want to store all user-based information there? I'm wondering about the long-term best place for this info.

Erioldoesdesign commented 3 years ago

@RachL mostly chose notion for ease of structure as in it already has our docs and such!

I do need to send the participants the digital notes before they go 'open' but all participants were asked if they are ok with anonymised notes being on a OSS repo. So what I would do once people given the a-ok over written notes is publish these in a github issue or possibly a gitbook depending on OFN community preference.

Definitely pro-open research though so I don't want this kind of insight locked behind a login wall.

Erioldoesdesign commented 3 years ago

Closing out this issue with open user testing research.

Plan & Script

https://app.zenhub.com/workspaces/product--inception-pipe-5f82e534db531f000f8c09ff/issues/openfoodfoundation/inception-pipe/21

There was a lack of clarity about the usability of the next buttons on the checkout process so Eriol of the design team has set up usertesting to collect qualitative data alongside some quantitative data from analytics tools to help choose a direction.

Usertesting Script

5 tests, split 3 desktop 3 mobile (virtual on the computer via dev tools)

Target User

Test with max 6 users who are likely to be regular and reasonably proficient online shoppers for food and/or groceries. They don't need to be experts in online shopping, but know it exists and have placed at leas one shopping order within the last 3-6 months.

Housekeeping questions

Scenario preamble

We're testing part of the experience of shopping on the Open Food Network in order to better understand how real people use an online shopping kind of experience to purchase food and other produce. The Open Food Network platform is a way of finding local food hubs or producers to purchase goods from that aims to shorten the food supply chain so food and produce comes from 'farm to table' much quicker with fewer 'middle services' like large lorry/truck transport and grocery chain store mark-up. We're going to default to the UK site unless there is an operational OFN in your country of residence.

I’ll ask you some questions about your online shopping behaviours first, then to complete 2-3 tasks using the website we're testing and then ask some general questions at the end, if that’s alright. The test should not take longer than 30 minutes.

You have no need to feel pressure here, we’re testing the designs, not you, so don’t be afraid to explore and speak your mind.

You don’t need to worry about hurting our feelings. We have very thick skin, so don’t be afraid to be brutally honest.

It helps a lot for our analysis if you can think out loud and describe what you’re doing as much as possible while you’re browsing the test website.

If at any point you choose to stop the session, that’s absolutely fine. Just let me know.

Intro questions

  1. Can you tell me the last time you purchased food online?
  2. Was the service you used a large, well known service or brand? like a supermarket chain?
  3. Was is a large or small shop? how long was the produce meant to last you?
  4. Have you ever heard of or used the open food network before? if yes, can you briefly explain how and why you visited?

Tasks

  1. We'll be using google chrome (green yellow and red circle) as a browser if we can.

    For Mobile testers: so we can take advantage of the mobile screen view. I'll walk you through this part.

    1. Open Chrome browser
    2. Go to https://openfoodnetwork.org.uk/eriol-farmer/shop

    Mobile testers!

    1. Right click anywhere in the webpage and choose 'Inspect' from the list of options.
    2. Your webpage might go a little strange to begin with but we'll click a few options so you get to simulate a mobile phone screen.
    3. Top section with a down arrow pointer → opens a list of options → choose Pixel 2 or what model the user uses.
    4. This simulates a mobile phone functionality so we can see a mobile view, but on our computer screen so if you'd take a moment to get in a 'mobile' mindset that would be great!
  2. Attempt to purchase at least 3 items. Allow the user tester to explore and have a little fun here.

  3. Once finished, show me where you would attempt to pay.

  4. Stop once you believe you are on the 'checkout' page.

  5. Take this page slowly, fill in all the details , you can place fake info in these fields. Talk me through each section as you complete it, letting me know what makes sense, what doesn't etc.

    1. Fake name, email@email.com, 0712345678, Flat 1, Random road, Bristol, Somerset, BS1 1QB,
    2. Interviewer notes: Pay close attention to if the tester uses the next buttons and in what circumstances. Pay particular attention to if the user expands the section after clicking next or find any of of 'next' confusing. if they click next more than once. If they scroll the page to double check any information.
  6. Stop just before clicking the 'place order now' and we'll move onto the general wrap up questions.

General feedback

What do you think overall?

Were there any parts of the process that were confusing or difficult?

Were there any specific elements on the page that were difficult to use or hard to understand what was happening?

If the user has still not mentioned the 'Next' button functionality ask this explicit question:

I've noticed that you have not yet mentioned the next buttons in the checkout section. Did these function in a way that made sense to you? Why?

Usertester '1' notes

Located in India.

Typed notes:

Next button info

Usertester '2' notes

Located in USA.

Typed notes:

Next button info

Usertester '3' notes

Located in Chicago USA

Typed notes:

Next button info

Usertester '4' notes

Located in Germany. Tested on virtual mobile in browser.

Typed notes:

Next button info

Usertester '5' notes

Located in USA. Tested on virtual mobile in browser.

Typed notes:

Tasks

Next button info

Usertester '6' notes

Located in USA on East Coast. Tested on virtual mobile in browser.

Typed notes:

Tasks

Next button info

Synthesis of usertesting

There are plenty of insights here on how to improve the shopper experience generally from landing on a shop right through to placing and completing an order.

Key subjects that either came up more than once or were key insights are:

  1. The phrasing in OC's can be confusing. Especially the example of 'Ready for immediately" no testers fully understood what this meant and confused many of them.
  2. Shipping was on every users mind right up until the delivery options. All testers mentioned shipping before thy were presented with the shipping details section of checkout. This means that shipping as a option must be referenced better earlier even if it is not determined in money value earlier there needs to be reassurance for users earlier that it exists.
  3. Typical shopper users find stores without many products confusing until they remember it's a small 'mom and pop' store. This message could carry through to the header section or the product listing as most shopper users did not click on, or read the about page to discover deeper info. They were, understandably, focussed on shopping for produce.
  4. There are many detailed insights on how to better the layout of the checkout details form page below.
  5. The page that some users get before checkout (login vs. checkout as guest) has too much complex information around the simple choice of 'login' or 'checkout as guest'. We don't need all the extra complex info and totals and summaries when users make this choice. A single total line and the two buttons of 'login' or 'checkout as guest' is enough. However, one user wants to know the benefits of signing up or logging in on this page so a simple 'Login to make checkout faster next time!' would suffice.
  6. Next button recommendations are below.
  7. Other insights on the mobile shopping experience can be found here:https://www.notion.so/openfoodnetwork/Mobile-UX-Usertesting-bd8acdcc2071476dbae9511e9de26ce8

Next button and checkout recommendations

Changes to the way the data entry page with next buttons functions is reasonably clear and can be divided into quick or critical wins and longer wins.

Quick or Critical wins

Longer or less critical wins

Form and page structure

Shipping

Transaction fees