On 8 Oct 2009, at 16:59, Jared Spool wrote:
On Oct 6, 2009, at 3:09 AM, Jonas Söderström wrote:
loved your post about getting the team to observe users, instead of
doing traditional usability tests. (Loved the way you presented the
same thoughts at IA Summit in Miami last year, too, btw!)
I'm glad _somebody_ liked it. :) Thank you!
I liked it too if it's any comfort!
Let's say we're developing a new version of an existing service.
Based on the insights from your research - what do you think would
be the best strategy?
To stick with letting the team watch users use the existing version
- and thus, over the project, collect richer and richer real
experience, and trust that the teams design skills will provide us
with good solutions for the new version?
Or should we make the users try our gradually developed prototypes
of the new product, in session after session?
I'm going to disagree with Adrian here and say there is a lot of
value to having the team watch users with the existing version. If
you structure the study right, you'll learn a lot about:
[sensible ideas snipped]
Agree completely. It was the idea of using the existing product as the
sole target of usability testing that I had problems with... obviously
having one of my miscommunication days :-)
Cheers,
Adrian
--
http://quietstars.com - twitter.com/adrianh - delicious.com/adrianh
________________________________________________________________
Welcome to the Interaction Design Association (IxDA)!
To post to this list ....... [email protected]
Unsubscribe ................ http://www.ixda.org/unsubscribe
List Guidelines ............ http://www.ixda.org/guidelines
List Help .................. http://www.ixda.org/help
