Journal · 2026-03-12
Reading feature reach without vanity numbers
A quiet way to tell whether a feature is part of someone’s week—or only part of a launch announcement.
When a release ships, it is tempting to celebrate any uptick in event volume. Volume alone rarely answers the question product teams actually ask: did this feature become part of how people finish their work?
Start with a reach window that matches your product’s natural rhythm. For a tool used daily, seven days of returning use after first exposure often says more than a single spike on launch day. For seasonal products, compare the same calendar window year over year rather than consecutive weeks.
Separate first-touch exploration from repeated completion. Exploration is healthy; it is also temporary. Mark the events that represent finished work—exports filed, reports shared, tickets closed—and measure how many accounts repeat those events without prompting.
Write the finding in plain language before you chart it. If you cannot say “about one in five active accounts used the new filter twice last week,” the chart is not ready for planning conversations.
Finally, name the audience that did not show up. Silent seats and seats that only open the product for billing are different problems. Feature usage reporting only helps when those groups stay distinct in the brief.