Beyond metrics: Using maturity models to develop a docs strategy
summary
Claims that a simple maturity model gives actionable direction when traditional metrics fail with volunteer-driven projects; builds a text-based maturity model (not visual) because MediaWiki and privacy limits block rich analytics; measures two things — org-level maturity and architecture/process maturity — and meets biweekly with quarterly reviews; started at ad hoc and now sits in rudimentary with two technical writers coordinating volunteers; outcome: clearer goals, tangible progress to show, and plans to iterate the model.
AI-written summary · about
chapters (24)
- 0:00Start
- 1:23Overview
- 4:26Traditional Metrics
- 4:54Categories of Metrics
- 5:24Readability Scores
- 5:45Timeliness and Accuracy
- 7:13Satisfaction Surveys
- 10:17Maturity Models
- 10:56History
- 11:22The Capability Maturity Model
- 12:25The Maturity Model
- 13:15Levels of Maturity in a Maturity Model
- 13:49Rudimentary Technical Documentation
- 14:17Baseline
- 14:56Managed and Sustainable
- 16:38What Form Do Maturity Models Take
- 18:00Content Maturity Model for Content Strategy
- 18:16Key Process Areas
- 18:43Software Testing
- 23:07How Do We Use Maturity Models at the Wikimedia Foundation
- 25:55Architecture Maturity Model
- 26:57Tips
- 29:00Decide on a Cadence for Revisiting
- 34:54What Plugins if any Do You Use To Help with Gathering Documentation Metrics
related talks
26mA maturity model for Developer Portals
26mMetrics and Modeling – Helping Teams See How to Improve
34mProving and improving the value of your docs
33mmetrics panel
20mHow to Communicate Metrics to Build Engagement
35mMetric driven documentation
51mQuality Maturity Model: Driving Excellence In High-Growth Orgs
40mDocs Tools for OSS Maintainers