Are teams ignoring your user research? 6 keys to increasing impact

Traditional Approach: Researchers conduct the research and share highlights and clips in a report and debrief. Result: Stakeholders gain a superficial understanding of users and their needs.

Team Approach: The stakeholder team observes significant amounts of raw user research directly and in depth. Result: Stakeholders develop a deep understanding of users and their needs.

Traditional Approach: The team that watches extended research is limited, often to just researchers. Result: Development, product and design teams fail to align on many critical decisions.

Team Approach: Non-researchers, including designers, developers, product owners, and management, are part of the team gaining in-depth exposure to users. Result: Teams develop a shared understanding about users and reach consensus on key decisions more often.

Diversity + depth: marketers, product owners, and developers watch full user interviews and usability sessions.

Traditional Approach: Most stakeholders’ research exposure is limited to large, ad hoc, and infrequent studies — twice a year at best. Result: It is easy to ignore persistent problems and forget about user needs.

Team Approach: Over time the diverse stakeholder teams observe in-depth user research at least once every 6 weeks. Result: It is hard to ignore persistent problems — and easy to keep an accurate picture of users in mind during design decisions.

Example of a repeatable 2-week testing cycle we developed for an enterprise tech organization

Traditional Approach: Researchers analyze and synthesize the research and share their problem findings in a report and debrief. Result: Stakeholders often hear what they want to hear, and dismiss findings that contradict their assumptions. Disagreement about top problems persists.

Team Approach: Researchers teach stakeholders design thinking techniques and facilitate a structured process to analyze and synthesize problem findings as a team. Result: False assumptions die quickly, and the team gets on the same page about the biggest problems worth solving.

Stakeholders collaborate to post, group, summarize and prioritize their research findings.

Traditional Approach: Researchers brainstorm ideas and recommend solutions in a report or debrief — sometimes supported by sketches or wireframes. Result: Stakeholders dismiss solutions they don’t like — often rightly so. But because they lack the research context and/or design skills, they struggle to generate alternative solutions that move the needle.

Team Approach: Researchers lead stakeholders through a step-by-step process to generate, sketch, combine, and critique ideas — both individually and in small teams. Result: Because they generated the solutions themselves, teams are more likely to implement them. And because those solutions embraced design thinking and the diverse knowledge of the team, they succeed more often.

A software director, IT architect, and QA analyst collaborate on solution sketches.

Traditional Approach: Researchers focus on 1) analyzing research, 2) designing solutions, 3) and presenting reports. Their value lies in UX expertise plus their ability to persuade others. Result: Relationships are often tense. Partner teams “just don’t get” researchers’ advice; researchers “just don’t get” the team’s business/IT/design constraints.

Team Approach: Researchers focus on 1) exposing teams to users, 2) teaching research methods and design thinking, and 3) creating a habit of user research. Their value lies in facilitation, empowerment, and program-building. Result: Because the partner team is an active player throughout the process, both sides work through disagreements in real time, with data. Relationships are more harmonious and productive.

After some training, a product owner and developer practice running their own concept test sessions.

When we bring these 6 keys together, we get this single, guiding principle statement:

For a user research program to be effective and impactful, it must empower a diverse stakeholder group to frequently observe users directly and in depth, and to analyze and solve problems collaboratively — supported by expert facilitation.

The team approach to research isn’t a silver bullet. It has plenty of challenges, such as getting partner teams to invest the necessary time to observe research and teaching engineers to ask open-ended interview questions.

But in our experience, these are solvable challenges in many organizations, especially when you start small and practice patience. As 1 or 2 teams experience the power of collaborative user research, they spread the word to other teams, and momentum builds.

Over time, instead of telling teams about their users, you’ll be teaching teams how to conduct their own user research. And eventually, your impact as a researcher will grow in ways you never thought was possible when your only deliverable was a report.

Categorized as UX

Leave a comment

Your email address will not be published.