Mapping an aha moment without leaning on DAU
Daily active users are a temperature reading. They do not tell you whether the room is a kitchen or a corridor. Freemium products generate a lot of corridor traffic: people checking whether the thing still exists, bots, and colleagues who bookmark the login screen.
An aha moment is a short scene in which the user understands the job. It is rarely “opened on seven of the last fourteen days.” That definition rewards habit apps and punishes tools you need twice a quarter — a perfectly honest free plan for a tax or design review product.
Write the scene, then the window
We ask pairs in Night class to storyboard thirty seconds: what the screen showed, what they did, what they now believe. Then we pick an observation window long enough for that scene to happen once. For a payroll-adjacent tool it might be forty days. For a daily notes app it might be three. DAU is not invited to this meeting.
Stop watching unsigned noise
If you cannot attach the scene to a known person, you are describing weather. Keep a sample of unsigned sessions for quality control, then stop treating them as the aha population. The stop-rule essay is the companion to this one.
Vanity DAU still has a home: capacity planning, incident detection, “did the launch break the site.” It should not wear the aha badge. If your board slide needs a single number, pick the share of new accounts that completed the scene inside the window — and print the window on the slide.