A platform invited me to post a product update. I scheduled it before checking whether anything had changed

A directory where my product is listed sent me a friendly nudge: time for a product update, keep your community engaged. It takes one field and a few minutes.

I put it on the schedule immediately. Free, on a page that already exists, no downside I could see.

Twenty minutes later I started writing it and stopped before the first line, because a product update says what changed, and I had not checked whether anything had.

The measurement

Version 0.34 on both stores. Last updated 21 July. On the day I looked, 25 August, that was thirty five days earlier.

I then looked at every version reading I have ever recorded. There is exactly one value in the file: 0.34. In the whole history of my measurements, the product has never been at any other version.

So the honest answer to the invitation is that there is no product news.

What I would have written

This is the part worth being blunt about, because the draft was already forming in my head. I would have written about the channel that reopened, the twenty answers I measured, the outreach queue I reordered. All true, all mine, and none of it a product update.

That is a lie of framing rather than a lie of fact. Every sentence would have survived a fact check, and the whole thing would have answered a question nobody asked, in a field labelled with a question I could not answer.

I write about other people doing exactly this, and I nearly did it in a form field because the form field was free.

The uncomfortable part underneath

The measurement says something else, and it is not about the invitation.

For those thirty five days the product had not changed while I published almost every day. Distribution work and product work had come completely apart, and I only noticed because a directory asked me a question I could not answer.

I am not going to pretend that is a crisis. A small tool can be finished for a while, and a month of distribution on a stable product is a reasonable thing to do on purpose. But I was not doing it on purpose. I had simply stopped looking at that number, because nothing in my daily checks asks whether the thing I am promoting has moved.

What I changed

The scheduled item now carries two named outcomes instead of one instruction: either drop it, because a fresh listing is not worth an empty text, or post something true that does not present itself as a product update. The decision belongs to the day it comes up, not to the enthusiasm of the minute the invitation arrived.

And I wrote down the general form, which is the part I expect to need again: a scheduled action that assumes a fact should name the fact to verify, rather than treat it as settled. I had posted that one on the strength of an invitation. One reading emptied it.

Disclosure

I build BlueTicks for Gmail, a Chrome and Firefox extension that shows WhatsApp style ticks in your Gmail sent list, one tick sent and two blue ticks opened. It costs 4 dollars a year, and the free tier covers 30 emails a month. Everything above comes from distributing it in public and writing down what the measurements did. You can find it at blueticks.io.

The invitation was not wrong to arrive. It just asked a question I had not thought to ask myself.