People frequently ask the CEO things like:
On this page, we document the biggest risks and how we intend to mitigate them.
Biggest risks have numbers attached to them for ease of reference, not for ranking.
We are growing rapidly (more than doubling headcount in CY2019 again), and there is pressure on departments to meet their hiring targets. It is better for us to miss our targets than to hire people who won't be able to perform to our standards since that takes much longer to resolve. To ensure the people we hire make the company better, we:
We are onboarding many people quickly, making it easy for things to fall behind. Therefore we:
As we add more layers of management to accommodate the new people, it's easy to become confused about what is expected of you.
To make sure this is clear we:
It's easy for a culture to get diluted if a company is growing fast. To make our values stronger, we:
Most companies start shipping more slowly as they grow. To keep our pace, we need to:
We were voted The World's Most Productive Remote Team by HackerNoon.
Since we are based on an open source product, there is the risk of fork and commoditize like what AWS experienced with ElasticSearch.
This risk is reduced, because we're application software instead of infrastructure software. Application software is less likely to be forked and commoditized for the following reasons:
|Type of software||Application software||Infrastructure software|
|Interface||Graphical User Interface (GUI)||Application Programming Interface (API)||A GUI is harder to commoditize than an API|
|Compute usage||Drives little compute||Drives lots of compute||Hyperclouds want to drive compute|
|Deployment||Multi-tenant (GitLab.com)||Single tenant managed service (MongoDB Atlas)||Hyperclouds offer mostly managed services|
|Feature richness||Lots of features||Few features||More features leads to more hard to commoditize propietary features|
|Ecosystem activity||Lots of contributions||Few contributions||Infrastructure is more complex to contribute to|
What we need to do is:
Our customers entrust their application code and data to GitLab. A security breach that erodes that trust is a significant risk. To ensure we safeguard our customers data, we:
An economic downturn will likely prolong our sales cycle. Our opportunity should still be there since GitLab saves companies money on licenses and integration effort.
There will always be competitive products. We tend to be much more cost effective because we build on open source, iterate quickly, get open source contributions, and only have to integrate new features with GitLab instead of a large number of tool combinations.
After GitLab core and home-grown DIY devops platforms, GitHub is GitLab's biggest competitor. After the Microsoft acquisition they have started to follow the single application strategy pioneered by GitLab.
In order to counter this risk, GitLab will:
We will always have competition. To deal with competition, operational excellence can be a surprisingly durable competitive advantage.
We encourage operational excellence in the following ways:
Our focus on improvement and commitment to iteration keep us rooted in what's next. This could result in us lowering our ambition. While we focus on what's next, we must also maintain a level of ambition to compete in the future in places where others might not think it is possible today.
We have large competitors and smaller ones. The larger competitors naturally get attention because we compete with them for large customers. According to the innovators dilemma: "the next generation product is not being built for the incumbent's customer set and this large customer set is not interested in the new innovation and keeps demanding more innovation with the incumbent product". So it is really important that we also focus on the needs of smaller users since the next generation product will first be used by them. If we don't do this we risk smaller competitors gaining marketshare there and then having the community and revenue to go up-market.
We serve smaller users by having:
The largest cost in application delivery is typically infrastructure. Large hyper-scale infrastructure providers could bundle their own native DevOps platform usage with their infrastructure. There are a couple of industry trends which limit this risk:
Also, see the fork and commoditize move that is available to hyper-scale infrastructure providers.
Often startups struggle through the transition when founders leave the company, especially when those founders also serve as the CEO.
To ensure we avoid this risk we:
We work Handbook First. As we say,
Having a "handbook first" mentality ensures there is no duplication; the handbook is always up to date, and others are better able to contribute.
If we work handbook second, we risk losing these benefits.
To ensure we avoid this risk, we:
Key people may leave as they vest and achieve their economic goals.
As reflected in our compensation principles, we don't want people to stay because they feel like they have golden handcuffs, but we do recognize the alignment that comes with options vesting. For team members who have been at GitLab for 3.5 years, we offer an option refresh program through which team members are granted a new option grant.
Alternatively, early team members may leave because working at a company the size of GitLab today or the size of GitLab in a year is different than working at an early-stage startup. Big companies are organizationally different than small startups, but there are many things about the spirit of a startup that we can maintain, notably:
Keeping the feel of a small startup, despite a growing headcount, may help retain employees who would otherwise leave.
As the number of layers increase and middle management layers increase, innovation and creativity are stifled. While this could be reflected in loss of velocity, innovation is also about the ideas that are being brought to the table.
In addition to keeping our hiring bar high, we have the benefit of our community to help bring new insights and use cases creating issues. We can keep this momentum by continuing to value and engage with our community. We have Merge Request Coaches who help contributors to get their merge requests to meet the contribution acceptance criteria, and wider community contributions per release is a GitLab KPI.
Ineffective middle management would be a result of lowering the hiring bar. In addition to addressing lowering the hiring bar, we address this specific risk by:
This is especially a problem if there are acquisitions of new technologies. We address this for acquired technology by having acquired organizations remake their functionality inside our single application.
Otherwise, we have a clear and consistent prioritization framework across engineering and product that helps ensure we are continuously making progress on the most important issues.
As more folks work away from customers, it is easy to lose sight of whom we are serving. We can address this by:
We're in a great market and have multiple waves that we're riding: