OKRs目标管理框架 - 产品经理必备的OKR设定与执行工具 | PMPrompt

okrs by pmprompt/claude-plugin-product-management

134 周安装量

22 GitHub Stars

GitHub

安装命令

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

方法论项目管理产品管理

🇨🇳中文介绍

领域背景

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

输入要求

关于您的产品、功能或问题的背景信息
相关数据、研究或约束条件（推荐但可选）
清晰阐述您希望实现的目标

OKRs（目标与关键成果）

定义

OKRs 是一个目标设定框架，旨在为团队和组织创造专注、协调和学习周期。其核心洞见是：每季度设定一个雄心勃勃的目标，并辅以 2-3 个可衡量的关键成果，然后每周跟进以保持专注。

关键的转变在于：从跟踪活动（"我们在做什么？"）转向跟踪成果（"我们在实现目标方面取得了哪些进展？"）。

OKRs 是维生素，而非药物。它们能极大地增强那些基础已经稳固（拥有战略、授权团队、心理安全感）的公司的能力。它们无法修复破碎的组织——它们只会揭示问题所在。

适用场景

当您需要时，请使用 OKRs：

聚焦团队 于本季度最重要的一件事
协调组织 使每个人都知道什么最重要
通过可衡量的成果（而不仅仅是活动）建立问责制
通过每周跟进和季度回顾建立学习周期
扩展领导力 使创始人/高管无需进行微观管理
通过避免精力过于分散的"花生酱"问题来加速进展

不适用场景

您没有明确的战略（OKRs 会揭示缺失的战略，但无法替代它）
您的公司缺乏心理安全感
您希望跟踪所有工作（OKRs 用于确定优先事项，而非全面的任务清单）
团队未被授权决定如何实现成果

资源

书籍：

Christina Wodtke 所著的《Radical Focus》（第二版）
John Doerr 所著的《Measure What Matters》

广告位招租

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

触达数万 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

OKRs (Objectives and Key Results)

What It Is

OKRs are a goal-setting framework that creates focus, alignment, and a learning cycle for teams and organizations. The core insight: set one ambitious objective per quarter with 2-3 measurable key results, then check in weekly to maintain focus.

The key shift: Move from tracking activities ("What are we doing?") to tracking outcomes ("What progress are we making toward our goals?").

OKRs are a vitamin, not a medicine. They supercharge companies that already have their fundamentals in place (strategy, empowered teams, psychological safety). They won't fix broken organizations - they'll just reveal what's broken.

When to Use It

Use OKRs when you need to:

Focus the team on the single most important thing for the quarter
Align the organization so everyone knows what matters most
Create accountability with measurable outcomes (not just activities)
Build a learning cycle through weekly check-ins and quarterly retrospectives
Scale leadership so founders/executives don't need to micromanage
Accelerate progress by avoiding the "peanut butter" problem of spreading effort too thin

When Not to Use It

You don't have a clear strategy (OKRs reveal missing strategy, they don't replace it)
Your company lacks psychological safety
You want to track ALL the work (OKRs are for priorities, not comprehensive task lists)
Teams aren't empowered to decide HOW to achieve outcomes

Resources

Books:

Radical Focus (2nd Edition) by Christina Wodtke
Measure What Matters by John Doerr
High Output Management by Andy Grove