Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Current »


 

Testing online with commercial tools

Most tree testing is now done online, so the “where” is really the participant’s PC or tablet or phone, wherever it may be. While their device is out of our control, we can check some things up front:

  • Do we know of any firewalls or network restrictions that will hamper certain participant groups in our audience?
    This is most common when targeting users in a large organization.

  • Are our participants running a compatible browser?
    Again, this is mostly a problem with large organizations who may be locked into older browser versions, or with users who have older mobile devices.

For more on dealing with this, see Checking for technical problems in Chapter 10.

 

Testing in person

If we’re testing on paper, or doing an online test face-to-face with a participant (see ~page for reasons why we would want to do this), then the “where” becomes important.

While a full discussion of how to host participants is beyond the scope of this guide, there are some basic points we should consider when planning an in-person session:

  • When recruiting participants, be clear how much time we will need (20-30 minutes for the tree test and subsequent discussion, more if we’re doing additional activities with them).

  • Also be clear that this is a one-on-one session (not a group session that they can more easily blow off), and that they’ll be reading text (from cards or a computer screen) so they should be reading glasses if they need them.

  • If they’re visiting us, be sure we give them clear directions and/or a map, parking tips (if they’re driving), and what to do when they arrive (wait at reception, walk up to the second floor, go to room 101, etc.).

  • If we are visiting them, find out where to park, and don’t go alone (for both our security and theirs). Oh, and take slippers (in case we need to remove our shoes).

  • Confirm our session with the participant the day before, and exchange mobile phone numbers in case something goes wrong on the day.

For more on hosting user-research sessions, see ~web resource or UT book.

  • move to recruiting/running-a-test chapters?

 


Next: Who will do what?

  • No labels