FY22-Q1 Engineering Division OKRs

Objective (ARR): Positively impact ARR through efficiency and open source efforts => 65.8%

• Key result: Drive MRARR from 12 to 25 (Quality Department)
• Key result: Materially improve purchasing and licensing workflows to improve sales efficiency through fixing 16 of 16 Fulfillment pain points (Development Department)
• Key result: Provide Engineering requirements to GitLab Private Plan => 65%
  • Support Department
  • Infrastructure Department
• Key result: Build Requester Wait Time (RWT) KPI and decrease by 20% (Support Department)

Objective (Product): Make GitLab more usable, secure, high-quality, and available => 67.8%

• Key result: Increase our SUS score to 72.5 or higher through UX design improvements (UX Department)
• Key result: Supply chain & new regions threat assessment (Security Department)
• Key result: Improve quality SLOs for S1s and S2s for Source Code and Continuous Integration (Development Department)
• Key result: Get signed-off DB sharding architecture evolution => 40%
  • Development Department
  • Infrastructure Department

Objective (Team): Make OKRs more efficient, live our DIB value, and address engagement survey items => 88.9%

• Key result: Run pilot project for OKR tool with one engineering department (Quality Department)
• Key result: URG Coaching Program: Get 15 coach signups, and 9 touch points with vendors
• Key result: Address and communicate CultureAmp survey engagement Survey action items => 82.6%
  • Include company performance update in 3 week's-in-review => 66% (2/3)
    • Feb 1
    • Feb 19
    • N/A
  • Include update about Culture Amp action items in 3 week's-in-review => 66% (2/3)
    • Feb 5
    • Apr 23
    • N/A
  • Every team member has at least one career development conversation with manager => 98.4%
    • Eric's directs => 100% (6/6)
    • Development Department
    • Infrastructure Department
    • Quality Department
    • Security Department
    • Support Department
    • UX Department
  • Conduct "Reverse AMA" with women of R&D and Support with EVP of Product (Scott W) => 100% (1/1)

Cache buster (to get last status in issue URL tooltips): 003

---

Good

• [see department-level issues for detailed retro]
• Generally high achievement across the board
• I learned lots of interesting things from the career development conversations with my reports
• Learned a ton from the Reverse AMA with women of engineering, were able to confirm for them that skip-levels were happening

Bad

• [see department-level issues for detailed retro]
• Sharding should have been in OKRs quarter(s) ago
• Didn't met the URG coaching goal for 1 partner: Latinitas (meant to serve a population we know deserves a better experience)
• Didn't follow thru with 100% of communication KR
• Fending off CI abuse from crypto mining took significant bandwidth from previously agreed upon priorities

Try

• [see department-level issues for detailed retro]
• Ally.io should provide better reminders for things like potential future WIR communication KRs