The ones who read every changelog but never click

There's a pattern that shows up in engagement data and almost never gets read correctly: the user who opens every changelog email, reads every release note, sometimes even visits the "What's New" page unprompted — and never adopts a single new feature.

Product teams tend to file these people under "aware but uninterested." Sometimes they get tagged as passive. Sometimes they end up in a re-engagement campaign, which is a particular kind of irony, because they're already deeply engaged. They're just not engaged in the way the dashboard rewards.

We started noticing this pattern in journeys where the user had been on the platform for more than a year. Long tenure. Stable usage. Feature footprint that hadn't changed in months. But changelog engagement that looked like a product manager's — consistent, thorough, sometimes within hours of publication. In one case, someone had opened 23 consecutive release-note emails and hadn't logged into a single new workflow. Standard product analytics would call that a churn risk, or at best a curiosity. We think it's neither.

What these people are doing is monitoring trajectory.

They made a bet on the product at some point. Maybe they convinced a team to adopt it. Maybe they built a workflow on top of it. Maybe they just spent credibility vouching for it in a meeting where someone else wanted a different tool. Now they're watching to see if the bet still holds. Every changelog entry is a data point in an argument they're still having — with a colleague, a board, or themselves — about whether the platform is headed somewhere that continues to justify the cost of switching to it, or staying on it, or building deeper into it.

This is not resistance to change. It's the opposite. It's someone who cares so much about the direction of change that they're reading the tea leaves every time you publish. They're not asking "is this feature useful to me today." They're asking "does this company still understand the problem the way I understand it."

The reframe matters because most teams interpret changelog engagement through an adoption lens. Open rate becomes a leading indicator for feature uptake. When uptake doesn't follow, the signal gets discounted. But the real information is in the persistence of attention without action. That combination — sustained interest, zero behavior change — almost always points to someone evaluating at a layer above the feature. They're evaluating you as infrastructure. Infrastructure you don't switch away from lightly, and you don't switch to lightly either. You watch it.

The thing product analytics misses here is structural. Most tools track what people use. Clicks, activations, time in a workflow. They are very poor at tracking what people study. A user who reads a changelog entry about an API overhaul and then does nothing has, in the traditional model, generated a near-zero signal. But in the context of their journey — a year of stable usage, a history of advocating for the product internally, a pattern of reading every update — that "nothing" is the most meaningful thing they've done in months. They looked at the direction and decided to stay.

One counter-example worth noting: sometimes heavy changelog readers really are evaluating features for adoption, just slowly. Enterprise buyers in regulated environments will often read 3 or 4 release cycles before even trialing something new. The tell is whether their reading pattern is selective or comprehensive. Selective readers — people who open changelogs about specific capabilities — are probably shopping. Comprehensive readers — people who open everything, regardless of relevance to their current usage — are watching the arc. The distinction is small in the data and large in what it means.

The quiet version of loyalty doesn't look like engagement in any report most teams run. It looks like a person reading a document and closing the tab. But that person may be the one holding the budget line open, or keeping the migration conversation off the table for another quarter, based on what they just read. Their attention is a bet renewal, made silently, every time you ship.