On Nov. 23, I (meaning Anthroguy, aka Hank Delcore) visited the Microsoft campus in Redmond, WA, to give a talk and do some knowledge exchange with colleagues in user experience and product planning. Nelle Steele, an old friend from grad school in Madison, WI, facilitated the visit. Nelle works on a user research team associated with Microsoft Office, obviously a massive MS division. It was fascinating getting an inside look at MS workspaces, organization and work style.
Being Thanksgiving week, many people were gone and others who had planned to come excused themselves due to looming deadlines. (Jonathan Grudin had accepted an invitation to come but unfortunately couldn’t make it.) One thing others have noted about MS was confirmed during my visit: this is a hard driving, “type A” organization where it’s all about what you can deliver. One designer brought some sketches to work on while I spoke — which I thought was great. He had a meeting the next day and had to have something ready.
The purpose of my talk was to fill the MS folks in on design anthropology at Fresno State and the work of the Institute of Public Anthropology. I ran down some curricular innovations we’ve fielded recently and described some recent IPA projects with ArcHop and the Library Study.
My other goal was to gauge how well we are prepping our students — anthro majors, business, engineering, etc. — for design-oriented work at places like Microsoft. What I heard was that we are doing lots right. One UX research manager singled out our emphasis on interdisciplinary teamwork as crucial — that’s the reality at MS, but the weakness of many highly capable experts from all fields. The other important thing we do is to help students, in their IPA-related projects, make the leap from data to design insight to concrete recommendation. MS and many other organizations demand you justify your existence by pointing to real impact, which means it’s not enough to produce good research — you have to effect change and drive implementation.
One thing I took away that I need to work sensitivity to product life cycle more into our curriculum and IPA practice. You have to know where you are in the product development cycle to know what kind of recommendations are helpful — our students need to know more about that. One product planner also noted that it’s helpful to know how to think about the links between the product and the larger strategy behind the product or even the entire organization.
This was all good stuff. It was helpful for me to see a slice of how Microsoft works and hear from some people on the front lines. On the Microsoft side, they seemed excited by the IPA’s emphasis on design research and the rich educational experiences our students are receiving. We discussed some possible points of collaboration between the IPA and Microsoft — we’ll see how those develop over the next few months.
Thanks to Nelle Steele for making my visit happen!