Documentation Analytics
I use analytics to improve documentation work, not to decorate it with dashboards. The useful question is always practical: what does a team need to see in order to prioritize, maintain, or improve the system?
The analytics model
content and workflow signals │ ▼ clean, reviewable reporting inputs │ ▼ visible scope, progress, and friction │ ▼ better maintenance and process decisions
Where the work helps
| Need | Method | Evidence |
|---|---|---|
| Understand what exists and what is stale | Content audits, inventories, and freshness tracking | 234-page governance system for maintenance priority |
| Make work visible | Centralized tracking, Tableau, SharePoint, and reporting workflows | 400+ products tracked; seven automated dashboards |
| Prepare and analyze operational data | Excel, Power Query, and SQL-backed metrics | Repeatable reporting and documentation-health signals |
| Prioritize work with real consequences | Usage data and workflow measurement | Focus on high-use content and the friction that affects it |
This work supports documentation operations. See Analytics and Reporting for the case-study evidence and Tools and Systems for the related toolchain.