We strive to make the following true:
- The team is working on the most important things on our strategy, and that it is communicated well both inside and outside of Sourcegraph.
- Each teammate has the customer and product context needed about customer problems, likely future priorities, possible solutions, etc. to perform their work effectively.
You can reach us at the #ask-product channel or @product-team on Slack. If you have ideas you want to pass on to the product team, check out the surfacing product feedback page.
Roadmap & Strategy
- The Sourcegraph strategy page containing our mission, vision, how we think about prioritization
- Roadmap tracker
- The PMM roadmap deck (internal only) which contains upcoming and recently launched important customer-facing features
Building a public or customer-facing roadmap means trading-off flexibility vs predictability. One extreme is to have no customer-facing roadmap at all, and be able to change direction without any impact. The other is to have a 12-month or more committed roadmap and not being able to change plans without costly communication to reset expectations. Our strategy, engineering capacity, and customer and market feedback are the inputs that drive the roadmap. If one of those changes, the roadmap will change as well.
We value flexibility over predictability, because that allows us to react faster to customer feedback and market changes. That said, we also want to give our largest customers visibility into key stable areas of our enterprise-readiness plans.
Here are the principles we apply for our roadmap:
- Focus on the direction and high level 1-year narrative. This helps our customers understand what problems we want to solve for them, independently of the specific feeatures we’re building.
- 3-month roadmap. We build a 3-month roadmap. It’s updated after each job fair cycle, and smaller updates as changes happen during a cycle.
- The roadmap includes experimental, beta and GA features, as defined in docs.
- We aim for 90% confidence in our 3-month roadmap: typically, out of 10 planned features, 1 will be dropped.
- Best effort 6-month+ roadmap for enterprise readiness. For mature features, we strive to build a longer-term roadmap for enterprise-readiness
- Cody is experimental. Its roadmap will be a 3-month outlook, subject to change as we focus on iterating to deliver the best product to our users.
- Codehost support has less customer and market unknowns. The main factor of uncertainty is engineering capacity. So we will strive to provide a longer term roadmap to inform our customers and go-to-market effort, provided that we get the go-ahead from capacity planning (VP Eng is the ultimate decision maker).
- Product team reference
- Roles and responsibilities of the product team
- Beta and experimental feature labels (internal only)
- Sourcegraph messaging
- RFCs (requests for comment)
- All RFC documents (Google Drive)
- How we use RFCs
- User research
- Product licensing
- Product Gaps Dashboard (internal only)
- Use cases
- Product team tools
- Product career development framework