Proving and improving the value of your docs
summary
State of Docs surveys find one in four teams track no metrics and ~80% of decision makers read docs, so the talk lays out concrete measurement choices: use page views to prove scale but compare them over time to spot inflections; track referral sources, support ticket deflection and doc surface area; monitor broken URLs and search no-results as missing information signals; and use AI assistant analytics to see real user questions (examples: MCP access gaps, many Docker searches). Practical steps: inventory metrics, inspect one familiar page, and start conversations with support, sales and users.
AI-written summary · about
chapters (8)
- 0:00Introduction
- 1:49Measuring docs impact
- 4:15Metrics expectations
- 7:05Proving and improving docs
- 13:03Improving with data
- 25:50Start measuring docs
- 26:11Q&A: AI readers
- 32:09Q&A: Customer surveys
related talks
40mThe Importance of Using Analytics and Feedback for your Documentation
23mWriting Docs Worth Reading
23mTwo Great Teams: Bridging the Gap Between Documentation and Customer Support
20mDo Docs Better: Practical Tips on Delivering...
27mThe hidden power of information assets The role of documentation in product success
45mOptimizing SEO for Technical Documentation
24mDocs Advocacy is Dev Advocacy
39mQuantifying the Impact of Documentation: Findings from DORA Research
