Employee Handbook

Product Direction

Credit: https://about.gitlab.com/direction/


Our vision is to replace DevOps toolchains with a single application that is pre-configured to work by default across the entire DevOps lifecycle.

Many organizations are in the midst of evolving from classic development paradigms, to DevOps. They want faster cycle time, higher quality outcomes, and less risk. Every organization, large or small, deserves to operate at peak efficiency. GitLab’s job is to help those companies along, accelerate their evolution, and provide optimized tooling once they get there. We do this by leveraging the best practices of 100,000 organizations co-developing the DevOps platform of their dreams. We deliver breadth over depth, and mature product surface area over time, all the while, focusing on customer results. We’re informed by data, and ROI-driven; balancing that with fleshing out the breadth of our vision as quickly as possible so people everywhere understand where we’re going, what’s possible, and how they can contribute. We believe in the emergent benefits of a single application for the entire DevOps lifecycle.

Background and History

Product Vision, Strategy, and 2020 Plan

The Product Vision Backstory


DevOps Stages


DevOps is a broad space with a lot of complexity. To manage this within GitLab, we break down the DevOps lifecycle into a few different sections, each with its own direction page you can review.

- Includes the Manage, Plan, and Create stages
Ops Section Direction
- Includes the Verify, Package, Release, Configure, and Monitor stages
Secure & Defend Section Direction
- Includes the Secure and Defend stages
Growth Section Direction
- Includes the Growth stage, which includes the Acquisition, Conversion, Expansion, Retention, Fulfillment, and Telemetry groups
Enablement Section Direction
- Includes the Enablement stage, which includes the Distribution, Geo, Memory, Global Search, and Database groups

Want to print your doc?
This is not the way.
Try clicking the ⋯ next to your doc name or using a keyboard shortcut (
) instead.