FY20-Q1 OKRs

View GitLabs Objective-Key Results for FY20 Q1. Learn more here!

Note: This is the first quarter where we shift our fiscal year. FY20-Q1 will run from February 1, 2019 to April 30, 2019.

CEO: Grow Incremental ACV. More leads. Successful customers, Scalable marketing

  1. Alliances: Measure the value partners can bring to the business. 3 references for each major public/private cloud, establish customer ability to purchase through marketplaces, joint marketing with key partners - 200+ leads per event
  2. CRO: Generate IACV from sales to higher tiers. Target 250 new opportunities created from free accounts, Implement sales motion to show all starter renewal accounts the benefit and value of premium and ultimate, Identify two new already deployed large enterprise free customers in each SAE territory
  3. CRO: Faster delivery of customer value. Deliver plan to have Sales quote implementation services and success plan on all new account quotes, Launch standard implementation model in large segment, Measure time to completed implementation for all new enterprise accounts.
  4. CMO: Recharge Inbound Marketing Engine. Top 10 GitLab.com Pages optimized for inbound, Inbound trial and contact-us strategy documented and baselined, Pages optimized for top 20 non-branded SEO target terms, Inbound strategy for Dev, Sec & Ops personas launched
    1. Content Marketing: Broaden audience reach by increasing new user sessions on the blog by 15%. Create next iteration editorial mission statement and content framework. Publishing plan mapped to key topics, persona, and campaigns. Publish 5 interactive or deep-dive assets.
    2. Content Marketing: Increase social referral traffic 20%. Execute 2 social campaigns. Next iteration social strategy and framework. Create internal social advocacy program.
    3. Content Marketing: Build content paths to support lead flow. Create content strategies for 3 personas/buying groups. Execute plan to increase newsletter subscribers 50%. Contribute 10% of overall click-thrus to form fills.
    4. Digital Marketing programs: Improve Top 10 GitLab.com Pages and increase inbound CTR and conversion rate as measured in marketo form completions by 10% QoQ.Optimize and increase organic search visibility for 20 non-branded terms, Optimize competition pages for better visibility and to assist competitive take-out with 10% increase in CTR from Organic Google.
    5. Digital Marketing programs: 15% QoQ increase in inbound website leads through gated content and paid digital and increase conversion rate with improved nurture. Implement 3 baseline nurture tracks to educate and generate leads within the database, Implement an always-on digital paid program (to include re-targeting, etc.).
    6. Product Marketing: Document buyer’s journey (buyer’s experience, tribe needs). Documented handbook pages of messaging around the 3 core pillars of Dev, Sec & Ops.
    7. Product Marketing: Execute 1 competitive takeout campaign. Create campaign materials (web pages, demos, whitepapers, blogs), perform global sales enablement sessions.
    8. Product Marketing: Identify, evaluate and implement competitor analysis and comparisons strategy. Deliver first 5 comparisons using new strategy.
    9. Product Marketing: Improve case study publish rate. Publish case studies at cadence of at least 2 per month, with at least 3 reference customers using all stages concurrently.
    10. Field Marketing: Create the ABM Framework and tooling. Execute ABM in 5 accounts per region, Identify messaging per account, Execute 1 account-targeted online campaign.
    11. Developer Relations: Increase the number of contributions (not contributors) from the wider community (including Free Team) across selected GitLab projects. For the 11.7 release, the target is 180; for the 11.8 release the target is 200; for the 11.9 release the target is 220.
    12. Developer Relations: Accelerate open source project adoption of GitLab.com. Hire an Open Source Program Manager, gain commitment of 1 big open source project (1000+ contributors) to migrate to GitLab.
    13. Developer Relations: Jumpstart meetups. Schedule 10 meetup events, at least one in every region (EMEA, APAC, NA).
    14. Developer Relations: Increase responsiveness and coverage. Decrease median first reply time to 7 hours while adding two new response channels (GitLab forum, Stack Overflow).
  5. CMO: Achieve marketing process and visibility excellence. 100% visibility into any and all leads at any time, Full-funnel marketing dashboard published in Looker, Unified marketing calendar published.
    1. Digital Marketing programs: Build out a framework and launch for an integrated campaign structure (ICS), execute one campaign, run one competitive take-out sub-campaign and adapt ICS to ABM use cases.
    2. Sales Development: SDR role clarity, defined development path. Clarified Lead Sources, add at least 2 Additional Lead Channels , inbound “call sales” phone line, Drift optimization - implement Drift Account Based Marketing.
    3. Sales Development: Reduce xDR Ramp Time to 3 months. Hire an Onboarding and Enablement Manager (Done), “Expert” Certifications around Personas, Product Tiers, better knowledge management solution: battlecards by persona, vertical.
    4. Field Marketing: Create Field Marketing Dashboard in SFDC. Identify & create the elements for dashboard, Creation of data driven decision framework for field, Improved visibility of field activity.
    5. Field Marketing: Create SLAs around Field Marketing & Marketing Ops. Creation of SLAs for Field Marketing to Ops (ops to field already exists), Create manual dashboard to track SLAs and improve performance, Improve overall speed of contact to MQL cycle time (need baseline).
    6. Developer Relations: Increase responsiveness and coverage. Decrease median first reply time to 7 hours while adding two new response channels (GitLab forum, Stack Overflow).
  6. CMO: Achieve $9.4m in Net New IACV Pipeline created by beginning of Q2 FY20 FY19 (as measured in this report). 720 SAOs delivered to sales by SDRs (Revised definition of SAO as of Jan 2019), 26,000 MQLs created, 11% MQL to SAO conversion rate.
    1. Sales Development: Increase Accepted Opportunity per SDR to 8/month. Rise in reps achieving quota per month. 16 Jan, 18 Feb, 20 Mar, 22 Apr; > 1 significant (3 min+) conversation per rep per day; complete an Outreach.io audit and content improvement.

