---
locale: en
translated: true
title: "Turning reading metrics into product improvements"
url: https://insightlog.site/en/posts/reading-metrics-to-product
site: "InsightLog"
published: 2026-11-08T09:50:16.935Z
updated: 2026-11-20T09:50:16.936Z
author: "Maya Chen"
author_url: https://insightlog.site/en/authors/maya-chen
type: "Essay"
category: "Product"
tags: ["Metrics", "Product", "Experiments"]
reading_minutes: 1
views: 556
upvotes: 28
downvotes: 1
---
## Three questions

Metrics answer different questions, and mixing them produces bad decisions.

- **Views**: did we reach anyone?
- **Votes**: were they satisfied?
- **Returning readers**: do they trust us enough to come back?

Views without votes means reach without value. Votes without returning readers means a single good article, not a durable publication.

## The improvement loop

1. Compare the top and bottom articles every week.
2. Find what the bottom articles commonly miss: a clear conclusion, a concrete example, a date on the numbers.
3. Change one element at a time next week.
4. Record the change and the result before starting the next experiment.

The fourth step is the one teams skip. Without a written record, every result becomes a story about why the last change worked.

## What to ignore

- Raw pageviews as a quality signal
- Time on page for short articles
- Averages across very different topics
- Any metric that can be improved by making the article shorter or vaguer

## A simple dashboard

Keep it to one screen:

| Metric | Window | Question |
| --- | --- | --- |
| Views per article | 7 days | Reach |
| Vote rate | 7 days | Satisfaction |
| Return rate | 28 days | Trust |
| Scroll depth | 7 days | Did they finish? |

If a metric does not change a decision, remove it.

## Conclusion

Metrics are not a scorecard. They are **a tool for choosing the next experiment**. The publication that improves fastest is the one that writes down what it tried.
