hierarchy-of-engagement

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.

Safety Notice

This listing is imported from skills.sh public index metadata. Review upstream SKILL.md and repository scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "hierarchy-of-engagement" with this command: npx skills add pmprompt/claude-plugin-product-management/pmprompt-claude-plugin-product-management-hierarchy-of-engagement

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

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

prd-writer

No summary provided by upstream source.

Repository SourceNeeds Review
General

feature-prioritization-assistant

No summary provided by upstream source.

Repository SourceNeeds Review
General

thinking-in-bets

No summary provided by upstream source.

Repository SourceNeeds Review
General

user-feedback-synthesizer

No summary provided by upstream source.

Repository SourceNeeds Review