Timeline for UX Comparative Test?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 5, 2017 at 17:14 | comment | added | Petar Subotic | For validity sake, you can't have the same participant do both versions, brings in a huge "previous knowledge" impact. Some sort of a split has to occur. | |
| Dec 6, 2016 at 9:45 | comment | added | SteveD | I am not sure you quite understand what A/B testing is. I am wondering if you are thinking it means building and deploying two different solutions to your whole user base, while you monitor a wide range of analytics? A/B testing can be done this way, but its definition is nothing more than comparing two designs with two groups of participants. Those designs can be paper prototypes, white board prototypes, Axure/Balsamiq/Invision/Photoshop prototypes, html prototypes or stubbed-out code prototype. 5 or 6 participants per design is OK for a usability test. | |
| Dec 5, 2016 at 17:43 | comment | added | SteveD | I do A/B testing with low number using paper prototypes as well as Axure prototypes. Why do you think it needs lots of users? You have 12 so split them into 2 groups of 6. You can still learn insights with low numbers. | |
| Dec 5, 2016 at 17:32 | comment | added | UXG | Thanks for your suggestion, but unfortunately I'm unable to do an AB test due to resourcing etc, otherwise I would have. This method is far more suited to AB testing and being run over a larger population than 12 users. However, I' in a position where I need to evaluate it using an invision prototype so I'm thinking qualitative testing with some method of quantifying attitudes towards behavior in some way. So assessing how likely users are to be influenced or not, and why etc. Then user a likert scale to quantify their preference to one over another. | |
| Dec 5, 2016 at 17:17 | history | answered | SteveD | CC BY-SA 3.0 |