Blog · 19 January 2026
Naming Drift Without Panic
A short practice for describing cohort change so stakeholders can decide, not react.
“New users are worse” is not a trend statement. It hides whether activation slowed, whether a feature was removed from the first path, or whether acquisition quality changed.
Pair every drift note with a comparison cohort, a time window, and one candidate cause you can test. Without those three lines, drift becomes a rumor.
When cause is unknown, schedule a short observation pass—session notes, support themes, or a handful of user conversations—before proposing a redesign.