hooked-ux

$npx mdskill add wondelai/skills/hooked-ux

Design habit-forming product loops using the Hook Model.

  • Solves low user retention and lack of engagement after signup.
  • Depends on the Hook Model framework and ethics evaluation matrix.
  • Scores each loop phase and applies the Manipulation Matrix gate.
  • Delivers actionable recommendations for triggers, actions, rewards, and investments.

SKILL.md

.github/skills/hooked-uxView on GitHub ↗
---
name: hooked-ux
description: 'Design habit-forming product loops using the Hook Model (Trigger, Action, Variable Reward, Investment). Use when the user mentions "users arent coming back", "habit formation", "engagement loops", "habit zone", or "the manipulation matrix". Also trigger when designing notification or re-engagement strategies, building streaks or progress systems, or analyzing why users stop after signup. Covers ethics evaluation and onboarding for habits. For friction reduction and B=MAP, see improve-retention. For viral sharing, see contagious.'
license: MIT
metadata:
  author: wondelai
  version: "1.5.1"
---

# Hook Model Framework

Framework for building habit-forming products. Habits are not created — they are built through successive cycles through the Hook.

## Core Principle

**The Hook Model** = a four-phase loop that connects the user's problem to your solution frequently enough to form a habit, moving usage from deliberate to automatic.

```
Trigger → Action → Variable Reward → Investment
    ↑                                      │
    └──────────────────────────────────────┘
```

## Scoring

**Goal: 10/10.** When reviewing or creating product engagement mechanics, score the loop by the four Quick Diagnostic rows (internal trigger, dead-simple action, variable reward, investment loads next trigger): each row earns 2 (fully satisfied), 1 (partial), or 0 (absent), then `score = round(total / 8 × 10)`. Then apply the ethics gate: if the Manipulation Matrix places the product as Dealer (or it hits any "When NOT to Use" condition), cap the score at 3 regardless of mechanics. Bands: 9-10 = complete loop, internal trigger identified, ethics clear; 5-6 = loop runs but leans on external triggers or predictable rewards; <=3 = broken loop or extractive design. Always state the current score and the specific diagnostic rows blocking 10/10.

## The Four Phases

### 1. Trigger

**Core concept:** The actuator of behavior. Triggers are external (environment-driven: notifications, emails, ads) or internal (emotion-driven) — and the goal is to migrate users from external to internal triggers.

**Why it works:** Every habit starts with a cue. External triggers get users started, but internal triggers — boredom, loneliness, uncertainty, FOMO — drive unprompted usage because the emotion itself fires before any reminder can.

**Key insights:**
- Map your product to the specific negative emotion it resolves (boredom, loneliness, confusion, FOMO)
- Effective external triggers are well-timed, actionable, and lead to the simplest possible next action
- If users still need external prompts after ~30 days, no internal trigger has formed

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| **Onboarding** | External triggers establish the first loop | Welcome email with one clear action |
| **Retention** | Map product to internal emotional trigger | Instagram resolves boredom; Google resolves confusion |
| **Re-engagement** | External triggers bridge gaps until habit forms | Push: "Your friend just posted a photo" |

**Copy patterns:**
- "Don't miss what happened while you were away" (FOMO trigger)
- "Your friend just..." (social trigger bridging to internal)
- "Pick up where you left off" (routine trigger)

**Ethical boundary:** Don't build triggers that fire on vulnerable emotional states (depression, addiction, grief) — those users can't exercise the autonomy the loop assumes.

See [references/triggers.md](references/triggers.md) when mapping triggers — the emotion-to-product mapping exercise and the external-to-internal transition plan.

### 2. Action

**Core concept:** The simplest behavior done in anticipation of a reward, guided by the Fogg Behavior Model: Behavior = Motivation + Ability + Trigger, all converging at the same moment.

**Why it works:** Increasing motivation is hard and unreliable; reducing friction (increasing ability) is easier and more effective. Every extra step, field, or decision is a drop-off point.

**Key insights:**
- Six elements of simplicity: time, money, physical effort, brain cycles, social deviance, non-routine
- The action is the simplest behavior in anticipation of reward — not the full task
- Hick's Law: more choices = slower decisions; reduce options to increase action rate

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| **Signup flow** | Minimize fields and steps | One-click Google/Apple sign-in |
| **Core action** | Completable in seconds | Twitter: type 280 characters and post |
| **Progressive disclosure** | Ask for more only after initial reward | Duolingo: play first, create account later |

**Copy patterns:**
- "Just one tap to..." (emphasizes simplicity)
- "No credit card required" (money/risk simplicity)
- Buttons should be verbs: "Post", "Save", "Share" — not "Submit" or "Continue"

