setting-okrs-goals

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Setting OKRs & Goals

设定OKRs与目标

Help the user create effective objectives and key results using frameworks and insights from 55 product leaders.

帮助用户借助55位产品领导者的框架和见解，创建有效的目标与关键结果。

How to Help

如何提供帮助

When the user asks for help with OKRs or goal setting:

Understand context - Ask about their company stage, team size, and whether they have existing goals or are starting fresh
Clarify the level - Determine if these are company, department, team, or individual goals
Identify the strategy - Ensure they have a clear strategy before setting goals (goals should be the end of strategy, not the beginning)
Guide the structure - Help them write inspiring objectives and measurable key results that avoid common pitfalls

当用户寻求OKR或目标设定相关帮助时：

了解背景 - 询问他们的公司阶段、团队规模，以及是否已有现有目标或是从零开始
明确层级 - 确定这些是公司、部门、团队还是个人目标
确认战略 - 在设定目标前确保他们有清晰的战略（目标应是战略的结果，而非起点）
指导结构搭建 - 帮助他们撰写鼓舞人心的目标和可衡量的关键结果，避开常见陷阱

Core Principles

核心原则

Goals should be one step from company goals

目标应与公司目标仅一步之遥

Matt LeMay: "No more than one step away from company goals. Don't let it get cascaded into oblivion." Ensure team goals orbit directly around the primary company objective rather than being buried under layers of organizational cascading.

Matt LeMay：“与公司目标的距离不应超过一步。不要让目标在层层传递中失去意义。”确保团队目标直接围绕公司核心目标展开，而非被多层组织架构的层层传递所淹没。

Build systems, not just goals

构建体系，而非仅设定目标

Lane Shackleton: "Instead of being obsessed with the goal, be obsessed with the system that gets you there." Replace one-time OKR targets with recurring 'default-on' systems like standing customer meetings that build long-term instincts.

Lane Shackleton：“与其执着于目标，不如执着于实现目标的体系。”用定期的“默认开启”体系（如固定的客户会议）替代一次性的OKR目标，培养长期的工作直觉。

OKRs bridge strategy to execution

OKRs是战略与执行的桥梁

Christina Wodtke: "The main benefit is that there's a lot of concrete action through an OKR that you don't always get from strategy." Use OKRs to turn abstract strategy into concrete quarterly numbers while creating a learning cycle through end-of-quarter grading.

Christina Wodtke：“主要优势在于，OKR能带来大量具体行动，这是单纯战略所不具备的。”利用OKRs将抽象战略转化为具体的季度数字，同时通过季度末的评估形成学习循环。

Triangulate with three key results

用三个关键结果形成三角验证

Christina Wodtke: "I like three. Something that's really hardcore numbers, something that's a little squishier like quality, and something that involves a dollar sign." Balance quantitative, qualitative, and financial metrics for a complete view of success.

Christina Wodtke：“我喜欢设定三个：一个是硬核量化指标，一个是偏定性的质量指标，还有一个涉及财务相关的指标。”平衡量化、定性和财务指标，全面衡量成功。

Use absolute numbers, not ratios

使用绝对数值，而非比率

Archie Abrams: "Ratios and percentages are dangerous metrics because they can be 'gamed' by reducing the denominator." Shift goals from 'conversion rate' to 'absolute number of users reaching a specific state' to prevent gaming.

Archie Abrams：“比率和百分比是危险的指标，因为可以通过缩小分母来‘操纵’结果。”将目标从“转化率”转变为“达到特定状态的用户绝对数量”，防止指标操纵。

Ambitious goals force new thinking

有野心的目标催生新思维

Daniel Lereya: "Put ambitious goals, it'll make you think differently. We really love to do it even when we don't know it's possible." Set goals impossible to achieve through 'working harder' alone to force 'working smarter' and fundamental rethinks.

