Activation is one sentence, not a metric tree
Practice
Ask five people on a product team to define "activated user" and you'll usually get five different answers, each defensible, none of them written down anywhere.
This isn't a data problem. It's a definition problem, and most teams try to solve it with more instrumentation instead of a better conversation.
The metric tree trap
Popular analytics tools encourage you to build activation as a funnel of sub-events: signed up, verified email, completed onboarding step one, invited a teammate, created first project. Each step feels necessary to track. The result is a metric tree with a dozen branches, and a debate every quarter about which branch actually predicts retention.
The tree grows because adding a node is cheap and removing one feels risky. Nobody wants to be the person who deleted the metric that turned out to matter.
Write the sentence first
Before you track anything, write down activation as one sentence a new hire could understand without context. Something like: "A user is activated when they've created a project and invited one teammate within seven days." No branches, no conditional logic, no "or" clauses stacked five deep.
If you can't compress it to one sentence, that's information. It usually means the team hasn't actually agreed on what activation means, and the metric tree is a way of avoiding that disagreement rather than resolving it.
How Nocturna handles this
We ask for that one sentence during setup, translate it into a single computed metric, and apply it everywhere: the dashboard, the weekly digest, the alerts. There's no separate "activation dashboard" to maintain alongside the definition, because the definition is the dashboard.
When the sentence changes (and it will, as the product changes) you update it once. Every view downstream updates with it. That's the actual argument for keeping activation simple: not that complexity is impossible, but that every added branch is something you now have to keep synchronized by hand.
