Date: Fri, 29 Mar 2024 13:40:46 +0000 (UTC) Message-ID: <2053026539.5.1711719646527@8e1da7a6bc51> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_4_3416667.1711719646526" ------=_Part_4_3416667.1711719646526 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
"When you come to a fork in th= e road, take it." - Yogi Berra
Once we=E2=80=99ve constructed one or more trees to test, and come up wi= th a list of the tasks we=E2=80=99d like our users to try, we should take t= ime to pause and congratulate ourselves =E2=80=93 most of the heavy lifting= is done.
Now we need to turn this raw material into an actual test that we can ru= n with users. Luckily, the tools now available make this a fairly straightf= orward process, as well as offering a raft of handy options to tailor the t= est to our needs.
In this chapter, we=E2=80=99ll cover how to get a test set up, and which= of those options we should choose when.
Tips to make our tests easy to identify later
Avoid giving away the grouping method and client
For the prompts and controls shown by the tool
If we need to keep the study private
Finishing manually, by # of participants, or by date <= /p>
Linking back to a panel, to another study, or to a recruiting survey
Pointers to Chapters 6 and 7
Welcome message, instructions, thanks message, and T&C
For screening, splitting results, research, comments, etc.
Setting the logo and color scheme
For participants' questions, concerns, or suggestions
In case customers inquire about it