参与度层级框架：提升产品留存与用户粘性的产品管理方法 | 实战指南

hierarchy-of-engagement by pmprompt/claude-plugin-product-management

81 周安装量

21 GitHub Stars

GitHub

安装命令

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

方法论产品管理

🇨🇳中文介绍

领域背景

此技能实现了一个经过验证的产品管理框架。该方法融合了行业领导者的最佳实践，旨在为日常产品管理工作提供实际应用。

输入要求

关于您的产品、功能或问题的背景信息
相关数据、研究或约束条件（建议提供，但可选）
清晰阐述您试图实现的目标

参与度层级

框架简介

参与度层级是一个用于构建能够留住用户并建立防御性的消费产品的三级框架。其核心洞见是：留存来自于产品随着使用次数的增加而变得更好，因此用户离开会损失更多。

大多数消费产品失败并非因为缺乏用户，而是因为缺乏留存。让某人注册是一回事；让他们留下来才是关键。该框架提供了一种系统性的方法来构建那些参与度会随着时间推移而复合增长的产品。

关键的转变是：从问"我们如何获得更多用户？"转向问"我们如何让每个用户的体验随着使用我们的产品而改善？"

使用时机

在以下情况下使用参与度层级框架：

定义您的北极星指标（什么行动最重要？）
改善消费产品或社交产品的留存率
构建超越功能本身的产品粘性
建立防止竞争对手的转换成本
设计您的入门/激活流程
通过参与质量评估产品市场契合度
优先考虑能够驱动复合价值的特性

不适用的场景

在以下情况下不要应用此框架：

构建 B2B 企业软件（留存动态不同）
产品本质上是交易性的（一次性购买）
没有有意义的"随时间使用"模式
在证明留存之前优先优化病毒式获取

参考资料

文章：

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

🇺🇸English

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