CEO: Popular next generation product. Grow secure and defend. Grown use of stages (SMAU). iPhone app on iPad.

  1. Product: Increase product breadth. 25% (6 of 22) “new in 2019” categories at minimal maturity, CI/CD for iOS and Android development on GitLab.com, develop an iOS app on GitLab.com web IDE on iPad => 17%, 100%, 100%
  2. Product: Increase product depth for existing categories. Consumption pricing for Linux, Windows, macOS for GitLab.com and self-managed, 50% (11 of 22) “new in 2018” categories at viable maturity => 17%, 36%
  3. Product: Grow use of GitLab for all stages of the DevOps lifecycle. Increase Stage Monthly Active Users (SMAU) 10% m/m for each stage, 3 reference customers using all stages concurrently => 19.3%, 0%
  4. Tech Writing: In 100/100 sampled Support/forum interactions in FY20-Q1, customer-facing product info is incorporated in docs, reinforcing Docs-First Methodology
  5. Alliances: evaluate if key partner services (AKS,EKS,GKE, VKE, etc) can grow use of stages. Conversion of SCM customers to CI/CD through joint GTM.
  6. CRO: Increase CI usage. Perform CI workshop/whiteboard at 2 of the top 10 customers that are only using SCM today in each region/segment by end of Q1.
  7. VPE: Make GitLab.com profitable. Recognize TBD% cost reduction on a per user basis.
  8. VPE: Increase productivity. Increase MRs per engineer 20% for all teams.
    1. Development: Increase velocity. Increase MRs per engineer 20% for all teams.
    2. Development: Develop memory program to reduce memory footprint based on customer feedback Memory OKR.
      1. Fellow: Make GitLab performant with Gitaly atop NFS
      2. Dev: GA of GraphQL to increase throughput for BE and FE. Resolve general topics like performance, abuse prevention and enjoyable development experience. Endpoints for Create and Plan relevant models. Implement new frontend features in Create and Plan only with GraphQL.
        1. Plan BE: Complete steps for general availability of GraphQL. => 70%
      3. Dev: Increase velocity for frontend implementations. Increase throughput by 20%. Have at least 50 gitlab-ui components at the end of Q1. Improve tooling in GitLab itself for JS engineering (webpack map, visual diffing, etc.) by adding 3 new tools to our workflow.
      4. Dev: Improve Performance of JS computation that is done on every page. Improve Initialisation execution by 20%. Reduce main bundle size by 20%.
      5. Manage BE: Take on more maintainer responsibilities: add a CE/EE backend maintainer => 100% (MR)
      6. Manage FE: Increase throughput via proper backlog refinement, improved estimation, and proper issue planning. Also utilize all existing gitlab-ui components for Manage code.
      7. Manage FE: Fully integrate Sentry into the FE org workflow by updating the library, optimize and repair (loading order, configuration, sourcemap support), and determine process for fully utilizing it as an org. Also explore using it in dev, canary, and/or small percentage of production via A/B flipper.
      8. Create BE: Improve maintainability and performance of GitLab Shell: port GitLab Shell to Golang => 43%
      9. Create BE: Take on more maintainer responsibilities: add a CE/EE backend maintainer, add a database maintainer => 50%
      10. Create BE: Prepare Elasticsearch for use on GitLab.com. Improve admin controls, reduce index size => Running at the moment on staging for the gitlab-org group; production readiness is planned for 2019-06-22 (GitLab 12.0)
      11. Sec: Increase Secure throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trendline
        1. Philippe Lafoucrière: Handover to new Secure Engineering Manager. => 100%
        2. Philippe Lafoucrière: CISSP certification. => 0%
        3. Philippe Lafoucrière: Benchmark 3 new security tools for integration in the Security Products. => 10%
      12. Ops (Verify, Release & Package): Increase BE team’s throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trend-line
        1. Kamil Train 2 new maintainers of GitLab Rails,
        2. Kamil Help with building CD features needed to continuously deploy GitLab.com by closing 5 that are either ~“technical debt” or ~“type::bug”
        3. Verify BE: Increase Verify throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trend-line
        4. Verify FE: Reduce implementation time by building on top of gitlab-ui components; increase throughput by building/improving upon JS and Frontend specific tooling by doing product discovery for 2 new tools.
        5. Verify FE: Improve onboarding for new engineers by creating a specific Frontend todo in the overall onbooarding issue.
        6. Release BE: Increase Release throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trend-line
        7. Release FE: Reduce implementation time by building on top of gitlab-ui components; increase throughput by building/improving upon JS and Frontend specific tooling by doing product discovery for 2 new tools.
        8. Release FE: Improve onboarding for new engineers by creating a specific Frontend todo in the overall onbooarding issue.
      13. Ops (Configure & Monitor): Define additional data to complement throughput: Implement a prototype for team pulse and define a path to implement it in GitLab product.
      14. Ops (Configure & Monitor): Increase the groups’s throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trend-line
        1. Configure BE: Increase Configure throughput by 20% and drive consistency week to week: Increase number of MRs week to week, increase number of reviewers and maintainers, and drive consistency in the trend-line
        2. Configure FE: Implement ES2015+ bundles for modern browsers & transpiled ES5 for older ones should reduce bundle size and parsing time
        3. Monitor BE: Increase throughput and consistency, Increase throughput by 20% and even out throughput week to week to bring the standard deviation below 2 for the most recent 12 weeks. As of Jan 4 the standard deviation is 2.8
        4. Monitor FE: Reduce 5% of the css loaded in our main css bundle and implement for 4 additional gitlab-ui components.
      15. Enablement: Communicate and address pain points with issue boards: identify and work with Product to prioritize 5 issues
      16. Enablement: Increase ownership for key GitLab components: add one new maintainer for each of Gitaly, Pages, Workhorse, and the ElasticSearch indexer
        1. Geo BE: support Production team in preparing Geo for DR: enhance selective sync to work at scale, support GitLab Pages
    3. Infrastructure: Make all user-visible services ready for mission-critical workloads while seamlessly supporting delivery of new product functionality and integrating infrastructure solutions in GitLab. [Availability] Definition and tracking of GitLab.com metrics for SLAs, [Product] Deliver OKR Infrastructure workflow and tooling using GitLab, [Introspective] Achieve a 10% cost reduction on GitLab.com spending.
      1. Reliability[AS]: Support SRE-at-large MTBF and MTTR objectives. [Availability] Reduce spin-up time for provisioning auto-scaled servers to <3.5min, [Product] Automate error budgets as a GitLab feature, [Introspective] Deliver new testing environment.
      2. Reliability[DS]: Drive all user-visible services’ MTBF to Infinity. [Availability] Deliver improvements to GitLab.com reliability on two foundational subsystems (ZFS on storage, Kubernetes + Charts), [Product] Take full operational ownership of CI/CD (take oncall from tomscz), [Introspective] Operationalize Vault and Consul.
      3. Reliability[JF]: Drive all user-visible services’ MTTR to less than 60 seconds. [Availability] Implement 4 significant availability features to improve database reliability (autovacuum, masterless backups, pgrepack, replica on ZFS), [Product] Deliver Patroni on GitLab, [Introspective] Deliver full service operational inventory
      4. Delivery: Streamline GitLab deployments on GitLab.com and self-managed releases. [Availability] Create deployment rollback process, [Product] Merge CE/EE codebases, [Introspective] Replace takeoff off with a method better suited for CI pipelines.
      5. Andrew Newdigate: Improve observability for all-user visible services to maximize MTBF and minimize MTTR. [Availability] Deliver distributed tracing on GitLab.com, [Product] Deliver Puma on GitLab and experiments on GitLab.com, [Introspective] Deliver overall service-level tracking in preparation for SLA tracking.
    4. Quality: Build everything in GitLab, move GitLab Insights production ready graphs into GitLab itself. => 75%
    5. Quality: Implement performance monitoring for the development department. Continuous measurement with performance tests for on-prem instances (10K scaled down reference). => 80%
    6. Quality: Improve Engineering velocity. Add 4 Engineering Productivity metrics with historical measures. Monthly throughput, total monthly Merge Requests, Merge Request review time, and time to resolve P1 P2 Bugs. => 80%
    7. Security: Secure the Product. Conduct one Red Team exercise with H1.
      1. AppSec: Security release: complete at least 4 cycles of security release process/checklist X%
      2. AppSec: App sec reviews: conduct at least 4 appsec reviews X%
      3. Compliance: SOC2 Examination Preparation and Gap Assessment: Complete SOC2 Control Statements, supporting documentation, and self-assessment questionnaire, including its distribution 100% GitLab Security Control Statements and Supporting Guidance
      4. Compliance: PCI Compliance: PCI requirements review and self-assessment 100% PCI Runbook
    8. Security: Secure the company.
      1. Strategic Sec: Evaluate at least 2 enterprise centralized SSO solutions and make selection. X%
      2. SecOps: Evaluate at least 2 security monitoring capabilities and deploy in GitLab.com as part of Zero Trust initiative. X%
      3. SecOps: Evaluate at least 2, and implement vulnerability scanning capability for GitLab.com infrastructure. X%
      4. SecOps: Develop and deliver one monthly New Hire Security Orientation training by EOQ. X%
    9. Support: Clarify support expectations within each solution.
    10. Support: Author architecture document for 10k GitLab install with review and approval from Infrastructure..
    11. Support: Improve docs based on solutions to customer reported issues.
    12. UX: Convert more prospects into new GitLab users. Decrease sign-up time to 1 minute or less. Document the existing user journey in video, propose a new sign-up flow, test it with users, and ship the first iteration of the new workflow. Design work is complete, but Implementation has moved from Manage to Fulfillment, currently with P2 priority. => 65% attainment
    13. UX: Provide a guided onboarding experience that helps new users become productive in GitLab more quickly. 80% of new users should start guided onboarding, and 80% of those who start should finish. Create a user journey of current experiences and pain points, propose and test a guided first-time experience, and ship the MVC solution. Design MVC is complete and implementation is in process. => 66% attainment
    14. UX: Improve usability and help beautify our UI by addressing 100% of known color contrast issues and updating CSS according to design system specs. For every stage group, identify areas where we rely solely on color to convey information by performing an audit, creating related issues, and identifying solutions. => 49% attainment
      1. UX Research: Democratize UX Research and prolong the relevance of every research study (scale) by making insights easily findable by anyone. Create a GitLab repository, evaluate 100% of existing studies to identify granular findings and recommendations, and tag every finding with searchable labels (such as stage group and customer type). Insights Repository => 90% attainment
      2. UX Research: Understand how GitLab users currently rate our usability so we can track changes over time. Identify segmenting data (such as customer type and length of use), run a pilot study, analyze data, and re-run a larger study. SUS is complete with basline score of 74.4 => 100% attainment

