Jul 25, 2013
Three questions that waste time without returning value during user interviews.
seen from Australia
seen from United Kingdom
seen from United States
seen from Germany
seen from China
seen from China
seen from Malaysia
seen from Hong Kong SAR China
seen from Italy
seen from Syria
seen from Poland
seen from China
seen from China
seen from Sweden
seen from United States
seen from China
seen from Germany
seen from United States
seen from Italy
seen from United States
Three questions that waste time without returning value during user interviews.
> "The problem is, adding the box to the beginning of the schedule doesn’t stop derailment. But if our goal is to pass the blame on to stakeholders we interviewed, saying “you didn’t tell us up front when we asked,” then we can declare this as mission accomplished. However, if our goal is to produce a great design that delights our users and meets their needs, we need to move on from adding a box to the schedule to a set of activities that work."
> "In our work with design teams, we see a lot of teams using prototypes today. We’re also seeing many of those same teams fall into traps that reduce the effectiveness of their prototyping efforts. Here’s five of the most common ones we see."
Fascinating thoughts and data on implementing redesigns. It's still difficult or impossible for many of us to avoid flipping the switch and ruining experiences for loyal users due to business models, but this kind of data helps.
> "To kick things off we're delighted to introduce our first UXmas goody for 2012. A free virtual seminar entitled 'Build a Winning UX Strategy from the Kano Model', generously provided (and presented) by Jared Spool of User Interface Engineering (retail value $129)."
How to find the missing expectations with which users approach our designs. This shows how usability testing isn't the right method for finding out this stuff, but we've got to go into a more sophisticated approach, and actually observe people doing what they actually do.
"If people love change, why do our users complain when we make changes to our designs? Well, it’s not because of their aversion. It’s because we did it wrong. And that’s the root of Google’s struggle every time they make a change. Google isn’t the only one, either."
"Jared M. Spool explains how a design studio workshop can help your team work through various design challenges and the benefits these workshops bring to the team."