validate your product with usability testing

Validate your Product with Usability Testing

BY NEARSOFT UXTEAM

http://ux.nearsoft.com/

HOST

Kim LantisContent Coordinator

@kimlantis

PRESENTER

Diana ArvayoUX Researcher

@dianonina

PRESENTER

Mónica TyeProduct Owner

@monicatyeb

https://twitter.com/kimlantis




https://twitter.com/dianonina




https://twitter.com/monicatyeb

https://twitter.com/monicatyeb

Agenda- Major Challenge for Software Development Teams

- How Usability Testing helps teams validate products

- Case Study: Retrospectives

- Takeaways

- Q&A

#NearsoftUXwebinarVALIDATE YOUR PRODUCT WITH USABILITY TESTING

CHALLENGE

REWORK50% of programmers’ time during a project is spent doing rework!

VALIDATE YOUR PRODUCT WITH USABILITY TESTING

http://www.usability.gov/what-and-why/benefits-of-ucd.html




With UX you save money by reducing rework.


CHALLENGE

REWORK

For every $1 invested in UX, the ROI can be anywhere from $10 to $100!


CHALLENGE

REWORK

Myth



Reality

Bye, bye!!!


Usability TestingHow people use your product and for what purpose


Usability TestingWhat people say vs. what people do


Hangouts or Skype

Record the Audio


Tasks & Script


Case Study

https://marketplace.atlassian.com/plugins/retrospectives4confluence/cloud/overview


● Launch a product● User Retention● Validate Ideas

When Should I Use Usability Testing

1. Set the goal

2. Define the audience

3. Write the tasks you will test

4. Prepare the setting and recording

devices

5. Run the session

6. Analyze the findings

7. Iterate

How to Run a Usability Test?



1. Set the Goal

● Set the goal based on your prototype

● Features to test

● Workflows (Login, Edit, etc)


Our goal with usability tests was to determine if our add-on was user friendly and intuitive, and if the features we had in mind were valuable to users.

1. Set the Goal


??¿? ?

¿¿?


● New or returning?

● Ask for lists of people who have contacted customer service or

the help desk

● Look for users in their natural habitat

● Use Social Media for example MeetUp!, Linkedin Groups,

Slack Communities

● Reward them :)

2. Define Audience & Recruit Participants


2. Define Audience & Recruit Participants

● Familiar with Confluence

● Had participated in Retrospective

sessions with their teams


3. Write Tasks You Will Test

● Consider the goal of the study

● Leave out clues or hints

● Avoid having micro-steps

● Give the test participant a goal but avoid describing the steps


3. Write Tasks You Will Test

● Right and wrong during the sprint

● Grouping similar ideas

● Voting for the most important ideas

● Creating Action items

● Getting a summary of the retrospective


4. Prepare the Setting and Recording Devices

● Friendly reminder

● Practice reading your script aloud

● Identify if you need an observer. If not, be sure to have an audio

recording device (your phone will be useful for that)

● Set up (location, internet, battery, etc.)


● InVision Prototype

● Recording screen by using QuickTime

● Development team took notes as observers

● Printed out script

4. Prepare the Setting and Recording Devices

Retrospective’s Prototype


5. Run the Session

● Make them feel comfortable

● We are evaluating the product, not you

● Your feedback will help us improve the product

● Make them aware that you will be quiet most of the time

● Instruct users to speak while working

● Avoid explaining or defending the product

● Avoid answering questions, rather ask, “What do you think?”


5. Run the Session

● 7 Usability Tests

● InVision Prototype


6. Analyze the Findings

● Review by task

● Study how the user reacted (emotions or expressions)

● How many participants ran into the same issues?

● What the user was trying to do vs. What the user did

● Which tasks were most (un)successful? Why?

● Are users successful, but slow?


6. Analyze the Findings

● Add instructions in some steps

● Users needed someone in the retrospective to be a moderator

to guide the team through the steps

1. Validated features

2. Prioritized backlog

3. Discovered a need for new

features

4. Reduced rework

Benefits ofUsability Testing


1. Put your assumptions to the test

2. Involve other team members

3. Don’t take all feedback literally. Don’t attempt to fix all the issues you found, focus on critical errors first

4. Include User Testing in your next sprint planning

5. Test again, again, and again!!!

TAKEAWAYS:

Validate your Product with Usability Testing


“Usability is about people andhow they understand and use

things, not about technology.”


― Steve Krug

Thanks! Want to know More?

Contact Sandra at (408) 890-2115

ux.nearsoft.com


[email protected]





Want to try out our

Retrospectives add-on?

Download it at Atlassian’s Marketplace and start

running your retro sessions inside Confluence!






validate your product with usability testing

Business