Mostly on survey outcomes

1. PRODUCT

2. Survey

3. handbook/
product/
survey

4. Quantitative outcomes
64 responses, 40 from sales

5. What is the best 'selling' feature of GitLab?
Why?
25x: CI integrated with SCM
24x: Single application for entire lifecyle
4x: SCM
Rest: Approvals, HA, Security

6. What feature / change are (potential)
customers most excited about? Why?
1. Security features
2. Issues (incl. portfolio management), CI
3. Kubernetes
4. Almost every other feature in GitLab

7. What should we be working on, that we're
not currently (or are planning to)? Why?
1. Issues (incl. portfolio management)
2. SCM / Code review
3. HA
4. Everything else

8. What are we doing product-wise that we
shouldn't be doing? Why?
No consensus whatsoever, but some highlights:
—Spend less time on X, where X is currently dominated by
other players in the market (JIRA, security tools,
AutoDevops)
—Building out more breadth
—Adding features to Core/Starter

9. Conclusions
1. There is a lack of insight in what we're building
2. It's unclear how we make decisions
3. We're not consistent in giving feedback

10. Actions
There is a lack of insight in
what we're building
—Easier to consume plans: /direction/manage
—Easier to reach PMs: /product/handbook/
categories
—PM/EM FGUs

11. Actions
It's unclear how we make
decisions
Prioritization process added to each /direction/
[manage,plan, ..] page

12. Actions
We're not consistent in giving
feedback
1. In doubt, ping a PM: /handbook/product/
categories
2. Maintain the Single Source of Truth: Issues
3. Keep up with the feedback!

13. Questions?
—What am I most excited about? => Q4
—Are we doing more depth now? =>
—Biggest concern? =>
# $
/
—11.4 best release ever? =>
✅
—When is GitLab 12.0 happening => March 22nd, 2019
—Best editor? => VSCode + GitLab extension by Fatih
—How is my daughter doing? =>
—What is your favorite emoji? => /