Reporting and Metrics

This section will provide reporting and metrics for knowledge management and KCS.

Why do we measure knowledge (and KCS)?

Reporting and Measurement is important because it helps us understand how our efforts are driving value for Gitlab Customers and internal Support . By having knowledge we know it helps improve support efficiency. We have faster resolution times, reduced tickets, and increase customer self service. We drive consistency with answers and it helps us identify gaps and risks.

With a Knowledge Dashboard, We will show trends over time. Are we creating knowledge, is that knowledge being consumed?
How often are we updating that knowledge, and are customers finding it?

What will we measure?

  • Article Views
  • Article Drafts, Published Modifications
  • Author Participation (for Recognition)
  • Linking knowledge to support tickets
  • Searches (for knowledge)
  • Feedback (Customer Feedback)
  • Article Ratings
  • Page views (where articles are being viewed, google analytics)
  • Ticket Deflection
  • First contact resolution (did customers find what they need without having to open support)
  • Knowledge reviews, and growth (articles created over time, how many are updated, what is the review cycle)

What is our focus

  • Improved Efficiency in the workflow. Are customers finding answers?
  • Cost Savings - are we seeing less tickets, are customers self solving and are we seeing a decrease in support costs?
  • Customer satisfaction - are our ratings increasing ?
  • Consistency- Support links to knowledge articles are we seeing repititive answers, articles being used and updated?
  • Increased knowledgg creation - this shows scalability
  • Integration - how we integrate with AI. Being part of DUO or Claude

Where can I find knowledge metrics?

We are currently working with our metrics team members to build a Dashboard for KCS and Knowledge Management. This is a work in progress.

  • ZenDesk Guide provides an over view of create/publish/etc. This level of information will be shared at our Support Monthly Business Review as well as SLACK Channels.
  • SWIR - we will begin to add metrics to the SWIR on a monthly basis (First week of the month)
  • #spt_knowledge-base SLACK CHANNEL -the metrics will be added along with RECOGNITION of our knowledge contributors!
Last modified June 9, 2025: Fixed W error (5c90bf65)