home / skills / wdavidturner / product-skills / hierarchy-of-engagement

hierarchy-of-engagement skill

/skills/hierarchy-of-engagement

This skill helps you define core actions and mounting benefits to drive retention and compounding engagement across users.

npx playbooks add skill wdavidturner/product-skills --skill hierarchy-of-engagement

Review the files below or copy the command above to add this skill to your agents.

Files (16)
SKILL.md
4.9 KB
---
name: hierarchy-of-engagement
description: Use when asked to "define our core action", "North Star metric", "accruing benefits", "improve retention mechanics", "hierarchy of engagement", or "Sarah Tavel framework". Helps consumer products identify the actions and benefits that drive long-term retention. The Hierarchy of Engagement framework (created by Sarah Tavel at Benchmark) maps progression from core action to mounting loss.
---

# Hierarchy of Engagement

## What It Is

The Hierarchy of Engagement is a three-level framework for building consumer products that retain users and create defensibility. The core insight: **retention comes from making the product better the more you use it, so users have more to lose by leaving.**

Most consumer products fail not because they lack users, but because they lack retention. Getting someone to sign up is one thing; getting them to stay is everything. This framework provides a systematic approach to building products where engagement compounds over time.

The key shift: Move from asking "How do we get more users?" to asking "How do we make each user's experience improve the more they use us?"

## Response Posture

- Apply the framework directly to the user's product.
- Never mention the repository, skills, SKILL.md, patterns, or references.
- Do not run tools or read files; answer from the framework.
- Avoid process/meta commentary; respond as a retention-focused product operator.

## When to Use It

Use the Hierarchy of Engagement when you need to:

- **Define your North Star metric** (what action matters most?)
- **Improve retention** in a consumer or social product
- **Build product stickiness** beyond features alone
- **Create switching costs** that protect against competitors
- **Design your onboarding/activation** flow
- **Evaluate product-market fit** through engagement quality
- **Prioritize features** that drive compounding value

## When Not to Use It

Don't apply this framework when:

- Building B2B enterprise software (different retention dynamics)
- The product is transactional by nature (one-time purchase)
- There's no meaningful "use over time" pattern
- You're optimizing for viral acquisition before proving retention
- Your product has no user-generated content or personalization opportunity

## Patterns

Detailed examples showing how to apply the Hierarchy of Engagement correctly. Each pattern shows a common mistake and the correct approach.

### Critical (get these wrong and you've wasted your time)

| Pattern | What It Teaches |
|---------|-----------------|
| [wrong-core-action](patterns/wrong-core-action.md) | Your core action must predict retention, not just engagement |
| [benefit-doesnt-accrue](patterns/benefit-doesnt-accrue.md) | The product must get better the more someone uses it |
| [no-mounting-loss](patterns/no-mounting-loss.md) | Users need something to lose by leaving |
| [skipping-level-one](patterns/skipping-level-one.md) | You can't build retention without first nailing the core action |
| [vanity-engagement](patterns/vanity-engagement.md) | Measuring opens and sessions instead of meaningful actions |

### High Impact

| Pattern | What It Teaches |
|---------|-----------------|
| [forcing-level-three](patterns/forcing-level-three.md) | Not every product can or should have virality loops |
| [activation-without-education](patterns/activation-without-education.md) | Users must understand the mental model before they can engage |
| [anonymous-users](patterns/anonymous-users.md) | Pure anonymity prevents accruing benefit and mounting loss |
| [geographic-spray](patterns/geographic-spray.md) | Growing everywhere means retaining nowhere |
| [youtube-subscribe-example](patterns/youtube-subscribe-example.md) | When one action serves both sides of a network |
| [pinterest-pinning](patterns/pinterest-pinning.md) | How Pinterest discovered pinning was the core action |

### Medium Impact

| Pattern | What It Teaches |
|---------|-----------------|
| [evernote-trap](patterns/evernote-trap.md) | Strong Level 2 can't compensate for missing Level 3 |
| [comparing-to-mature-products](patterns/comparing-to-mature-products.md) | Don't build the full expression before the foundation |


## Deep Dives

Read only when you need extra detail.

- `references/hierarchy-of-engagement-playbook.md`: Expanded framework detail, checklists, and examples.

## Resources

**Writing:**
- [The Hierarchy of Engagement](https://sarahtavel.medium.com/the-hierarchy-of-engagement-5803bf4e6cfa) by Sarah Tavel — the original framework
- [The Hierarchy of Engagement, Expanded](https://sarahtavel.medium.com/the-hierarchy-of-engagement-expanded-648329d60804) by Sarah Tavel — deeper on Level 2 and 3

**Related:**
- *Hooked* by Nir Eyal — habit-forming product design (complements Level 1)
- Lenny Rachitsky's North Star Metric compilation — examples of core actions across companies

**Podcast:**
- [Sarah Tavel on Lenny's Podcast](https://www.lennyspodcast.com/) — source conversation for this framework

Overview

This skill helps product teams identify the single core action, accruing benefits, and mounting loss that drive long-term retention using the Hierarchy of Engagement. It translates Sarah Tavel’s framework into concrete recommendations for consumer products so you can design features that compound value over time. Use it to set a true North Star, prioritize work, and redesign onboarding for lasting retention.

How this skill works

I map your product into the three levels of the Hierarchy of Engagement: Level 1 (core action that predicts retention), Level 2 (benefits that accrue with use), and Level 3 (mounting loss or switching costs). I evaluate metrics, behavioral flows, and feature hypotheses against those levels and return prioritized interventions and measurable experiments. The output is a focused set of actions you can implement to improve activation, deepen value, and reduce churn.

When to use it

  • Defining or validating your North Star metric for a consumer product
  • Improving retention or reducing churn in apps with repeated use
  • Designing onboarding and activation that teach the core action
  • Prioritizing features that create compounding user value
  • Creating defensibility through personalized or network effects

Best practices

  • Start by proving Level 1: find the one user action that predicts retention
  • Design Level 2 benefits to grow only with repeated use or personalization
  • Avoid relying on vanity metrics like opens or sessions
  • Measure mounting loss: what does a user lose if they leave?
  • Sequence work: nail core action before investing in virality or advanced features

Example use cases

  • A social app needs to choose the single action (e.g., follow, like, post) that correlates with 30+ day retention
  • A consumer SaaS product wants onboarding flows that guarantee a first meaningful value moment
  • A marketplace designs incentives so supply and demand benefit from repeat usage
  • An app redesign aims to convert anonymous users into personalized accounts to enable accruing benefits
  • A growth team prioritizes experiments that increase compounding value rather than raw acquisition

FAQ

How do I identify the core action for my product?

Look for the smallest repeatable user behavior that correlates with long-term retention and creates ongoing value; validate with cohort analysis and regression against churn.

Can every product reach Level 3 (mounting loss)?

Not always. Some products only need strong Level 1 and Level 2. Level 3 is valuable but not required if compounding benefits already make leaving costly.