Internal Developer Portal product category
Goal
Create a new product category: Internal Developer Portal
Context
GitLab positions itself as "the AI powered DevSecOps platform". Based on our 3-year strategy we want to target "Organizations that want an enterprise-grade solution, have a large number of developers, and have complex security and compliance requirements". At the same time, we miss their core interest in our product: to build an internal developer platform.
We know that GitLab product teams are hyper functional, focusing on their core areas exclusively. This resulted in gaps we identified already in the past, like inadequate attention to a solid information architecture. A similar gap is to not having any teams with a mandate to serve platform engineers.
While GitLab can be used by platform engineers to build a code-based internal developer platform, today our customers often build separate UIs on top of GitLab or adopt totally separate products, like Backstage to serve their needs.
Proposal
Create a new product category called Internal Developer Platform and set up a product team with:
- dedicated PM
- dedicated PD
- 2 frontend engineers
- 3 backend engineers (at least two of them senior+)
Who should own this category?
- platform engineering is about project lifecycle management
➡️ Plan or Create - platform engineering is about automation
➡️ Verify (should we rename it?) - platform engineering is partially about compliance
➡️ Govern - platform engineering is about the landing page when a user opens GitLab
➡️ 🤷🏼 - the persona is best understood by
➡️ Deploy and "SaaS Delivery"
We can try to tackle it as a cross-stage initiative, but the reason why we don't serve these users well is because it's a cross-stage user. I recommend a new group under the Deploy stage:
- Environments group
- Continuous Delivery
- Deployment Management
- Environment Management
- Feature flags
- Platform engineering group
- AutoDevOps
⬅️ this is our current platform offering! - Internal Developer Portal
- Infrastructure as Code
- Release Orchestration
- AutoDevOps
Prior art:
Discussion
To help with collaboration, the discussion documents live in Google Docs.