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.
I recently read
I have a BUNCH of notes from books and articles I have read on design research. I had reason to revisit them all recently when I was writing a training course and thought to share them as a set of reference tools for others, you dear reader, and as a memory boost for me on our next field trip.
Working for a customer experience consultancy, as I do, I am always on the look out for stories about customer activism or advocacy — so I was very interested in this story on the SMH about the influence of a customer in the removal of soft porn content from the Telstra BigPond service. Except it wasn’t quite the story I had read in the Saturday paper, which I have quaintly photographed and included for you below.
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?