At the end of a workshop about person-focused research, someone asked “So, why do people decide to buy an iPhone versus an Android phone?” Smiling, I turned to the rest of the people in the room and asked them to answer. Silence ensued. This post, first published as How to Keep Designers from Defaulting, tries to remind JohnnyHolland readers of the perennial design research assumption: evaluation.
How to Keep Designers from Defaulting
What is the best way to protect yourself from defaulting to an existing product? At the end of a workshop I taught in Silicon Valley in April 2011, where I had emphasized the difference between evaluative and generative research, a participant asked, “So I’m still not sure how I would research why people decide to buy an iPhone or an Android or a Win7 phone.”
Smiling, I turned to the rest of the people in the room and asked them to answer her. Silence ensued. Wide eyes and cocked eyebrows stared at me. True, it was nearly nine o’clock at night and everyone was tired. Yet even at midday, fired up on caffeine, smart professionals get stuck at this same point. We still couch our questions based on existing artifacts or ideas.
Instead, ask the root question. “When on the go, why do you stay in touch, and with whom or with what?” This root question is a generative question. It will enable you to empathize with the person who might buy one of the phones listed—or might not. This empathy will help you design better tools for them.