There are several sites I go to again and again for their original content and comprehensive resource lists of methods and tools. And who doesn’t love a list?
Earlier in the year I had the good fortune of presenting to a class from the University of Technology, Sydney’s Interaction Design course. As someone who occasionally hires designers, experience in user testing and a sincere integration of users in the design process is what makes candidates stand out. Why? Because this is what reduces errors, minimizes IT and build change requests and helps ensure users can understand and use our products. It’s a mistake to think something has to be detailed and almost production ready to be tested. Test ideas, test sketches, test digital, test services. Test early, iteratively and often.
This week a colleague rushed up asking how long it would take to produce a journey map and the answer was … it depends.
The Australia Institute celebrates Go Home on Time Day today November 19. This is certainly something that my partner would hope that I take part in.
There are some great UX/UCD resources online — my favourites to date have been Service Design Tools and more recently UX Mastery. But today I was knocked out by the phenomenal effort to define and encapsulate design research activities in a cohesive project framework. It was all revealed by a rather innocuous tweet that did not quite foretell the brilliance ahead.
While I was a student I worked in retail. At one store we were encouraged (forgive me if you hate sales assistants) to ask open questions to invite conversation. It’s harder that it sounds. Years later while being trained in user research we were encouraged to ask why. Not only why, but as many whys as we could … and you know why … to get to the root cause, that deep fundamental driver of behaviour. Of course this too is not as easy as it sounds. Unless you’re a charming 5 year old asking why can sound pretty obnoxious and being asked why can make anyone feel quite defensive. I’m guessing advice like this has its roots in the famous 5 Whys, which I take to be a tool of analysis, not a script. If you disagree with anything here, or have more to add please say so in the comments.
Debriefing as soon as possible after your research encounter is vital. Push yourself beyond first impressions with these 10 questions.
Ethnography for Marketers: A Guide to Consumer Immersion was recommended to me in 2007, I finally got round to reading it in 2010 and the other day I revisited the copious notes I took. This is a book about ethnography, research, projects and design. But why write a blog post that is a book review? Particular when the subject is essentially a text book?