User Testing and Reporting

Data powers design! Whenever possible I like to run user tests and surveys to direct mine and my team’s designs.

Why Test?

  1. Identify problems, bugs, and stumbling blocks that we have overlooked by being too familiar with the product.
  2. Validate assumptions about design “improvements” (or let go of those assumptions if they turn out to be wrong).
  3. Convince leadership, finance, and engineering teams that design is a worthy investment.
  4. Perform basic A/B tests and compare designs against one another, or against a competitor.
  5. Learn about how different demographics react to different designs.
  6. And finally, because I always learn something about another part of the product that I wasn’t looking for!

Example Reports

Number of Mentions for Certain Topics (taken from direct quotes)

 

Preview Thumbnail for PDF of Study: Reviews
User Test: How to Improve Reviews Section

 

Preview Thumbnail for PDF of Study: Location of Hotel Description

Preview Thumbnail for PDF of Study: Location of Hotel Description
User Test: Where Should the Hotel Description be Placed

 

Preview Thumbnail for PDF of Study: Showing Lead Pricing vs. Add-On Pricing
User Test: Showing Lead Pricing vs. Add-On Pricing

Preview Thumbnail for PDF of Study: Showing Average per Person Pricing vs. Total Pricing

Preview Thumbnail for PDF of Study: See whether users prefer carousels or masonic galleries
User Test: Do Users Prefer Images Shown in Carousel or Masonic Format