**Strategy** * As research has been scaling across GitLab, feedback has revealed that it's difficult for GitLab team members to understand: * what research is being conducted * what was learned from it * what decisions were made based from the insights * The Research team needs a scalable, informative, and broad communication plan which demonstrates one of the GitLab values: transparency. **Where are we now?** * Presently, some teams have difficulty understanding what the Research team is working on, who is doing what (non-researchers, in particular), and what we're learning about our customers. * There isn't a mechanism in place to share research findings back to FirstLook. This community is an important participant pool for UX Researcher; as they help us identify insights. **Where do we want to be?** * To offer a deeper level of transparency to our team members about what research is being conducted across GitLab. * To be able to tell our research projects in the form of engaging stories. * We also want to share our research insights and processes with our customers. In addition to exhibiting transparency, this approach also educates GitLab customers (and potential GitLab customers) about our development process at GitLab. * Lastly, sharing research findings back with the FirstLook panel can demonstrate to them the value they bring to GitLab. **How will we get there?** * By taking an iterative approach: piece the strategy into small issues to complete in a quicker cadence than a single large project, pilot, iterate, repeat * Shift to a storytelling approach when informing audiences about specific research projects * This will require effort mainly from the UX Researchers, who will define the details and manage the UX Research Team Communication Plan (link to define this in the Handbook). Researchers will also be responsible for creating the story for a given research project their team is fielding.