In the Retention Signal Studio we keep a cheap exercise. We take last week’s DAU chart from a volunteer and ask a single follow-up: what verb, if it disappeared, would still leave this line intact? The answers are rarely the product’s reason for existing. Password resets, receipt PDFs, push-driven returns to a badge, and the polite open that happens when iOS restores a session all count as ‘active’ in many implementations.
None of those behaviours are sins. They become costumes when they are allowed to wear the word ‘habit’. A pensions app we sat with had a DAU spike on every regulatory letter. The letters were necessary. The spike was a download. When we plotted completed advice tasks against the same dates, the story inverted: more doors opened, fewer rooms used.
A second series, not a sermon
We do not ban DAU. We demote it. The title chart in a board pack should be a return to the core verb, with DAU in an appendix for operators who still need to staff a queue. If your core verb is ambiguous, that is a taxonomy problem, not a visualisation one. Name the event before you argue about the line. The companion essay on event names exists because this one kept stalling in class.
Weather belongs in the margin. A celebrity mention, a store outage, a bank holiday in Scotland but not in England — these are not personality changes in the user base. Annotate them. If your vendor makes annotation ugly, keep a dated note in the same folder as the export. The point is not beauty. The point is that next quarter’s reader can see why Tuesday looked brave.
What this does not solve
Unpicking a costume will not tell you what to build next. It will only stop you celebrating a waiting room. Growth work starts after the chart is honest. That is a different sitting.