13

Our Design Team's Process for Running Usability Tests Every 2 Weeks

over 6 years ago from , Design @ OneSignal

At Mesosphere we've set up a process that enables us to run usability tests every 2 weeks.

  • We use Intercom, Pardot and PowWow to help us recruit users
  • We offer gift card incentives
  • We conduct the tests on-site or remotely via Hangouts
  • We dedicate 1 day every 2 weeks and run 5 tests
  • We test features that are built, design prototypes, and value hypothesis

Read the full post here

How does this compare to how you and your team run usability tests? Any other recommendations?

6 comments

  • Megan VoMegan Vo, over 6 years ago

    Great write up! I'm curious what the significance of "remember to take a photo of the users" is?

    0 points
    • Lee MunroeLee Munroe, over 6 years ago

      Thanks! I find it helps provide some context for when sharing our reports. Helps those reading the report visualize who was testing it. Also helps me when I'm looking back at previous reports, seeing a photo can help me remember the user and what we chatted about.

      0 points
  • Charles PearsonCharles Pearson, over 6 years ago

    Great process, thanks for writing it up and sharing. Its nice when the full value of research can be recognized. ;)

    0 points
  • Sherizan SheikhSherizan Sheikh, over 6 years ago

    Great process! We have similar structure. What I am curious is "post-tests". What do you do with the valuable feedback and what plans are made to put those valuable data into action?

    0 points
    • Lee MunroeLee Munroe, over 6 years ago

      Good question. Since the report is in our Wiki, we use inline commenting to have discussions around each issue and pull in the relevant PM, lead developer or lead designer. Out of that we either modify our designs and prototypes, if it's something we're working on, or if it has already been built create an issue for developers to look at (we use Jira). If it's something major then we'll pull in relevant team members and discuss over a whiteboard.

      Also worth noting we tag our usability test reports in a way that they are pulled in to product requirement wikis, so hopefully they are always referenced even in future projects.

      0 points