• What is your expected timeline and schedule for testing?
• When do you need a final report?
• How many iterations of testing, if more than one? When and where? (What cities are being targeted?)

TESTING INFORMATION

• What is the objective of user testing?
  1. What are your priorities? What do you want to know at the end of the test?
  2. Who at your company is or will be interested in the results of a usability test?
  3. Who will be invited to observe the user interviews/tests?
• Do you have a list of known issues/user complaints with your current site? Who has that information?
• What do you want to be tested? Is it a functioning prototype, live site/application, screenshots or paper?
  1. Do you have any user test plans that are already done? Any other relevant documentation?
  2. Descriptions of already completed formal or ad hoc or informal testing?
  3. Do you have documents that define how the elements on each page are expected to work given as many user actions as possible - for example, information about all possible functionalities for each form
• How should users use the site?
  1. Do you have user flows for your redesign/current design?
  2. Do you have site flowcharts which show linear information flow?
  3. Do you have IA documentation?

USER TEST PLAN INFORMATION

• What demographic information do you want to know about your users?
• You can collect general information about users' connection speeds, CPU types, etc. Do you want that sort of information?
• What cases/scenarios do you want to watch users to do? Such as finding a product, registering, logging in, uploading, downloading, opening an account, wiring money, etc.
• You can ask users a lot of general/overview questions about the site, such as:
  1. What do you think of the overall design and layout?
  2. What are you supposed to do here?
  3. What stands out? What is the first thing you notice on the page?
  4. How many ads are on this page?
  5. What do you like about the site? What do you hate about the site?
• Do you want to ask questions about content such as "what content would you like to see on the site that you've seen at other similar sites?"
• What sorts of navigation questions do you want to know about? for example:
  1. Navigate to home page from somewhere on the site
  2. Finding help
  3. How do you sign up to become a member?
  4. How do get to a particular section of the site?

USER INFORMATION

• How many users do you plan to interview? (recommend 8-12)
• What demographics of users will be tested? How is the screener and profile defined?
  1. Gender, Age
  2. Profession, Education
  3. Web-savviness
  4. Income
• Who will recruit the users? Do you have current registered users you could use?
• Are there any users that you would like to "disqualify?" (such as people who work for your competitors)
• How many types of users?
  1. One type of user or 2 or 3 to compare (i.e. people who've used the web for more than 1 year and people who've used the web for less than 1 year)
• Will users be required to sign NDAs or Informed Consent forms (to consent to being videotaped)? If so, make sure it's just 1 page.
• How do you plan to compensate users? 

LOGISTICAL/TECHNICAL INFORMATION

• What hardware and software do you need for testing? Operating system, Web browser, CPU, Monitor size and resolution, color depth, connection speed, required plugins
• Where will testing take place? At a rented lab? Or at your office in a conference room? Or at users' home/offices?
  1. In what city or cities will testing take place?
• URL for testing? login/password? or access to prototype? How will it be accessed?
• Will there be an observer who's also taking notes to put in the final report of recommendations?
• Will the user sessions be videotaped (picture in picture of the computer screen and the user's face)? (you can also watch during user testing)
• Do you want a 10-15min. edited video of the best parts of the user sessions?

DELIVERABLES

• Who's managing the details of the project?
• Who's developing the screener/profile?
• Who's recruiting and scheduling?
• Who's writing the test plan/interview guide?
• Who's test driving?
• Who's interviewing the users?
• Who's compiling the results?
• Who decides what to change/revise/add as a result of the testing? Who makes the revisions?

ADDITIONAL INFORMATION

• anything else?