CEO: Great team. Employer brand, Effective hiring, Increase decision making effectiveness.

  1. CFO: Improve financial reporting and accounting processes to support growth and increased transparency.
    1. Mgr. of Data Team: 100% of executive dashboards completed with goals and definitions
    2. Mgr. of Data Team: Public release of finance metric(s).
    3. Dir. of Bus Ops: Data Quality Process (DQP) completed for ARR, Net and Gross Retention and Customer counts.
    4. FinOps Lead: Integrated financial and hiring model that covers 100% of expense categories driven by IACV (as first iteration) and marketing funnel (as second iteration).
    5. Sr Dir. of Legal: Detailed SoX compliance plan published internally and reviewed by Board.
    6. Sr Acctg Manager: Key internal controls documented in handbook.
  2. CFO: Create scalable infrastructure for achieving headcount growth
    1. Sr Dir. of Legal: 90% of team members covered by scalable employment solution
    2. Payroll and Payments Lead: Automation of contractor payroll completed.
  3. CFO: Improve company wide operational processes
    1. Mgr. of Data Team: All data processes documented with handbook as SSOT
    2. Dir. of Bus Ops: Roadmaps for all staffed business operations functions are shipped and Q2 iteration by EOQ
    3. Controller: Zuora upgrade to orders which will allow for ramped deals, multiple amendments on single quote and MRR by subscription reporting.
  4. VPE: Create a happy and productive team. Unify vacancy descriptions with experience factor content and career matrices for all roles, develop compensation roadmaps for every major role in engineering, hold a roundtable meeting for each role benchmark
    1. Development: Deliver the 2019 roadmap. Hire IC’s to plan, Hire Directors for secure and enablement
    2. Development: Improve customer focus. Get every engineer in one customer conversation
      1. Fellow: Help solve critical customer issues: Solve 1 P1 issue
      2. Dev
        1. Gitter: Improve security practices: Enable use of dev.gitlab.org for security issues, document security release process for gitter.im in partnership with Security => 100%
          • Now using https://dev.gitlab.org/gitlab/gitter/webapp for security releases/fixes
          • Security release process now documented
        2. Manage BE: Increase test coverage for the CustomersDot: increase from 45% to 60% => 56.87% coverage = 79.13% of target
        3. Manage BE: Proactively reduce future security flaws. Identify five areas where we have systematic/pervasive/repeated security flaws, Finalize plan to tackle three areas, 2 merge requests merged => 4 areas identified (80%), 0 MRs merged
        4. Create BE: Increase set of people working on Create features: have team deliver 6 Create Deep Dives => 50%
        5. Plan BE: Add to engineering blog to make it a more attractive destination for customers and prospective candidates. Four blog posts from the team on recent Plan work (including backstage) => 75%
      3. Sec
        1. Secure BE: Improve onboarding for new engineers: Improve team page, resources, time to first MR merged by new engineers.
      4. Ops (Verify, Release & Package): Improve on-boarding for new engineers: Improve team pages, resources, time to first MR merged by new engineers: Goal for first MR to be complete in the first 2 weeks.
        1. Verify BE: Improve on-boarding for new engineers: Improve team page, resources, time to first MR merged by new engineers.
        2. Release: Improve on-boarding for new engineers: Improve team page, resources, time to first MR merged by new engineers.
      5. Ops (Configure & Monitor): Improve on-boarding for new engineers: Improve team pages, resources, time to first MR merged by new engineers: Goal for first MR to be complete in the first 2 weeks.
      6. Ops (Configure & Monitor): Define first iteration for BE role framework (Software Engineer, Senior Software Engineer, Staff Software Engineer)
        1. Configure BE: Improve on-boarding for new engineers: Improve team page, resources, time to first MR merged by new engineers.
        2. Monitor BE: Improve on-boarding for new engineers: Improve team page, resources, time to first MR merged by new engineers.
      7. Enablement: Improve documentation and training for supporting our customers: identify and address 3 major pain points for customer support and/or professional services.
        1. Distribution: GA for GitLab Operator: GitLab Operator enabled by default in the charts
        2. Distribution: Create automated charts installation and upgrade pipelines for supported Kubernetes flavors (e.g. GKE, EKS, etc.)
        3. Distribution: Generate library licenses and collection for the official Helm charts (similar to the omnibus-gitlab functionality)
        4. Gitaly: Make rapid progress on top company priorities: ship GA of object deduplication, ship beta of Gitaly HA => 50%
          • Pending QA on GitLab.com git object deduplication will be GA in %12.0, removing the feature flag and fixing minor bugs is whats left.
          • Beta of Gitaly HA is postponed given the renewed focus on performance. Hopefully 12.1 is the new target.
  5. CCO: Improve the candidate experience at GitLab for hiring great talent.
    1. Recruiting Director: Recruiting processes and systems to expedite hiring communicated across GitLab
    2. Recruiting Director: Average candidate timeline between application and offer reduced to 30 days.
    3. All Hiring Managers and Interviewers: 80% of candidate feedback submitted within 24 hours of the interview.
  6. CCO: Improve GitLab’s training and development Program,
    1. People Ops Director: Hire a L&D Specialist by the end of Q1.
    2. People Ops Director: Increase the tuition/course reimbursement utilization by 10%
    3. People Ops Director: Define metrics for each training that inform us on the value of current and future trainings
    4. L&D Specialist: 80% of attendees rate the training as valuable and/or actionable
    5. L&D Specialist: Defined key business metrics that should be improved by the training.
    6. L&D Specialist: Follow-up survey 30-60 after training to gauge applicability and usefulness.
  7. CCO: Improve GitLab’s Employer brand to increase our hiring and sourcing success.
    1. Recruiting Director: Hire an employment branding specialist by the end of Q1.
    2. Recruiting Director: Identify 5-10 locations to focus our branding and sourcing (25% increase in pipeline from these locations).
    3. Recruiting Director: Collaborate with Marketing to ensure that recruiting activities are integrated into at least 95% for conferences by the end of Q1
    4. Employer Branding Specialist: Reply to 90% of Glassdoor reviews
  8. Alliances: 3 acquisitions completed with 15 new team members joining GitLab. Establish the foundations of the sourcing process.