**Ethical boundary:** When you simplify an action, don't strip the cost or consequence with it — a one-tap purchase must still surface the price and the commitment.

See [references/product-applications.md](references/product-applications.md) when adapting the loop to your context — action and investment patterns for B2B SaaS, e-commerce, health, and productivity tools.

### 3. Variable Reward

**Core concept:** The phase that keeps users coming back. Anticipation of reward — not the reward itself — creates dopamine, and rewards must be variable (unpredictable) to sustain engagement.

**Why it works:** The brain's dopamine system responds most strongly to anticipation of uncertain rewards — the slot machine effect. Three reward types — tribe (social), hunt (resources), self (mastery) — tap fundamental human drives.

**Key insights:**
- Tribe = social validation; Hunt = search for resources/information; Self = personal mastery
- Predictable rewards lose power; finite variability eventually becomes predictable — aim for infinite variability
- Autonomy is critical: users must feel in control; forced engagement backfires

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| **Social features (Tribe)** | Variable social validation | Instagram likes — you never know how many |
| **Content feeds (Hunt)** | Unpredictable resource stream | Infinite scroll with algorithmically varied content |
| **Gamification (Self)** | Accomplishment with variable difficulty | Duolingo streaks + surprise bonus challenges |

**Copy patterns:**
- "See what's new" (implies variability)
- "3 people responded to your post" (tribe reward, variable quantity)
- "You've unlocked a new achievement!" (self reward, unexpected)

**Ethical boundary:** If users consistently feel worse after engaging (regret, time loss, anxiety), the reward system is extractive — avoid infinite scroll without natural stopping points.

See [references/rewards.md](references/rewards.md) when designing a reward — tribe/hunt/self patterns, the four reinforcement schedules, and reward timing. For the dopamine/anticipation mechanism behind variable rewards, see [references/neuroscience-foundations.md](references/neuroscience-foundations.md).

### 4. Investment

**Core concept:** Users invest something — time, data, effort, social capital, money — that improves the product for next use, raises switching costs, and loads the next trigger.

**Why it works:** People value what they put effort into (the IKEA effect). Investment is not about immediate reward — it improves the next cycle, creating a self-reinforcing loop.

**Key insights:**
- Investment should come after reward, not before — users invest when they feel good
- Each investment should load the next trigger (posting content triggers reply notifications)
- Small investments compound: preferences → better recommendations → more usage; stored value grows over time

**Product applications:**

| Context | Application | Example |
|---------|-------------|---------|
| **Data investment** | History improves personalization | Spotify: more listening = better recommendations |
| **Content investment** | User-created content they won't abandon | Instagram posts, Notion documents |
| **Reputation/social investment** | Social capital that exists only on-platform | Airbnb host ratings, LinkedIn network |

**Copy patterns:**
- "Complete your profile to get better matches" (investment → future value)
- "The more you use it, the smarter it gets" (compound investment)
- "Invite your team to collaborate" (social investment)

**Ethical boundary:** Investment should genuinely improve the experience — never trap users with artificial switching costs or impossible data export; make staying the better choice through real value.

## The Habit Zone

Two axes determine if a product can become a habit:

| | Low Frequency | High Frequency |
|--|---------------|----------------|
| **High Perceived Value** | Viable product (needs ads/marketing) | **HABIT ZONE** |
| **Low Perceived Value** | Failure | Failure |

Ask: how often do users need to engage, what's the perceived value of each engagement, and is frequency high enough to form automatic behavior?

## Habit Testing

The 5% rule: a habit has formed when at least 5% of users show unprompted, habitual usage.

**Three questions:**
1. **Who are the habitual users?** Which users engage most frequently, and what do they share?
2. **What are they doing?** Identify the "Habit Path" — the action sequence that separates power users from casual users.
3. **Why are they doing it?** What internal trigger and emotion precede usage?

See [references/habit-testing.md](references/habit-testing.md) when running the test — cohort analysis, finding the Habit Path, and confirming the 5% threshold. For worked teardowns of these loops in real products (Instagram, Slack, Duolingo, Pinterest, and failures), see [references/case-studies.md](references/case-studies.md).

## The Manipulation Matrix

Framework for evaluating the ethics of habit-forming products:

|  | **Maker Uses Product** | **Maker Doesn't Use** |
|--|------------------------|----------------------|
| **Materially Improves User's Life** | **Facilitator** | **Peddler** |
| **Doesn't Improve Life** | **Entertainer** | **Dealer** |

Ask: would I use this myself? Does it genuinely help users achieve their goals? Am I exploiting vulnerabilities or serving needs?

