Fulfillment Q3 OKRs
Overview
This issue will capture proposals for "bottoms up" OKRs from the Fulfillment section. We want to collaborate with all our counterparts and stakeholders to recommend OKRs for the team that we'll surface to leadership.
We had done this in Q2 but the process was a bit disjointed. This quarter we'd like to align on a set of OKRs by July 7th-ish, which will be incorporated directly into VP (and likely CEO) OKRs.
Context:
- Here is the pilot process we're following in Q3: https://about.gitlab.com/handbook/product/product-okrs/#fy22-q3-product-okr-process
- Here is the pilot process we followed in Q2 gitlab-com/Product#2095 (closed)
Contributors: anyone can contribute, but we'll want to be sure the following folks have a chance to review and provide feedback
PM: @justinfarris @tgolubeva @teresatison @amandarueda
EM: @jeromezng @csouthard @rhardarson @chris_baus @jameslopez
UX: @jackib @esybrant @timnoah @mnearents
Support: @shaunmccann @tatkins @doniquesmit @rverschoor @kevenhughes
Enterprise Apps: @ccnelson and team
Sales Ops: @james_harrison @jbrennan1
Format for OKR Proposal
Objective: Expand Cloud Licensing adoption
- KR1 - Introduce mid-term upsell options that will increase adoption by 5%
- KR1 - Roll out "strict" orders limiting purchase options to just Cloud Licensing
Ask
Over the next 2w please recommend OKR proposals on this issue. Anything goes, and we'll discuss/debate your proposal in each comment thread.
Towards the end of the week of 2021-07-05 @justinfarris will collect inputs and provide a final set of recommended OKRs for feedback.
FY22-Q3 OKRs
Objective: Cloud Licensing and service usage data for 100% of eligible new and renewing subscriptions. (CEO - Sid)
- KR: Fulfillment: Cloud licensing and service usage data for 100% of eligible new and renewing subscriptions (Development & Support Departments) (CTO - Eric)
- KR (CPO - Scott): Cloud Licensing and service usage data for 100% of eligible new and renewing subscriptions.
- KR: Fulfillment: Cloud licensing and service usage data for 100% of eligible new and renewing subscriptions @justinfarris
Objective: Improve the purchase experience for new and renewing transactions - @justinfarris @jeromezng
- KR: Complete engineering work to move CI and Storage purchasing to GitLab.com. Complete UX and Product work to move remaining purchase flows - @justinfarris @jeromezng
- KR: Complete frontend engineering work to move CI and Storage purchasing to GitLab.com - @rhardarson
- KR: Complete backend engineering work to move CI and Storage purchasing to GitLab.com - @chris_baus
- KR: Complete non-EoA UX work for subscription & purchases page, upgrade flow, and renewal flow in GitLab.com - @jackib
- KR: Complete non-EoA product work for subscription & purchases page, upgrade flow, and renewal flow in GitLab.com - @justinfarris
- KR: Document all combinations of purchase flows (Trial / Purchase / Renewal / Reconciliation) across SaaS / SM and across CustomersDot and GitLab.com - @rhardarson
- KR: Support counterpart teams with adequate test coverage for CI and Storage purchasing - @vincywilson
- KR: PM identifies and completes problem and solution validation work to remove friction from low-dollar sales assisted transactions - @justinfarris
- KR: Complete migration to Orders Harmonization - @justinfarris @jeromezng
Objective: Improve infrastructure of Fulfillment systems @jeromezng
- KR: Complete migration of CustomersDot from Azure to GCP @jameslopez
- KR: Deprecate LicenseDot application @jameslopez
Objective: Make foundational technical improvements to Fulfillment - @jeromezng
- KR: Develop technical roadmap for metered billing @csouthard
- KR: Transition JiHu to Cloud Licensing @csouthard
- KR: Migrate plans from the CustomersDot code to Zuora using IronBank caching mechanism @tyleramos
- KR: Improve documentation of all Fulfillment systems - @jeromezng
- KR: Document APIs, data models w/ SSoT, data flows, data sync / replication mechanisms for all license systems - @jameslopez
- KR: Document APIs, data models w/ SSoT, data flows, data sync / replication mechanisms for all utilization systems - @csouthard
- KR: Document APIs, data models w/ SSoT, data flows, data sync / replication mechanisms for all purchase systems - @chris_baus
- KR: Document APIs, data models w/ SSoT, data flows, data sync / replication mechanisms for all fulfillment frontend systems - @rhardarson
- KR: Complete research and a technical implementation plan for Company as a first class citizen - @chris_baus
- KR: Increase billing knowledge in Fulfillment - @vitallium
Potential Future OKRs
- Share best practices across engineering managers @jeromezng
- Improve E2E testing to run on commits @vincywilson
- Develop technical roadmap for improving or replacing VCR test suite @vincywilson
- Deprecate mechanizer and move all features into CustomersDot and GitLab admin @justinfarris @jeromezng @jameslopez
- Complete backend engineering work to move to Zuora Orders @chris_baus
- Dockerize CustomersDot application @jameslopez