Engineering (VPE)

Development

Dev

Plan BE
  • GOOD
    • The team wrote seven blog posts! (Three merged, four in review.)
    • GraphQL collaboration between Plan and Create, and frontend and backend, worked well
  • BAD
    • Swapped GraphQL for Elasticsearch with Create, both missed
    • Not all blog posts completed
  • TRY
    • Extending blog posts goal to more engagement in other forms, too
Create BE
  • GOOD
    • Overperformed on hiring target: hit Q1 + Q2 goal of 3 hires in Q1
    • Benefits of Create Deep Dives are already showing: One engineer was able to help resolve a repository mirroring related production issue because he had learned how to troubleshoot it in the Deep Dive
    • ElasticSearch is enabled on staging for the gitlab-org group
    • We found multiple ElasticSearch related bugs that have been or are in the process of being fixed
  • BAD
    • Little progress was made on improving ElasticSearch admin controls
    • Wasn’t able to add a database maintainer because the database maintainership process took some time to be established
    • Single Code Base issues took resources away that could otherwise have been spent on other engineering-led efforts like some of these KRs
    • Most significant gitlab-shell features (push, pull) have not yet to be ported to Golang
    • The gitlab-shell epic wasn’t as fully fleshed out at the beginning of the quarter as it could have been, which would have allowed us to spread the work out better
    • gitlab-shell Golang features haven’t been enabled and tested on any live environment yet
  • TRY
    • Fleshing out KR-related epics better ahead of time
Manage BE
  • GOOD
    • Hiring: 2 new joiners in Q1, 3 new candidates accepted offers to join in Q2
    • Fulfillment section is now functional, reducing product scope of Manage
    • We have a plan to split the Manage stage in to two groups: Control and Framework, which will help scale up both team size and product scope
  • BAD
    • We haven’t delivered any more Deep Dive sessions, which brought value to the team in Q4 CY18
    • “Proactively reduce future security flaws” OKR was to generic and we didn’t have foresight that completion would be valuable or achievable. Identifying pervasive flaws was useful, but the only MR we felt would add value had already been picked up by another group
    • We no longer have a Maintainer in Manage, as James moved to Fulfillment
  • TRY
    • Encourage continuation of previous OKR initiatives that have added value (e.g. Deep Dives)
Gitaly
Last modified February 14, 2024: Remove Sisense references and links from Company, CEO, and About pages in Public Handbook (3a53a99d)
View page source - Edit this page - please contribute. Creative Commons License