Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show results on 2019 Q4 Distribution team OKRs #433

Merged
merged 3 commits into from
Jan 7, 2020
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 10 additions & 10 deletions company/okrs/2019_q4.md
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# 2019-Q4 OKRs

1. **CEO: Net new ARR**
1. **Sales (Closing Deals): Reach [$N](https://docs.google.com/document/d/1clukaACTCjPLnmhEttJXcOwadxHEGYK24Znn0HUQGB0/edit#bookmark=kix.n8t17z6iyawc) net new ARR in Q4 by fully onboarding 2 new AEs who will close 4 Tier 1 deals (>=$100K ARR) and 11 non-Tier 1 deals.**
1. **Sales (Closing Deals): Reach [\$N](https://docs.google.com/document/d/1clukaACTCjPLnmhEttJXcOwadxHEGYK24Znn0HUQGB0/edit#bookmark=kix.n8t17z6iyawc) net new ARR in Q4 by fully onboarding 2 new AEs who will close 4 Tier 1 deals (>=\$100K ARR) and 11 non-Tier 1 deals.**
1. Sales (Closing Deals) KR: Get 70% of companies on a free trial to convert to paid customers.
1. **Sales (Deal Optimization): Scale our sales pipeline to 50+ deals per AE, of which 60% of deals are engaged and actively evaluating Sourcegraph.**
1. Sales (Deal Optimization) KR: Maintain company-wide HubSpot consistency to generate actionable reporting from data logged.
Expand All @@ -21,19 +21,19 @@
1. VP Eng KR: 100% of monthly releases ship on time.
1. VP Eng KR: No tier 1 or 2 customers are blocked from upgrading to a monthly release once it ships.
1. **Distribution: Automate time-consuming ops and support tasks.**
1. Distribution KR: Major/minor and patch releases take 1 hour (including general QA but excluding customer-specific testing).
1. Distribution KR: All customer specific testing is complete within 2 business days of tagging any release.
1. Distribution KR: Major/minor and patch releases take 1 hour (including general QA but excluding customer-specific testing). => QA has been fully automated and releases are possible in under an hour. In practice, a 1 hour release has not yet happened due to QA finding release blockers. [RFC 86](https://docs.google.com/document/d/1mbnLHBhEPT2c8ttoxQaQRstivW0JIbKHKtjg-ZRr5WM/edit) addresses how to amortize QA over PRs to eliminate release blockers so that releases can take under an hour.
1. Distribution KR: All customer specific testing is complete within 2 business days of tagging any release. => Now relying primarily on automated QA for most customer testing, excluding a few which did not happen in 2 business days but did take <24h to complete at a later date.
1. **Distribution: Streamline technical blockers for tier-1 customers advancing toward general availability.**
1. Distribution KR: Address all rollout-blocking issues within 1 iteration of reporting.
1. Distribution KR: Scale search and authz to [C1](https://app.hubspot.com/contacts/2762526/company/407948923/) and [C2](https://app.hubspot.com/contacts/2762526/company/1712889883/) requirements by EOY.
1. Distribution KR: Address all rollout-blocking issues within 1 iteration of reporting. => Unclear to me @slimsag what issues fall under this KR, this has been modified from what I saw we agreed upon ("1 iteration of reporting" vs. by Q1?)
1. Distribution KR: Scale search and authz to [C1](https://app.hubspot.com/contacts/2762526/company/407948923/) and [C2](https://app.hubspot.com/contacts/2762526/company/1712889883/) requirements by EOY. => Zoekt is now horizonally scalable and experimental paginated search is available for heavy scripting use cases. Sufficient for C1, unclear for C2 yet.
1. **CEO: Standard developer platform**
1. **VP Eng: Build a world class engineering team.**
1. VP Eng KR: Grow team to plan (+1 code intel, +1 distribution, +1 web app, 1+ core services, +1 manager distribution).
1. VP Eng KR: Handoff of web and core services management responsibilities deemed a success by all involved parties.
1. VP Eng KR: Track career goals for every engineer.
1. **VP Eng: Deliver the product roadmap.**
1. **Distribution: Improve site admin experience.**
1. Distribution KR: Provide additional monitoring and debugging tools to site admins ([#4260](https://github.com/sourcegraph/sourcegraph/issues/4260), [#5547](https://github.com/sourcegraph/sourcegraph/issues/5547), [#5706](https://github.com/sourcegraph/sourcegraph/issues/5706), [#5531](https://github.com/sourcegraph/sourcegraph/issues/5531), [#5369](https://github.com/sourcegraph/sourcegraph/issues/5369), [#5769](https://github.com/sourcegraph/sourcegraph/pull/5769))
1. Distribution KR: Provide additional monitoring and debugging tools to site admins ([#4260](https://github.com/sourcegraph/sourcegraph/issues/4260), [#5547](https://github.com/sourcegraph/sourcegraph/issues/5547), [#5706](https://github.com/sourcegraph/sourcegraph/issues/5706), [#5531](https://github.com/sourcegraph/sourcegraph/issues/5531), [#5369](https://github.com/sourcegraph/sourcegraph/issues/5369), [#5769](https://github.com/sourcegraph/sourcegraph/pull/5769)) => Some progress made, but generally not completed.
1. **Code intel: Deliver LSIF-based code intelligence.**
1. Code intel KR: Support LSIF-based code intel in targeted languages (Go, JavaScript/TypeScript, Python, Java, C#, and C/C++).
1. Code intel KR: LSIF-powered code intel on Sourcegraph.com for at least 1 public project per language.
Expand All @@ -44,11 +44,11 @@
1. Web KR: Increase usage of filters (e.g. filter UI). => Improved filter UI (omni mode, filter highlighting in interactive mode) are expected to ship in Q4.
1. **Web: Data driven decisions for search improvements.**
1. Web KR: Measure number/type of filters used for each search on customer instances.
1. Web KR: Measure the number of searches that result in an error. => We expect to reach approved status on [RFC 79](https://docs.google.com/document/d/
1. Web KR: Measure the number of searches that result in an error. => We expect to reach approved status on [RFC 79](https://docs.google.com/document/d/)
1. **Core services: Sourcegraph search scales to our largest customers.**
1. Core services KR: Symbol and text search returns in under 2s on instances with 80k repositories and configured ACLs for 1k active users.
1. Core services KR: Sourcegraph can index any code independent of code host and version control system.
1. Core services KR: Admins know what percentage of repositories are available for search and when the instance will reach 100% availability.
1. Core services KR: Symbol and text search returns in under 2s on instances with 80k repositories and configured ACLs for 1k active users. => Added horizontal scaling to zoekt and made Bitbucket ACLs APIs more efficient but not going to measure KR as written because customer E is no longer a priority.
1. Core services KR: Sourcegraph can index any code independent of code host and version control system. => Achieved with src-expose but doesn’t support history and no customers using it yet.
1. Core services KR: Admins know what percentage of repositories are available for search and when the instance will reach 100% availability. => This was de-prioritized in favor of automation.
1. **Product: Build a better product.**
1. Product KR: Hire a product manager and UX designer. => Actively seeking [UX designer](https://github.com/sourcegraph/careers/blob/master/job-descriptions/ux-designer.md) and [Product manager](https://github.com/sourcegraph/careers/blob/master/job-descriptions/product-manager.md).
1. Product KR: Sourcegraph users provide feedback as they use the product over time. => Not started, likely to miss.
Expand Down