Field notes · 2026-01-08
Activation is not adoption — and why the difference matters
Teams often celebrate first-use milestones while repeat use for the same feature stays flat.
Activation answers whether someone completed a meaningful first action. Adoption answers whether that action becomes part of how they work week after week.
Confusing the two leads to odd roadmaps: more prompts to force first clicks, while the feature still fails to earn a second visit. Feature adoption tracking should keep both signals visible and named separately.
When we review releases with United Kingdom product teams, we ask them to define the repeat behaviour they care about before looking at any dashboard. Without that definition, every spike looks like progress.
A useful habit is to pair each feature with an activation event and an adoption window — for example, three uses in fourteen days, or one use in each of two consecutive weeks. The window should match how often the job occurs.
Once those definitions are written down, release reviews become calmer. You can say clearly: activation met the bar; adoption did not — and decide whether the next work belongs to education, reliability, or the feature itself.