The First Spark of Value: Which Exact Behavior Must a User Perform for Real Value to Have Begun?

“Our activation rate is sixty percent,” the product manager said. I asked: “What do you mean by activation?”

“Users who sign up and complete their profile.”

Completing a profile. In a CRM, a project management tool, an analytics platform. Nothing in the user's life changes because they completed their profile. That's not activation. That's a form completion rate.

I've had this conversation in so many versions that I nearly know it by heart. Teams usually tie activation to the first step that's easy to measure: verifying an email, logging in for the first time, changing a setting. Then they optimize that step. The rate goes up. Retention doesn't move.

Three moments, three questions

There are three moments in a user's first days with a product that get confused with each other, and separating them changes everything.

The first is the setup moment. The user becomes able to use the product: account created, data connected, team invited. Necessary, but it creates no value on its own. Its only purpose is to reach the next one.

The second is the aha moment. The user sees, with their own eyes, what the product can do for them. Their first report gets generated, their first automation runs, their first customer pays. A spark flies here, but a spark isn't a fire yet.

The third is the habit moment. The user starts getting that value again and again, and the product settles into the natural flow of their work or life. This is where real value accumulates.

Most teams measure the first, talk about the second, and hope for the third. But the real definition of activation is the behavior that connects the second to the third: the behavior where most users who do it stay, and most who don't, leave.

Looking for the spark in the data

There are two often-told examples, and both tell the same idea. In Facebook's early years, the team observed that users who reached seven friends within ten days of signing up largely stayed. At Slack, it's said that teams who had exchanged around two thousand messages became far less likely to abandon the product.

The numbers themselves mean nothing for your product. What matters is the method: look at the behavioral difference between users who stay and those who leave, and find the threshold that creates the difference.

In practice you start like this. Take the users who signed up in a given period. A few months later, separate the ones who are still active from the ones who aren't. Then put everything they did in their first two weeks side by side. You'll see one or two behaviors that nearly all the stayers did and most of the leavers didn't. Sometimes it's the action itself, sometimes a frequency: “three times in the first week.”

When you find it, you have a candidate definition of activation. I say candidate because there's a trap.

Correlation can fool you

The fact that retained users did a certain thing doesn't mean that thing is what kept them. Maybe the already highly motivated users were the ones doing it. Maybe the behavior is a result of value rather than its cause.

The only honest way to tell is to test. Make a change that gets one group of new users to that behavior faster and more easily, and leave the other group as is. If retention rises along with the behavior, you've found a real lever. If the behavior rises but retention doesn't budge, you've caught the wrong thing. Pushing users into a behavior doesn't give them the value behind it.

I've watched teams get impatient at this point many times. A correlation is found, everyone gets excited, onboarding is rebuilt end to end around that behavior, and the result is a disappointment. One more week of testing is cheaper than three months of running in the wrong direction.

Onboarding is the shortest path

Once you find the right behavior, the purpose of onboarding becomes clear: take the new user to that behavior by the shortest route. Nothing else.

For most existing onboarding flows, that means serious simplification. Product tours get shorter. Mandatory setup steps get questioned: do we really need this information now, or after we've shown the first value? Empty screens get filled with ready-made examples, because waiting for the user to bring their own data is sometimes the longest road of all.

My favorite question is this: in the first minute after opening the product, how many clicks away is the user from the activation behavior? Count them. Then try to reduce that number every quarter. That number is the most concrete form of the time to value I talked about in the second piece of this series.

The spark doesn't fire once

One last note. The activation behavior isn't fixed. As your product changes, as you open up to new segments, as the reasons users come to you change, that behavior changes too. A threshold that's right for small businesses may be meaningless for an enterprise customer.

That's why I don't treat the activation definition like a KPI you set once and forget, but like a hypothesis to be questioned regularly. Repeating the same analysis every six months is the cheapest way to see how both the product and its users are changing.

The phase we call understanding value closes here: we've talked about what value is, how it's perceived, and where it first sparks. The next phase is about turning that spark into a fire. And we'll start with the metric teams most often measure wrong: retention.