GitLab Workspaces: Competitive Analysis
Problem to solve
Opportunity Canvas: https://docs.google.com/document/d/19E2EBnIJowyi2Es6AZTBMONWEYqqaREbDUPUyrwyNJw/edit#
Handy links
- Competitive analysis: https://medium.com/user-research/competitive-analysis-b02daf26a96e
- Product development flow: https://about.gitlab.com/handbook/product-development-flow/
Competitors
- Jetbrains: https://www.jetbrains.com/space/
- GitHub: https://github.blog/2010-06-29-introducing-organizations/
- Asana: https://asana.com/guide/help/workspaces/basics
- JIRA: https://confluence.atlassian.com/jirasoftwareserver/setting-up-your-workspace-938845051.html
- Azure DevOps: https://docs.microsoft.com/en-us/azure/devops/organizations/accounts/create-organization?view=azure-devops
Problem/JTBD
GitLab customers don't currently have a way to create users, have or assign admin permissions or operate as an autonomous instance on GitLab.com. The current infrastructure, without Workspaces, is confining and limits the flexibility customers need to manage their groups and teams.
The lack of Workspaces creates a barrier between self-managed and GitLab.com implementations that forces a trade-off decision for customers and generally reduces value for GitLab.com customers until feature parity is obtained for self-managed features.
GitLab.com is also not a fully secure solution for subscribed customers. We should ensure that customers have total privacy and zero risk of data leaking into other groups.
What questions are you trying to answer?
- How are our competitors solving this problem?
WIP Documentation
Tasks
- ...
- ..
- ...