Field notes · 2026-04-02
Choosing cohort windows for B2B feature adoption
Weekly jobs need different observation windows than daily ones — a common source of false alarms.
A seven-day adoption window fits consumer habits poorly onto a B2B feature used once per invoice cycle or monthly reporting close. Teams then declare failure too early.
Map the job’s natural rhythm first. If finance teams reconcile on Fridays, your cohort window should span at least two of those moments. If account managers update plans quarterly, a thirty-day slice will understate return use.
Segment by role when the feature serves more than one job. An admin may adopt configuration quickly while end users never see the surface. Averaging them hides both stories.
Document the window in the release brief so leadership reviews use the same frame. Changing the window mid-conversation destroys trust in the numbers.
When in doubt, report two windows: early reach and a longer return window. Clarity beats a single vanity rate.