Creating a user research repository isn’t just about implementing tools. It’s about designing better ways to share knowledge and improve decision-making.
As part of improving your current processes, you will have to introduce changes to stakeholders and teammates. This is where things can get tricky. Organizational initiatives can fail when people forget the emotional side of change.
Implementing any change within an organization requires a deep understanding of how to engage people with the project, especially those who will be impacted by the change.
At this stage, you’re trying to understand and scope the actual project (data and workflow challenges) and trying to identify the hidden agendas within your team (people challenges).
Remember that even if your team is already committed to the idea of building a research repository, you will face resistance at multiple stages, not only within your team but also from adjacent teams. Building an airtight business case will help you navigate some of the inevitable friction more easily.
Your goal is to understand your stakeholder’s expectations and how they will use the data you are planning to centralize.
To get started with those conversations, here are a couple of questions you may want to ask stakeholders:
These conversations will help you identify the gaps in communication and processes that you need to consider when implementing your repository. This is a crucial step in your implementation process and can help you define success with your stakeholders in mind.
If you're building a presentation for stakeholders, make sure it covers:
The type of data you decide to centralize in your user research repository should help researchers connect the dots more quickly, gain more context on the research that has been previously done, and facilitate their analysis process.
It should also help the product team answer questions and build on top of existing insights. Ultimately, it should help other stakeholders to make better decisions and empathize with customers.
Here are some examples of datasets that can be centralized in your repository:
Mapping your internal communication channels will help you understand where information can fall through the cracks and identify the most reliable channel to capture your team’s inputs.
Mapping your channels is about more than just reducing information overload for the team. It’s also about reducing the anxiety other teams experience when they don’t know if their shared feedback has been acknowledged.
Follow these steps and you'll be well on your way to preparing an effective business case that speaks to the concerns of stakeholders and teammates.