Hooked

Nir Eyal's Hooked is a framework for designing products that become part of a user's routine.

The book's core claim is that repeated product use can be engineered through a four-part loop:

A successful hook connects an internal need to a product response often enough that the user eventually stops requiring deliberate persuasion. The behavior becomes automatic.

The product stops competing for attention each time it is used when the user's own internal state begins supplying the trigger.

Painkiller or vitamin

The first useful question is whether the product behaves like a vitamin or a painkiller.

A vitamin may improve life but is easy to postpone.
A painkiller addresses an immediate problem.

The distinction matters because habits form most easily around recurring discomfort. The user is not merely seeking pleasure. Repeated pleasure-seeking can become relief-seeking as the absence of the product itself begins to create tension.

The notes capture the progression this way:

• pleasure-seeking behavior can become pain-alleviating behavior

• pain-alleviating behavior can become pleasure-seeking behavior

• stress can increase susceptibility to habitual or compulsive behavior

This makes the relevant product question more precise:

What recurring state makes the user want relief, and can the product become the default response to that state?

Habits

A habit is behavior performed with little or no conscious thought.

The source notes reduce habit formation to two conditions:

• frequency

• positive perception

A product used rarely has fewer opportunities to become automatic. A product associated with friction, confusion, or disappointment has fewer reasons to be repeated.

The Hook Model is therefore not simply a retention tactic. It is a mechanism for connecting:

The stronger the association, the less external prompting is required.

Trigger

Triggers initiate behavior.

External triggers

External triggers contain the information necessary to tell the user what to do next.

Examples include:

• calls to action

• push notifications

• emails

• buttons

• alerts

• referrals

• environmental cues

The product question is:

Where and when can the external trigger appear so that the next action is obvious?

Internal triggers

Internal triggers are associations stored in memory.

They are more powerful because the product no longer needs to interrupt the user. The user's own emotional or situational state recalls the product.

Negative emotions can be especially strong triggers:

• loneliness

• boredom

• anxiety

• uncertainty

• frustration

• fear of missing out

A useful template is:

Every time , the user .

The first blank identifies the recurring internal state.
The second identifies the behavior the product wants to become automatic.

Action

The action is the simplest behavior performed in anticipation of a reward.

The source notes use the Fogg behavior model:

The relevant motivational forces include:

• seeking pleasure

• avoiding pain

• seeking hope

• avoiding fear

• seeking acceptance

• avoiding rejection

Ability is constrained by:

• time

• money

• physical effort

• mental effort

• social deviance

• non-routine behavior

The strongest design implication is to prioritize ability over motivation.

Increasing motivation is like pushing a boulder uphill.
Reducing friction is like pushing it downhill.

Instead of asking how to persuade users to try harder, ask:

• Can the action take fewer steps?

• Can it require less thought?

• Can it require less money?

• Can it happen inside an existing routine?

• Can uncertainty be removed?

• Can the first useful result arrive sooner?

The easiest way to increase behavior is often not to make the user want the outcome more, but to make the path to it dramatically easier.

Variable reward

The reward must satisfy the user's need enough to justify the action while preserving enough uncertainty to sustain attention.

The notes emphasize that anticipation can be more behaviorally activating than receipt. Variability creates uncertainty, and uncertainty creates attention.

The framework identifies three broad classes of reward.

Rewards of the tribe

These come from other people:

• belonging

• empathy

• status

• recognition

• competition

• approval

Social products are especially capable of producing variable rewards because other people are inherently unpredictable.

Rewards of the hunt

These come from searching for resources or information:

• money

• bargains

• information

• content

• opportunities

• scores

• discoveries

Feeds, markets, search products, and games often use this pattern.

Rewards of the self

These come from personal competence:

• mastery

• completion

• progress

• control

• achievement

The product question is:

Is the reward satisfying enough to matter, but variable enough that the next cycle remains interesting?

Investment

The final step is the user's investment in the product.

Investment is the work a user performs that increases the likelihood of future use.

Examples include:

• creating a profile

• adding followers

• building a feed

• saving songs

• creating playlists

• entering data

• training recommendations

• building reputation

• accumulating history

• learning the interface

The important property is stored value.

A generic product can be replaced easily.
A product that becomes increasingly shaped by the user becomes more costly to abandon.

An Instagram feed becomes more valuable as relationships accumulate. A Spotify account becomes more valuable as playlists and taste history accumulate.

Investment therefore serves two purposes:

1. it increases the value of the next cycle

2. it loads the next trigger

This is where retention begins to compound.

The Hook Model

The original notes reduce the book to four questions:

1. Trigger — What internal trigger is the product addressing? What external trigger gets the user there?

2. Action — What is the simplest behavior the user can perform in anticipation of reward?

3. Reward — Is the reward fulfilling while still leaving enough uncertainty to motivate another cycle?

4. Investment — What small amount of work increases the likelihood that the user returns?

These questions are more useful than asking whether a product is generically "engaging."

They identify the causal mechanism behind repeat behavior.

