mcpField
H
hierarchy-of-engagement

hierarchy-of-engagement

github.com/pmpromptMarketing & growth55341 installsUpdated 6d ago
Repository

About hierarchy-of-engagement

A product management skill for consumer product teams applying the Hierarchy of Engagement framework. It focuses on how value can compound with continued use, informing retention, switching costs, and feature priorities.

Key features

  1. 01Define a North Star metric
  2. 02Assess engagement and retention
  3. 03Identify value that compounds with use
  4. 04Evaluate switching costs and stickiness
  5. 05Guide onboarding and activation design
  6. 06Prioritize features for compounding value

Use cases

  1. 01Improve retention in consumer or social products
  2. 02Design onboarding and activation
  3. 03Assess product-market fit
  4. 04Prioritize features that create long-term value

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/pmprompt/claude-plugin-product-management --skill hierarchy-of-engagement

After installing, type/hierarchy-of-engagementin Claude Code to confirm it loaded.

Details

From the project README

Domain Context

This skill implements a proven product management framework. The approach combines best practices from industry leaders and is designed for practical application in day-to-day PM work.

Input Requirements

  • Context about your product, feature, or problem
  • Relevant data, research, or constraints (recommended but optional)
  • Clear articulation of what you're trying to achieve

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?"

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

Resources

Writing:

  • The Hierarchy of Engagement by Sarah Tavel (Medium)
  • The Hierarchy of Engagement, Expanded by Sarah Tavel

Further Reading

Comments

Markdown supported