011 min
What breaks without an aha moment
A product team ships a sign-up flow, a profile screen, a tour of six features and a welcome email. Most new users finish some of it. Many never return. The team sees an activation rate, but the rate counts steps completed, such as "created a profile". A step like that says nothing about whether the person learned why the product is useful.
This is the failure the aha moment names. The team measures what is easy to count and treats it as value. The first week of the product is then built around the wrong event. The onboarding tour teaches where the buttons are. It does not get the user to the one experience that makes them want to come back.
The cost is a decision made wrong. A team that does not know its aha moment spends a quarter improving sign-up completion. Sign-up completion rises. Retention stays flat, because the users who complete sign-up still have not reached the experience that keeps people.
The three real cases in this article all started from the same observation. Some new users stayed and some did not. Someone then looked for the earliest behaviour that the two groups did not share.
022 min
How an aha moment works
An aha moment has two parts that people often merge. The first is a feeling: the user sees that the product does something useful for them. The second is a behaviour the team can count, which happens at about the same time as the feeling. The feeling cannot be measured directly. The behaviour can, so teams use it as a stand-in.
The counted behaviour is called a threshold, or an activation metric. It has a quantity and often a time limit. "7 friends in 10 days" has both. "2,000 messages sent by a team" has a quantity only.
The mechanism has four steps:
- A team compares users who stayed with users who left, in the first days after sign-up.
- It looks for an early action that most stayers took and most leavers did not.
- It picks the point where more of that action stops making a difference. That point is the threshold.
- It redesigns onboarding so more new users reach the threshold, and it checks whether retention rises.
Step 4 matters most. Step 2 only finds a correlation, which is a pattern in the data. It does not show that the action causes people to stay. The later sections cover how to test that.
| Part | What it is | Example |
|---|---|---|
| Feeling | The user's realisation that the product is useful to them | A new user sees a feed full of people they know |
| Behaviour | The countable early action that goes with the feeling | Adding friends |
| Threshold | The quantity, and time limit, past which staying becomes likely | 7 friends in 10 days |
| Check | The test that reaching the threshold causes retention | Changing onboarding, then comparing retention |
The aha moment is the earliest experience of the product's value. The activation metric is the number the team counts to see whether a user has had it.
Because the user decides what is valuable, the threshold differs by product. A messaging product for teams needs a team to have used it together. A social network needs a user to see content from people they know. A file-sharing product needs a file to be shared with someone else. In each case, the threshold is the point where the product starts doing the job it was built for. A job to be done is a useful way to name that job before the data search starts.
031 min
Where the aha moment idea came from
The phrase "aha moment" is older than product management. In everyday speech it names a sudden understanding. Growth teams in the 2000s and 2010s borrowed it for the first moment a user understands a product, and gave it a number.
This entry does not trace the phrase to one inventor. What can be checked is how named teams used it. In a talk about how Facebook reached one billion users, Chamath Palihapitiya described the finding of the growth team:
The biggest thing we realized: get any individual to 7 friends in 10 days.
Sean Ellis and Morgan Brown described the same method in their 2017 book Hacking Growth. An excerpt published by Mattermark tells how Josh Elman, then a product manager at Twitter, found a similar number. Index Ventures wrote in 2016 that many companies have documented their own tipping points to user stickiness. In that article, Facebook, Dropbox and Slack are all listed.
What these accounts share is the method, not the number. Each team started with retained users, looked backward at what they did early, and set a target for new users. The next two sections show two of those cases in detail.
042 min
Slack and Dropbox: one threshold per product
Index Ventures, in a 2016 article, named Slack's tipping point as a team that reaches 2,000 messages sent. The unit is a team and not an individual user. That fits what Slack is. A messaging product has no value to one person alone, so the useful count is the amount of conversation a whole team has had in it.
The same article lists two other companies' thresholds. Facebook's is 7 friends in 10 days. Dropbox's is a user who puts at least one file in a share folder. The three thresholds have different units: friends, messages and files shared. They have one thing in common. Each describes the moment the product starts doing its job between people, and not the moment someone finishes setting it up.
For Dropbox, putting a file in a share folder is the first time the product does more than store a file. The file is now reachable by another person. The count for Dropbox is one, which shows that a threshold does not need to be large. It needs to mark the right event.
The Facebook threshold has a time limit, 10 days. A quantity with no time limit does not tell a team what to design for. A time limit turns the finding into an onboarding goal: get a new user to 7 friends before day 10. The Slack threshold has no time limit in the source, so any team using it would need to decide one.
These numbers come from each company's own data. They are not rules for other products. A team building a calendar tool should not target 7 friends. It should run the same comparison on its own users.
052 min
Twitter: finding the threshold, then finding out why
Twitter's case is useful because it goes one step further than a count. In the Mattermark excerpt from Hacking Growth, Josh Elman's analysis found that the users who came back at least seven times a month were generally following about 30 other accounts.
That is a correlation. The team did not stop there. The excerpt says they asked whether the wish to follow many accounts was the real reason people stayed. They looked for another pattern in the data and found one. Users who were followed back by about a third of the accounts they followed were the ones who became loyal.
That second pattern is odd. More follow-backs did not mean more loyalty. The team phoned users to find out why. According to the excerpt, if much more than a third of the people a user followed followed them back, then Twitter seemed pretty much like just another social network. If fewer than a third followed back, it seemed more like a news site. A one-third to two-thirds ratio was where Twitter's distinct value became clear.
| Follow-back share | What users told the team | Outcome |
|---|---|---|
| Much more than a third | Twitter seemed like another social network | Distinct value not clear |
| About a third | Twitter was a place to find out what is happening | Became loyal users |
| Fewer than a third | Twitter seemed like a news site | Distinct value not clear |
What this adds to the Facebook and Slack cases is the question "why". The count of 30 was a lead. The interviews explained the feeling behind the count. A team with only the count could have pushed users to follow more accounts without understanding what made following useful.
The variable that differs between this case and the first is the type of evidence. Slack and Facebook, as presented in their sources, give a threshold. Twitter's source gives a threshold and the reasoning that tested it.
062 min
How to find an aha moment this week
The output of this work is a short written threshold, such as "a new team that does X at least N times within D days", with the evidence behind it. A spreadsheet is enough. The steps below follow the pattern in the cases above.
Pick the retention you care about.
Choose one outcome, such as "active in week 4". Use the same one for every user you compare.
Split new users into stayers and leavers.
Take everyone who signed up in one period, such as three months ago. Mark each as a stayer or a leaver by the outcome above.
List early actions.
Write every action a user can take in the first 14 days, such as inviting a colleague, creating a project or connecting an account.
Compare the groups.
For each action, compute the share of stayers and the share of leavers who took it. Rank actions by the gap.
Find the count.
For the top action, compare retention for users who did it once, twice, five times and so on. Look for the count after which retention stops rising much. That is your candidate threshold.
Add a time limit.
Test 3, 7 and 14 days. Choose the shortest one that keeps the retention gap.
Ask users why.
Phone five stayers and five leavers. Ask what they were trying to do and when it worked for them. This is the step that Twitter's team added.
Test it.
Change onboarding to push the action, show it to a random half of new users, and compare retention. A controlled test shows whether the action causes retention or only goes with it.
The usual caution applies at step 4. Correlation is not causation. A user who invites ten colleagues in the first week may have been going to stay anyway, because they came with a strong need. Step 8 is the check against that.
| Step | Artifact you produce |
|---|---|
| 2 | A table of users with stayer or leaver marked |
| 4 | A ranked list of early actions by retention gap |
| 5 | A chart of retention against action count |
| 7 | Ten short interview notes |
| 8 | A test result that supports or rejects the threshold |
072 min
Where aha moment work goes wrong
Mistaking correlation for cause. This is the failure with the clearest tell. A team finds that stayers added many friends and pushes every new user to add friends. Retention does not move. The friends were a sign of users who were already motivated. They were not the reason those users stayed. The Twitter team saw this risk and tested the reason, as described above.
Setting a threshold that is easy to hit but empty. If a user can reach the threshold by tapping through a prompt, the number rises and the experience has not changed. The tell is an activation rate that improves while week-4 retention stays flat. The threshold should be an action the user chooses to take, because they get something from it.
Using one threshold for everyone. A product with two kinds of user, such as people who post and people who only read, can have a different aha moment for each. A single number averages two groups and describes neither.
Treating a company's number as a rule. The figures in this article belong to Facebook, Dropbox, Slack and Twitter. They show how to find a threshold. They do not show what yours is.
A limit of the idea itself. The method looks only at users who signed up and stayed or left. It does not tell the team about people who never signed up. It also assumes that value arrives early. A product whose value appears after weeks of use may show no useful early action. For that kind of product, the team needs a different measure, and the aha moment may be the wrong frame.
Sources differ on how precise these thresholds are. The article from Index Ventures presents them as tipping points that companies have "documented". The Mattermark excerpt describes 30 as a number that "seemed" to be a tipping point. Neither source claims a law. A practitioner should treat any threshold as the best current hypothesis, and re-run the comparison when the product changes.
082 min
Aha moment compared with nearby concepts
The aha moment is easy to mix up with the habit it leads to, with the first successful use, and with the whole onboarding flow. The table separates them by the question each one answers.
| Concept | Question it answers | When it happens |
|---|---|---|
| Aha moment | When does the user first see the value? | Early, often in the first days |
| Habits | Does the user come back without being prompted? | After repeated use, over weeks |
| Reactivation | How do we win back users who left? | After the user has gone quiet |
| Onboarding | What steps do we put in front of a new user? | The first session or days |
The deciding fact is time. The aha moment comes before the habit and is its entry point. A product can have an aha moment and fail to build a habit, if the value is real but the user has no reason to return. A product can also build a habit without a clear aha moment, if a prompt brings users back before they understand why. The order for a team is: find the aha moment first, then design onboarding to reach it, then work on what brings the user back.
Reactivation comes later again. It addresses users who passed through onboarding and then stopped. A team that cannot name its aha moment will find reactivation harder, because it will not know which experience to send a lapsed user back to.
?7 questions
Questions people ask
What is an aha moment in product management?
What is an example of an aha moment?
How do you find your aha moment?
Is an aha moment the same as activation?
Does every product have one aha moment?
Who should run this analysis?
What do you do if the threshold does not raise retention?
§3 sources
Sources
Show all 3 sourcesHide sources
Index Ventures, "Growing As Fast As Slack", 28 November 2016. Names the tipping points for Facebook, Dropbox and Slack.
Sean Ellis and Morgan Brown, Hacking Growth (2017), excerpt published by Mattermark: "Putting It All Together: How Josh Elman Identified a Growth Driver at Twitter".
Chamath Palihapitiya, talk "how we put Facebook on the path to 1 billion users", quoted in The Growth Mind, "The Ultimate Story of Growth, Part 1".





