Docs are a product: how to measure them

Teams measure sign-ups, activation and churn. Documentation, which sits in the middle of all three, often has no metrics at all. That makes it hard to fund and easy to neglect.

Treat readers as users#

A docs reader has a goal, a context and a moment of frustration. That is a user. Once you accept that, product habits apply: define the outcome, measure it, iterate.

Five metrics that matter#

1. Task success. Did the reader finish what they came to do? Measure it with a one-question "Did this help?" prompt.
2. Search with no results. Every empty search is a page you should have written.
3. Support deflection. Tickets per active user, before and after a page ships.
4. Time to first success. For API docs: minutes from signup to first successful call.
5. Freshness. The share of pages reviewed in the last 90 days.

Close the loop#

Metrics only help if they change the backlog. Once a month, review the top empty searches and the lowest-rated pages, and turn each into a ticket. Treat docs tickets like product tickets, with owners and due dates.

What good looks like#

A healthy docs practice has a named owner for every page, a visible feedback signal on every page, and a monthly review that leads to real work. The exact tooling matters much less than that loop.