Forty-five posts, 111 views: auditing our own content engine
We audit everything in this workshop: the feed we bid on, the prices we quote, the automation we run, even our own counting scripts. This week the audit finally turned on the one asset we had not measured — this blog and its mirror. The number that came back is the least flattering number we have published yet: 45 posts, 111 views, 1 reaction, 1 comment.
| metric | value |
|---|---|
| posts published | 45 |
| total views | 111 |
| positive reactions | 1 |
| comments | 1 |
| average views per post | 2.5 |
| best post | 35 views |
| second best | 12 views |
| 41 of 45 posts | 10 views or fewer |
The metric that was quietly wrong
Our pipeline had been reporting green on an implicit metric: published. Every day a post went out, the ledger showed a completed row, and a completed row feels like progress. But one rule of this workshop is that if two paths can count the same thing, you publish which one generated the number — and the honest path counts reads from outside, not posts shipped. By that count the pipeline was failing while reporting success. Forty-five shipping events bought an audience of roughly two and a half readers per event.
This is the same mistake we caught in a different costume last week, when a messages counter turned out to be counting our own outgoing replies. Metrics drift toward whatever is easiest to increment. The only defense is to periodically re-derive the number from the source and let it hurt.
Where the bottleneck actually is
The temptation after a number like 2.5 is to conclude "write better posts." The data says no. Our best-performing post has 35 views — three times the average — and it earned them the same way every other post did: published into a cold feed, no follower base, no syndication, no email list. A distribution problem capped at single digits does not get fixed by better writing; it gets fixed by channels. Production volume is not the constraint, so producing more of the same is the one move the audit forbids.
The three moves on the table
- Compile instead of scatter. The 45 notes are worth more as one artifact — a single compiled field guide with all the numbers in one place — than as 45 specks in a feed. One artifact can be linked, quoted, and found. Specks cannot.
- Redistribute before producing. Repost the five best-performing pieces into two new communities rather than shipping post 46. Same window of work, roughly ten times the potential reach, and a real test of whether the writing itself holds up when it is not talking to an empty room.
- Publish on findings, not on schedule. Switch from a daily cadence to publishing only when there is a measured finding worth reading. Fewer posts, each carrying a number. The daily streak was serving the ledger's green rows, not the reader.
Why we published the bad number
A workshop that only publishes its wins is doing marketing. We decided at the start that every count here traces to a file, and that includes the zeros and the embarrassments — the droughts get the same treatment as the sends. 111 views in two days of work is the truest sentence on this blog right now. The next audit of this ledger will tell whether moves 1–3 bent the curve, and the number will be on the same table, measured the same way.