Strategic research is focused on answering future facing questions about users that help inform the long term product direction and roadmap. This kind of research can consist of one or more connected projects to better understand a larger topic area. Usually, the topic is broad enough to cover multiple stage groups and/or stages. Thus, strategic research can be high impact for the product teams and company as a whole.
We can use Strategic research to:
Understand how to apply a solution across different territories or groups of people. For example, consider how a different industry, like lawyers curating legal documentation, could leverage source control management for versioning.
Explore additional constraints to the current problem to make it more future proof – for example, adding the number of concurrent users to support on a feature.
Consider upstream and downstream experiences – for example, enhancing the Verify experience for GitLab users by using Auto DevOps to help them get started more easily with Continuous Integration.
Identify emerging market trends. For example, if customers are signaling an interest in their maturity for adopting DevOps, uncover ways can GitLab coach people in their maturity using Machine Learning or AI.
How does GitLab think about Strategic research?
Strategic research is research that is:
Conducted to directly inform the strategy of a team and/or organization
Aimed at answering broader research questions, not specific to a single stage area or feature
Seeks to understand and challenge current assumptions of feature functionality
Engages cross-stage or multi-stage stakeholders
Defines unmet needs
Results in the addition, refinement, or removal of personas
How is Strategic research measured?
Success will be measured by the impact of the research, at the project level. As strategic research matures at GitLab, we will look for common measures of success that could be applied to all strategic research projects.
Examples of Strategic research topics:
Understanding stage usage trends
Expanding understanding of our customers’ motivations, goals, challenges, and needs
Identifying our customers’ biggest IT initatives/goals
Understanding how GitLab can overcome DevOps adoption pains
Understanding more about cross-stage use cases and workflows
Identifying ways Ops can drive adoption across multiple stages and stage groups
Creating Actionable Insights connected to cross-stage group issues to be scheduled in the next 1 year
Examples of Strategic research from recent projects:
Release Manager Persona Addition was a great example of a cross-stage and multi-group strategic research effort that resulted in an update to the Roles and Personas page. This positively impacted the entire Ops Section and helped us reach new audiences in the Ultimate tier.
KubeCon Ops Product Direction Survey was a large scale project that was able to inform the future product roadmap within Ops. This was done through obtaining valuable feedback about what CI/CD workflows are most challenging for GitLab users and learning what perference users had in mind for their ideal secrets solution.
Strategic research outputs
The outputs from Strategic Research can be found in issues, changes made to documentation, and in published changes to a category direction page (which includes 1 year and 3 year visions), such as:
What is GitLab Adoption Research? As a solution, GitLab is considered a DevOps Platform. The DevOps platform is a single application that eliminates complex integrations, data chokepoints, and toolchain maintenance, resulting in greater productivity. This single application is made up of our GitLab stages. In order for us to better understand DevOps Platform adoption, we must understand how and why users are adopting more stages.
In our research on adoption, we have learned new namespaces adopting 3 or more stages have significant differences from those namespaces not adopting multiple stages.
