Versions Compared

Old Version 1

changes.mady.by.user Anonymous

Saved on

compared with

New Version Current

changes.mady.by.user Jesilyn Barnes

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Field Study November 12, 2018

Initial Questions and Methods: http://bit.ly/RegTesting
Test Planning: http://bit.ly/RegUXResearch
Project: New Registration

...

  1. Plan in advance what designs or tools you need for the visit, who’s going, create a schedule.
  2. Think about ways to Intercept them, once they get to the store, during check out line, when?
  3. Open questions: Try to ask questions that don’t have only Yes - No answers.
  4. Speak their language, our customers use daily language, not a proper one.
  5. Interact with the device - Let them take control of the device and ask them to think-aloud.
  6. Add few more targeted questions about things like layout and design, not just about the tasks.
  7. Building our relations with the Branches and associates. How can we continue to do that better? Try bringing some donuts for them or something else. Explain to them what we’re doing, and ask them if they have ideas or know customers that could help.
  8. Lina: Speak slower
  9. Identify Blockers and let the manager know beforehand.
  10. Planning Document should include:
    1. Estimated Calendar or Schedule
    2. People who are working on the project are the ones should be there, designer, writer, etc.
    3. Who is going and their roles?
  11. Include in the Script all those things we discover in the visit, all the process before the customer and setting up: Who from Ferguson we should talk, which one is the best branch, why is the right method, etc. Once we got to the branch we didn’t know what to expect, and the Manager just showed us a place behind the counter where we could stand but nothing else.
  12. Rehearse the Script and do it with people involved before going to the branch. Define roles and who’s going in advance.
  13. Coming up with solutions or designing make sure to keep in mind that we are doing an MVP, identifying “Nice features” vs “Needed Features”. It’s good to work together to prioritize features between “Nice to have” vs “Must have”. Any fancy functionality that doesn’t affect the actual functionality will take longer, especially if they haven’t done it before, BUT don’t limit your designs if you want it in there keep it, just let IT know to organize ideas and have the best possible design.

Moderated Remote Test February 2019

Initial Questions and Methods: http://bit.ly/SingCheckQuestions
Test Planning: http://bit.ly/SingCheckTest  
Project: Single-Page Checkout

...