Business Operations & Strategy

The Business Operations & Strategy (BizOps) team is made up of Business Operations, Data Operations, and Analytics. This page contains information that is relevant to the whole company, and each of the links below will take you to subteam-specific information. There are plans to split up the Business Operations and Data and Analytics teams, which will happen sometime after the Director of Data and Analytics position is filled. At this point, everything in this section applies to all functional areas.

Functional areas




See the Operations OKRs for the Ops team’s full OKRs. Below are the BizOps-specific OKRs:

  • KR: Complete a migration off of BigQuery for ETLs (to dbt, Airflow, or similar)
  • KR: Every product team, go-to-market team and company-wide has at least one automated KPI dashboard sent into Slack
  • KR: Build a scalable marketing data infrastructure to support ROI analysis (and specifically, have a system in place for tracking multi-touch attribution of leads)
  • KR: Every L2 and above product or feature release and update is measured as successful or not, beyond just being delivered on time
  • KR: TBD: Institute a cleaner, more thoughtful data architecture with documentation
  • KR: TBD: Working on getting sales insights and recommendations scoped so we list specific things to be delivered

Note: TBD KRs are not fully scoped and therefore intentionally vague, but are on this list because it’s something we will likely spend time on in

Goals roadmap

We also work on projects outside of our specific key results that fall within overall themes of our OKRs (Upgrade systems and automate processes, Proactively help the business make better decisions, Build an operational foundation to prepare for Sourcegraph Cloud). The full list of non-ad-hoc projects and timelines can be found on the BizOps roadmap.

How to work with us

Requests for deliverables

The Business Operations team accepts work requests through GitHub issues in the Sourcegraph analytics repository. Any request that doesn’t have an attached GitHub issue will not have an assigned individual and expected timeline, and won’t be tracked by the team.

Examples of requests that require an issue:

  • requesting a new dashboard
  • getting a question answered with data (e.g. “I would like to know the number of MAUs for the Batch Changes feature”)
  • requesting analytics support for a new feature (e.g. “Can we start tracking page views of our case studies”)
  • finding a bug in our data or data pipeline (e.g. “I ran a SQL query and the data does not match my expectations”)

GitHub issues help us manage requests by including as much relevant information as possible. Please use the relevant issue template in the repository and fill out the requested information. If no template matches, create a blank issue and include as many details around your request as possible. These points are normally useful:

  • The problem: Describe the problem or question you have.
  • End state: What is the end state of the project? What decisions will be made? Be as specific as possible (i.e. if the end state is a graph, draw out the graph in Figma, on paper and upload a PDF, etc)
  • The why: What will this request be used for? How does it support Sourcegraph’s company and team goals?
  • Timeline: What’s the timeline of the project? Is it urgent? When does this need to be delivered, and how will it be followed up upon in the future?
  • People: Who is involved, and what are the expectations of each person? Who will be responsible for driving the project forward? Does each person have the necessary bandwidth to uphold the expectations asked of them?

A BizOps team member will triage and assign issues to the relevant team member.

For time-sensitive and urgent requests, please tag the issue with the urgent label. This will make the GitHub issue appear in the #analytics channel in Slack to ensure visibility, where you can follow up with more details/asks.

What a great request looks like

  • The problem: We don’t have a great high-level dashboard for the product/eng leadership team to get a pulse on our product KPIs.
  • End state: PDF of a sketch and a doc of all the metrics.
  • The why: This will play a part in prioritizing product/eng projects, understanding feature adoption, progress towards OKRs, etc
  • Timeline: By for a first draft would be ideal!
  • People: Nick and Christina will be responsible for usage of the dashboard and suggesting modifications. This will be delivered (automatically) into #TBD Slack channel every Monday.

General contact

To get in touch with us, or ask for our input or help:

How we work

We use GitHub issues in the Sourcegraph analytics repository to track projects, and the Business Operations Kanban board for tracking current projects.

Slack channels

  • #business-ops to interact with the Business Operations team (e.g. questions you know are specifically for us)
  • #business-ops-internal for internal BizOps communication
  • #analytics for anything related to analytics; not just the Business Operations team (e.g the impact on a shift from HubSpot to Marketo, sharing a deliverable that has cross-functional impact, or a question related to data you don’t know where to ask). This channel has previously been a catch-all for Business Operations, and we’ll be pushing you all towards business-ops for those topics
  • #analytics-review for help with self-service and WIP data projects (questions about the data, requests for peer review). Although we do expect to be involved in this quite a bit, it’s not just meant to get feedback from Business Operations. We will also be using this channel to have our work peer reviewed and collaborate with other folks from different parts of the business! Anybody comfortable enough with data can be a peer reviewer or answer questions
  • #data-eng-ops for Data Ops communication