Splitting the first three days into separate failure modes makes this easier to act on than one big churn number. The empty-state cliff on day 2 is the one teams skip most, since it only shows up for users who came back once and found nothing waiting. Putting instrument first at the top of the playbook is right too, otherwise the activation rate step has nothing to measure against.
StackShortlist
Proof Over Promises.
Splitting the first three days into separate failure modes makes this easier to act on than one big churn number. The empty-state cliff on day 2 is the one teams skip most, since it only shows up for users who came back once and found nothing waiting. Putting instrument first at the top of the playbook is right too, otherwise the activation rate step has nothing to measure against.