http://www.uie.com/brainsparks/2006/08/30/resources-for-adventurous-usability-techniques/ UIE\'s latest insights on the world of design Wed, 19 Jun 2013 13:13:40 +0000 hourly 1 http://wordpress.org/?v=3.4.1 http://www.uie.com/brainsparks/2006/08/30/resources-for-adventurous-usability-techniques/comment-page-1/#comment-143470 Web in the burbs » So that logo… Wed, 13 Aug 2008 09:02:10 +0000 http://www.uie.com/brainsparks/?p=314#comment-143470 [...] Looking Back on 16 Years of Paper Prototyping - Jared Spool [...] [...] Looking Back on 16 Years of Paper Prototyping – Jared Spool [...]

]]> http://www.uie.com/brainsparks/2006/08/30/resources-for-adventurous-usability-techniques/comment-page-1/#comment-23174 adaptive path » blog » blog archive » Signposts for the Week ending September 1, 2006 Fri, 01 Sep 2006 15:46:01 +0000 http://www.uie.com/brainsparks/?p=314#comment-23174 [...] The cool kids are all abuzz about Flickr adding geotagging. Jeff Veen explains why. (For more fun in this space (pun intended), check out MIT’s PlaceMap Project.) Crazy good collection of links from UIE on field research. [...] [...] The cool kids are all abuzz about Flickr adding geotagging. Jeff Veen explains why. (For more fun in this space (pun intended), check out MIT’s PlaceMap Project.) Crazy good collection of links from UIE on field research. [...]

]]> http://www.uie.com/brainsparks/2006/08/30/resources-for-adventurous-usability-techniques/comment-page-1/#comment-23102 Words and Software : Resources for prototyping Thu, 31 Aug 2006 20:03:35 +0000 http://www.uie.com/brainsparks/?p=314#comment-23102 [...] So, let's talk about prototyping instead, just because the User Interface Engineering blog posted an excellent collection of resources yesterday. I wrote a bit about our usability testing last year (has it been that long already?). We used a prototype then, although it was a bit more sophisticated than the paper prototypes mentioned in this article. Although there are great arguments for paper prototyping based on costs and time and efficiency, I think the emotional one is key. As the author explains: "Modifying a paper prototype is much less painful than for the developers than modifying an actual product. With a real product, because of the substantial amount of work they've put in, the team has an emotional investment in the status quo and will naturally tend to "defend" their design. Even when the team clearly understands the need for changes, it's tough to throw away all that hard work. In contrast, because paper prototypes are so easy to create and modify, there is less invested effort to defend. As a result, development teams become more flexible and willing to try new ideas." Filed Under: User experience [...] [...] So, let’s talk about prototyping instead, just because the User Interface Engineering blog posted an excellent collection of resources yesterday. I wrote a bit about our usability testing last year (has it been that long already?). We used a prototype then, although it was a bit more sophisticated than the paper prototypes mentioned in this article. Although there are great arguments for paper prototyping based on costs and time and efficiency, I think the emotional one is key. As the author explains: “Modifying a paper prototype is much less painful than for the developers than modifying an actual product. With a real product, because of the substantial amount of work they’ve put in, the team has an emotional investment in the status quo and will naturally tend to “defend” their design. Even when the team clearly understands the need for changes, it’s tough to throw away all that hard work. In contrast, because paper prototypes are so easy to create and modify, there is less invested effort to defend. As a result, development teams become more flexible and willing to try new ideas.” Filed Under: User experience [...]

]]>