participant observation

Auto Ethnography

by FIONA MOORE, Royal Holloway, University of London “Where is Hassan?” I asked the assembled team of programmers. “And please don’t tell me he’s on the track, running with the automobiles?” Rose tossed her blonde hair and rolled her eyes like the sorority girl she otherwise completely failed to resemble. “OK, but that’s only because he’s down in the garage in his sleeping bag, recharging with the automobiles.” “You really should do something about that, Professor Leibowitz.” That’s Ruth, incisive and sharp, perched on the edge of her wire-frame office chair, chin resting on her hand, fixing me with her birdlike eyes. “Why should he?” Ay shifted his slightly-too-tall frame. “We’re in completely uncharted territory here with these cars. I say, if unorthodox methods work, then use them.” “Mind elaborating, Atticus?” I said, just to see the tension manifest in a tiny quirk at the corner of his mouth. No, he couldn’t help what his parents named him, but I could never quite resist...

Engineers “On The Ground”: Mass Observation at Moto

by STOKES JONES, PREE KOLARI, Motorola CXD   Of course, EPIC has always been a ‘community of praxis’ (as much as practice) helping attendees put what they learn into action. For us at Motorola Mobility, 2013 was no exception. The company had reduced its phone portfolio to a handful of products; and knew the only way to grow market share was expanding sales outside the US. But we had not done ‘front end’ research outside American shores since 2009. Likewise, most of our newly hired designers, product managers, and software engineers had never created phones for any geography but North America. So how could we “sensitize” whole teams to the differing desires & needs of people in Brazil or India? And how could we flush out those devilish details which we didn’t yet know we did not know...the ones that make the difference between a product being “just right” vs. “totally wrong” in a new environment? We decided lone report-writing researchers could not bring product teams in tune with our “next...