### When NOT to Use the Hook Model

- Your product doesn't genuinely improve lives
- You're targeting vulnerable populations (children, addiction-prone users)
- The business model depends on user regret
- Engagement conflicts with user wellbeing

See [references/ethical-boundaries.md](references/ethical-boundaries.md) when the Manipulation Matrix flags a concern — dark-pattern catalog and how to protect vulnerable users.

### Regulatory Context

Watch emerging regulation: children's apps (COPPA, GDPR-K), dark patterns (rising FTC enforcement), "addictive" notification practices, and loot boxes (expanding gaming rules).

## Onboarding Audit Checklist

Optimizing onboarding for habit formation:

### First Trigger
- [ ] First action obvious and easy; right external trigger for this user
- [ ] Value proposition clear before asking for investment

### First Action
- [ ] Core action completable in under 60 seconds, friction removed
- [ ] UI familiar (no new learning required)

### First Reward
- [ ] Immediate feedback with a variable element (surprise, delight)
- [ ] Reward connects to an internal trigger

### First Investment
- [ ] Investment asked after reward (not before), small but meaningful
- [ ] Investment loads the next trigger

### Loop Completion
- [ ] Clear path back to the trigger; external triggers sent at appropriate times
- [ ] Progression through the Hook is measured

## Common Mistakes

| Mistake | Why It Fails | Fix |
|---------|-------------|------|
| **Relying on external triggers indefinitely** | You're renting attention, not building habits | Map product to an emotion; transition to internal triggers within 30 days |
| **Making the core action too complex** | Users drop off before the reward | Simplify to minimum viable action; apply the six ability factors |
| **Using predictable rewards** | Dopamine response fades with novelty | Add variability across tribe, hunt, and self rewards |
| **Asking for investment before reward** | Users haven't received value yet | Sequence: trigger, action, reward, THEN investment |
| **Ignoring the ethics of your hook** | User regret, backlash, regulatory risk | Use the Manipulation Matrix; be a Facilitator, not a Dealer |

## Quick Diagnostic

Audit any product feature:

| Question | If No | Action |
|----------|-------|--------|
| What's the internal trigger? | Users need reminders to use it | Research user emotions |
| Is the action dead simple? | Users start but don't complete | Remove friction |
| Is the reward variable? | Users get bored | Add unpredictability |
| Does investment load next trigger? | Users don't return | Connect investment to triggers |

## Further Reading

Based on the Hook Model developed by Nir Eyal:

