Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Writing successful research questions #57

Open
lindsayboylan opened this issue Jun 24, 2020 · 0 comments
Open

Writing successful research questions #57

lindsayboylan opened this issue Jun 24, 2020 · 0 comments
Labels

Comments

@lindsayboylan
Copy link

lindsayboylan commented Jun 24, 2020

General Guidelines

  • Avoid leading questions and try to talk as little as possible, if you can. Let the participant lead and fill any gaps in speaking.
  • Try not to pre-fill your questions with answers. If they need prompting, that's okay, but avoid blurting out "for example....xyz"
  • Ask for specific, past examples. Users are inherently bad at predicting future behavior. They self-report how they want to see themselves or want to act rather than what they'd actually do.
  • As an interviewer, you should ask open-ended questions that allow users to explore options and question their own responses to really get into the 'why'. Practice the 5 Whys technique.
  • Use your script as a guide, not a list of bullet points you absolutely must hit. There are no extra points for asking every question! Make your participant as comfortable as possible. If you need to skip or re-word a question, that's okay.
  • Both your participant AND you need to be comfortable. You can end the session at any time if you deem necessary.

Testing-Specific Questions

  • I find it helpful to give broader scenarios rather than specific questions. This keeps you from writing leading questions that turn into "ok do this, then this, then this" and lets us see how someone would actually navigate your prototype.
  • Obviously, not all prototypes lend to this strategy, so be sure to write your goals first and then I find it easiest to write the questions & construct the prototype at the same time.
  • Again, open-ended, non-leading questions are best. A good rule of thumb is if you're looking for more, your question shouldn't be able to be answered with a "yes" or "no." However, sometimes you just need to know!

Helpful Reads

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant