So many product research projects focus on influencing a decision, for which the researcher provides very specific insights about a specific portion of the overall problem.The beauty of Participatory Design projects is that the focus in not only on the initial task-at-hand that needs to be solved by the group, but also that the unstated goal becomes raising the knowledge of the people in the room.
When engaging in formative, strategic research for my product teams, and by engaging them throughout the process, my goal is to inform my stakeholders about a broader, more holistic context of use.
I hadn’t thought about this particularly, until a design director at work said to my director, “I want to work with you. But my people can’t focus on anything but research that helps them design what they are working on right now.” [Read into that “can’t” what you will] His meaning was that I can’t spend time sharing insights with the designers that don’t directly answer questions about this widget or that widget. Very disappointing. Especially when I’ve developed good relationships with the Product Managers, Marketing Managers and Engineers by sharing stories and insights about user experiences that helps to raise there OVERALL understanding of how people use communication tools.
My purpose for this kind of sharing of insights is mainly driven by my belief that I am not at MOST of the meetings where decisions are made– if they are even made in meetings. I also can’t research every little question that comes up, “Should this button go here or here?” “Do people share photos or quotes more often?” Therefore I need to arm the decision makers with an empathy and understanding of how different users make choices, so that EVERY decision they make is a bit more informed by real end-users.