- [*"Hooked: How to Build Habit-Forming Products"*](https://www.amazon.com/Hooked-How-Build-Habit-Forming-Products/dp/1591847788?tag=wondelai00-20) by Nir Eyal
- [*"Indistractable: How to Control Your Attention and Choose Your Life"*](https://www.amazon.com/Indistractable-Control-Your-Attention-Choose/dp/194883653X?tag=wondelai00-20) by Nir Eyal (companion: resisting unwanted habits and building focus)

## About the Author

**Nir Eyal** taught at Stanford Graduate School of Business and the Hasso Plattner Institute of Design, after working in the gaming and advertising industries where he saw habit psychology firsthand. *Hooked* distills that research into a framework used by product teams from startups to Fortune 500s; his follow-up *Indistractable* addresses resisting the same triggers.

More from wondelai/skills

SkillDescription
37signals-wayBuild lean, opinionated products using the 37signals philosophy from "Getting Real", "Rework", and "Shape Up". Use when the user mentions "Getting Real", "Rework", "Shape Up", "37signals", "Basecamp method", "six-week cycles", "fixed time variable scope", "appetite vs estimates", "betting table", "breadboarding", "fat marker sketch", "build less", "underdo the competition", "opinionated software", "we have too many meetings", "how do we ship faster", or "stop overbuilding". Also trigger when cutting scope to ship sooner, running a small team, or avoiding long-term roadmaps. Covers shaping, betting, building, and the art of saying no. For MVP validation, see lean-startup. For design sprints, see design-sprint.
blue-ocean-strategyCreate uncontested market space using value innovation instead of competing head-to-head. Use when the user mentions "blue ocean", "red ocean", "strategy canvas", "ERRC framework", "value innovation", "non-customers", "buyer utility map", "the market is too crowded", "how do we stand out", or "escape the price war". Also trigger when exploring a new market category, or finding underserved or non-customers. Covers the Four Actions Framework, Six Paths, buyer utility map, and value-cost trade-offs. For real strategy formulation and bad-strategy detection, see good-strategy-bad-strategy. For tech adoption strategy, see crossing-the-chasm. For product positioning, see obviously-awesome.
clean-architectureStructure software around the Dependency Rule: source code dependencies point inward from frameworks to use cases to entities. Use when the user mentions "architecture layers", "dependency rule", "ports and adapters (hexagonal)", "onion architecture", "screaming architecture", "where should business logic go", "decouple from the database", "swap the framework without a rewrite", or "keep business rules independent". Also trigger when deciding which layer code belongs in, isolating core logic from infrastructure, defining module boundaries, or debating whether the framework should call your code or the reverse. Covers component principles, boundaries, and SOLID. For code-level quality, see clean-code. For domain modeling, see domain-driven-design.
clean-codeWrite readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "clean up this code", "this function is too long", "code smells", "naming conventions", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing a pull request for readability, untangling a messy function, debating comment styles, or improving error-handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture and dependency rules, see clean-architecture.
cold-start-problemStart and scale networked products using Andrew Chen''s "The Cold Start Problem" framework for network effects. Use when the user mentions "network effects", "chicken and egg", "cold start", "two-sided marketplace", "atomic network", "hard side", "liquidity", "critical mass", "invite-only launch", "how do I get my first users", or "the marketplace has no buyers or sellers". Also trigger when launching a marketplace, social, or collaboration product that is worthless without other users, deciding launch sequencing and seeding tactics, or diagnosing stalled network growth at scale. Covers the five stages: cold start, tipping point, escape velocity, hitting the ceiling, and the moat. For word-of-mouth virality, see contagious. For habit-driven retention, see hooked-ux.
contagiousEngineer word-of-mouth and virality using the STEPPS framework (Social Currency, Triggers, Emotion, Public, Practical Value, Stories). Use when the user mentions "go viral", "word of mouth", "shareable content", "social currency", "why people share", "referral program", "nobody is sharing it", or "make this spread". Also trigger when designing shareable features, crafting social campaigns, or building products that spread through peer recommendation. Covers environmental triggers and high-arousal emotional content. For sticky messaging, see made-to-stick. For persuasion tactics, see influence-psychology.
continuous-discoveryBuild a weekly cadence of customer touchpoints using Opportunity Solution Trees, assumption mapping, and interview snapshots. Use when the user mentions "continuous discovery", "opportunity solution tree", "weekly interviews", "assumption testing", "discovery habits", "product trio", "outcome-based roadmap", "how do I talk to customers regularly", "we keep building things nobody uses", or "connect research to the roadmap". Also trigger when setting up regular customer feedback loops, prioritizing which experiments to run, or tying discovery insights to delivery work. Covers experience mapping, co-creation, and prioritizing opportunities. For interview technique, see mom-test. For team structure, see inspired-product.
create-appGuided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way, software-design-philosophy - asking the user questions at every decision point and recording results in the project docs/ folder (PRODUCT.md, ARCHITECTURE.md, EXPERIMENTS.md, CREATE-APP-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new app, validate an idea before writing code, architect an MVP that will not need a rewrite, or says ''help me build my app the right way''. App already exists: use improve-app or grow-app. Business idea not yet validated: run create-business first. Marketing site only: use create-website. Architecture-only question: design-code-architecture. For one framework in isolation, invoke that skill directly.
create-businessGuided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation, crossing-the-chasm - asking the user questions at every decision point and recording results in the project docs/ folder (CUSTOMER.md, POSITIONING.md, OFFER.md, CREATE-BUSINESS-PLAN.md) so the journey resumes across sessions. Use when the user wants to start a new business, validate a startup idea, find product-market fit before building, or says ''I have an idea for a company''. Do not use once the business has paying customers: use grow-business to add revenue and customers, or improve-business to fix strategy and operations. For building the product itself use create-app or create-website. For one framework in isolation, invoke that skill directly.
create-websiteGuided journey from a blank page to a live, high-converting website, built message-first, then design, then conversion. Orchestrates ten skills phase by phase - one-page-marketing, storybrand-messaging, made-to-stick, top-design, web-typography, refactoring-ui, ux-heuristics, cro-methodology, scorecard-marketing, steve-jobs-design-review - asking the user questions at every decision point and recording results in the project docs/ folder (POSITIONING.md, WEBSITE.md, DESIGN.md, CREATE-WEBSITE-PLAN.md) so the journey resumes across sessions. Use when the user wants to build a new website or landing page from scratch, turn a validated idea into a page that converts, or says ''build me a landing page for my SaaS''. Site already exists: use improve-website to fix conversion/UX or grow-website for more traffic; building a software product, not a marketing site: use create-app; no positioning yet: run create-business first or the positioning phase here. For one framework in isolation, invoke that skill directly.