Daniel Lereya：“设定有野心的目标，这会让你换个角度思考。即便不知道能否实现，我们也热衷于这么做。”设定仅靠“更努力工作”无法实现的目标，倒逼团队“更聪明地工作”，从根本上重新思考方法。

Separate strategy from OKR discussions

将战略讨论与OKR讨论分离

Lane Shackleton: "OKRs are not actually strategy. It's critical to disconnect strategy discussions from OKR discussions." Create a distinct strategy ritual before OKR planning to ensure the 'why' isn't lost in the 'what'.

Lane Shackleton：“OKRs并非战略本身。将战略讨论与OKR讨论分开至关重要。”在OKR规划前先开展专门的战略研讨，确保“为什么做”不会被“做什么”所掩盖。

Limit planning overhead

限制规划成本

Lane Shackleton: "The 10% planning rule - ensure you're not planning for more than 10% of that execution period." If planning for a quarter, spend no more than about a week on the planning process.

Lane Shackleton：“10%规划原则——确保规划时间不超过执行周期的10%。”如果是季度规划，花费的时间不应超过一周左右。

Focus on outcomes, not outputs

聚焦结果，而非产出

Marty Cagan: "In a real product team, you celebrate when you actually solve the problem. That's why we say product teams are about outcomes, not output." Define success by problem resolution rather than feature shipment.

Marty Cagan：“在真正的产品团队中，你会为实际解决问题而庆祝。这就是为什么我们说产品团队要关注结果，而非产出。”以问题是否解决来定义成功，而非是否交付了功能。

Goals are communication tools

目标是沟通工具

Molly Graham: "No company needs more than three company goals. The point is to help people know what the most important things are." Keep goals simple, ensure one wins in a fight, and assign exactly one owner to every goal.

Molly Graham：“任何公司都不需要超过3个公司级目标。关键是让人们知道最重要的事情是什么。”保持目标简洁，确保在优先级冲突时有明确的胜出项，并且每个目标都指定唯一负责人。

Questions to Help Users

用于引导用户的问题

"What is your company's primary goal right now, and how does this team goal connect to it?"
"How will you know if you've succeeded - what specific number would change?"
"Is this objective inspiring enough to motivate the team through obstacles?"
"Are your key results outcomes (how you know you succeeded) or tasks (a to-do list)?"
"What system could you build to make progress on this goal 'default-on'?"
"If you achieve this goal but hurt user experience, would it still be a success?"

“你们公司当前的核心目标是什么，这个团队目标如何与之关联？”
“你们如何判断是否成功——会有哪些具体的数字变化？”
“这个目标是否足够鼓舞人心，能激励团队克服障碍？”
“你的关键结果是结果（如何判断成功）还是任务（待办清单）？”
“你可以构建什么体系来让这个目标的进展‘默认推进’？”
“如果实现了这个目标但损害了用户体验，这还能算是成功吗？”

Common Mistakes to Flag

需要指出的常见错误

Key results that are tasks - Key results should be measurable outcomes, not a checklist of activities to complete
Too many goals - Companies need no more than three goals; more than that dilutes focus and prevents trade-offs
Vague objectives - Objectives should make you excited to get out of bed, not generic corporate language
Goals set before strategy - If you don't have a real strategy, OKRs become meaningless exercises in false precision
Over-indexing on a single metric - This can incentivize keeping customer-hostile features that happen to move the number

关键结果是任务——关键结果应是可衡量的结果，而非待完成的活动清单
目标过多——公司的目标不应超过3个；过多会分散注意力，无法做出取舍
目标模糊——目标应能让你充满动力起床工作，而非空泛的企业话术
先设定目标再制定战略——如果没有明确的战略，OKRs就会沦为虚假精准的无意义练习
过度依赖单一指标——这可能会促使团队保留对客户不利但能提升指标的功能

Deep Dive

深入了解

For all 74 insights from 55 guests, see

references/guest-insights.md

如需获取来自55位嘉宾的全部74条见解，请查看

references/guest-insights.md