Month 1, twelve posts in — what I've learned

Twelve posts in four weeks. Three posts a week on LinkedIn. Twelve companion blog articles on this site. A newsletter that went from zero to whatever it now reads as by the time this post publishes.

Some of what happened was predictable. Some of it wasn't. Before I start Month 2, here is the short reflection.

What I expected

I expected the standards-focused posts to do worst. Regulatory content doesn't travel on LinkedIn. It's dry, it's long, and it's hard to fit onto a carousel without losing the argument.

I expected the incident-catalogue post — the one naming Tesla Giga Texas, Goseong, Ecovacs, and the OSHA numbers — to do best. Named incidents attract engagement the way abstract analysis doesn't. That part of human attention is stable and predictable.

What surprised me

Three things.

The "slow reading" post — a short field note about reading standards on Tuesday mornings — got a lot more response than anything else structurally similar. I don't think it was the message. I think it was the length. In a feed optimised for scroll velocity, a short post that makes one argument and stops appears to land harder than a long post that makes the same argument more carefully.

The investment-paradox post produced the most substantive DMs. People who fund this kind of work, in Israel and out of Israel, read that specific post and wanted to talk. The comments it got were polite; the DMs were the real conversation. I was not expecting the DM channel to matter this much this early.

The SIL-levels deep-dive post was read by people who already knew what SIL was. This is the opposite of what I expected. Deep-dive content turns out to work as a trust signal to specialists, not as an educational piece for newcomers. The newcomers were reading the shorter primers. The specialists were reading the deep dives to check whether this publication was worth their time.

What didn't surprise me

The audience is small, and it's the right one.

This is a specialist publication about a specialist problem. It is never going to have the numbers of a general-audience tech newsletter. What it needs to have — and what it appears to be accumulating — is the right few hundred readers. The ones building machinery in Europe who need to read 2023/1230. The ones allocating capital in the safety-infrastructure sub-sector. The ones running safety offices at operators who are already asking the questions I'm writing down.

If you're one of those readers, thank you. Month 2 starts this week. The thesis doesn't change. The publishing cadence doesn't change. The quality bar goes up.