InfraDev Connect
Journal
Practical notes on reading adoption and writing feature usage reports that product teams finish.
-
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.
-
Adoption questions worth asking at kickoff
Five concrete questions that keep an adoption assessment from drifting into general product advice.
-
Handing usage briefs across Korea-based product teams
Practical notes on timing, language, and ownership when reports move between Seoul offices and distributed engineers.
-
When event names block adoption work
How messy tracking catalogs quietly sabotage feature usage reports—and what to clean first.