The three hardest product questions

A separate product framework in the source notes compresses product growth into three questions.

1. How do you get people in the front door?

This is the acquisition problem.

A product with strong retention but no distribution remains invisible.

The question includes:

• discovery

• word of mouth

• referral mechanics

• positioning

• reputation

• app-store presentation

• advertising

• brand

• organic distribution

2. How do you get users to an "aha!" moment as quickly as possible?

This is the activation problem.

The user must encounter the product's core value before patience runs out.

Every step before that moment is a tax.

The goal is not simply shorter onboarding. It is shorter time-to-value.

3. How do you deliver the core product value as often as possible?

This is the retention problem.

Once the user understands the product, the product must repeatedly deliver the reason they came.

This creates a useful operating sequence:

The three questions also discipline prioritization. Teams can spend enormous amounts of time improving features that do not materially affect any of the three.

Find the keystone metric

The notes use Facebook's historical "7 friends in 10 days" example as a model for finding an elegant product statement.

The point is not the specific number.

The point is to discover a behavior that acts as a compact proxy for whether the user has crossed into durable value.

A useful keystone metric should answer:

What observable behavior best predicts that the user has actually understood and experienced the product's core value?

That metric becomes more useful than broad vanity measures because it connects product behavior to retention.

Product discipline

The source notes add several operating principles associated with Chamath Palihapitiya's product philosophy.

• very high intelligence

• strong sense of purpose

• unwillingness to buckle under short-term pressure

• relentless focus on success

• aggressive competition while respecting the person and challenging the idea

• a quality bar bordering on perfectionism

• recruit people better than you

• build frameworks and discipline so the organization continues functioning without you

The central operating rule is:

Do not get distracted by things that do not matter.

That requires resisting short-term ROI when it interferes with the deeper product mechanism.

Gut feeling is not enough as a permanent operating system.
Product lore should be challenged with data and consumer behavior.

The source notes phrase the required posture as being clinical and emotionally unattached to the product.

That does not mean lacking taste or conviction. It means being willing to revise the product when evidence contradicts the story the team tells itself.

Product critique

The final source page converts the theory into a product-review process.

The critique begins with two objectives:

1. understand people's desires

2. understand how people react to things

A useful critique should reconstruct the entire user journey rather than evaluate isolated screens.

Discovery

How did this app come to your attention?

• Was it word of mouth?

• Why did the friend mention it?

• What compelled you to download it?

• Did the icon or name create interest?

• Had you heard of it before?

• How many prior exposures were required?

• Why did you not download it earlier?

• What finally tipped the decision?

This reconstructs the front door.

Positioning

What is your one-line summary of what this app does?

If a user cannot explain the product simply after encountering it, either the proposition is unclear or the experience has failed to communicate it.

Social proof and expectation

What's the buzz so far?

• Is it perceived as popular?

• Useful?

• Well designed?

• Did ratings and reviews create confidence?

• Did screenshots and descriptions communicate the expected experience?

These elements establish an expectation before first use.

The product is then judged partly against that expectation.

First use

Play with the product for several minutes and document the first impressions.

Ask:

• What did you notice first?

• What appeared important?

• What was confusing?

• What felt polished?

• What felt generic?

• What did you expect to happen next?

Do not retrospectively clean up the experience. The value is in the unfiltered first interpretation.

Sign-up and onboarding

Evaluate:

• Was sign-up easy or challenging?

• How did the product explain itself in the first minute?

• Did you read the onboarding or skip it?

• Was the interface immediately understandable?

• Did you have to tap around to discover what to do?

• Were there too many navigation items?

• Did an aha moment occur?

• Did the product deliver on the expectation established before download?

This section measures how quickly the user moves from curiosity to core value.

Retention

Then ask:

• Did the app remain installed?

• What caused you to reopen it?

• Push notification?

• Habit?

• Internal trigger?

• Stored value?

• Social obligation?

• Unfinished task?

• How does it compare with alternatives?

• Where is it better?

• Where is it worse?

• Based on what you now know, does the product appear likely to remain useful a year from now?

This closes the loop between first impression and repeat behavior.

A complete product framework

Together, the three source pages form a broader system than Hooked alone.

Hooked explains why repeated behavior forms.

The three difficult product questions explain what the team should prioritize.

The critique explains how to inspect whether the system is actually working.

Combined:

This is a more complete product model because it connects acquisition, activation, retention, habit formation, and qualitative critique.

Implications

The durable lesson from Hooked is not that every product should maximize engagement.

It is that repeated use has a structure.

Users return because some recurring state triggers an easy action that produces a meaningful reward, and prior use makes the product increasingly valuable or easier to return to.

The stronger product question is therefore not:

How do we make this more addictive?

It is:

What recurring problem deserves to become easier to solve automatically?

That distinction matters because habit formation is only valuable when the repeated behavior serves a durable user need.

The practical operating model is:

The best habit-forming products do not merely capture repeated attention. They become the lowest-friction response to a recurring problem the user already has.