Dear reader,
Nine articles into this blog, I went back and looked at which ones actually got read, shared, and commented on. I expected the technical pieces to win, the SharePoint governance breakdown, the platform lock-in warning, the kind of content that demonstrates expertise directly.
That's not what happened.
The one that actually landed
The piece that got the most engagement by a clear margin was about member renewal, and it wasn't really about renewal at all. Buried in the middle of it was a story about chasing an industry accreditation back in the mid-2000s, and winning a photography award that still means something to me now. Nothing about iMIS. Nothing about systems. Just a genuine, personal account of what membership actually meant to me once, before I was the one advising associations on it.
Why that's uncomfortable to admit
It's a little deflating, honestly. I've spent most of these articles trying to demonstrate expertise: here's a problem, here's the pattern, here's how to fix it. That's useful content, and I still believe in it. But it turns out the piece people actually connected with wasn't the one proving I know what I'm talking about. It was the one where I stopped explaining and just told a true story about being a member myself.
What that actually means
I don't think it means the technical pieces were wrong to write, several of them exist specifically because a particular problem needed solving in public, and that's still genuinely useful. But it's a real signal about what makes someone stop scrolling and actually read to the end: not more proof of expertise, but a moment where the writer stops performing that expertise and just says something true and specific about themselves.
Where this changes things going forward
I'm not going to force a personal story into every piece from here, that would feel exactly as manufactured as it sounds. But I'm going to stop assuming the technical explainer is automatically the stronger choice, and start asking, honestly, whether there's a true, specific moment sitting underneath the topic that would do the job better than another framework or checklist.
Until next week,
Brock