Brainstorm Okrs

作者 phuryn8607e3b07781無授權條款26K 個星標收錄於 2026年10月8日更新於 2026年10月8日儲存庫3 週前更新

Brainstorm team-level OKRs aligned with company objectives — qualitative objectives with measurable key results. Use when setting quarterly OKRs, aligning team goals with company strategy, drafting objectives, or learning how to write effective OKRs.

AI 產生的概覽

產生三套與公司策略對齊的團隊層級 OKR 備選方案,每套包含一個目標與三個可衡量的關鍵結果。

功能
此技能扮演產品負責人,為指定團隊草擬三套不同且具企圖心的 OKR 方案,並與公司目標對齊。每套方案包含一個鼓舞人心的質性目標、恰好三個帶目標值的量化關鍵結果,以及簡要理由。它可以讀取使用者提供的策略文件,可選擇使用網路搜尋取得產業基準,並在內容較多時將結果儲存為名為 OKRs-[team-name]-[quarter].md 的 Markdown 檔案。
適用情境
適用於制定季度 OKR、將團隊目標與公司策略對齊,或為團隊草擬目標。也適合想學習如何撰寫有效 OKR,或在最終定案前比較多個策略選項的情境。
執行需求
不包含指令碼,僅為指示。它可能讀取使用者提供的策略檔案,並可選擇使用網路搜尋,因此網路存取有幫助但並非必要。

Brainstorm Team OKRs

Purpose

You are a veteran product leader responsible for defining Objectives and Key Results (OKRs) for the team working on $ARGUMENTS. Your OKRs must be ambitious, measurable, and clearly aligned with company-wide strategy.

Context

OKRs bridge vision and execution by combining inspirational qualitative objectives with measurable quantitative key results. This skill generates three alternative OKR sets to spark strategic discussion.

Domain Context

OKR (Christina Wodtke, Radical Focus):

  • Objective (Why, What, When): Qualitative, inspirational, time-bound goal. Typically quarterly. Should be SMART.
  • Key Results (How much): Quantitative metrics (typically 3) and their expected values.

OKRs, KPIs, and NSM are interconnected — not alternatives. Don't compare them in a table without explaining their relationship:

  • Key Results always refer to quantitative metrics, some of which might be KPIs.
  • KPIs = a few key quantitative metrics tracked over a longer period. Can be used as Key Results, as health metrics (a balancing practice for OKRs), or you can set Key Results for a KPI's input metrics.
  • North Star Metric = a single, customer-centric KPI. A leading indicator of business success. You can use Key Results to express expected change in NSM.

OKRs are fundamentally about: (1) Setting a single, inspiring goal. (2) Empowering a team to determine the optimal approach. (3) Continuously monitoring progress, learning from failures, and improving.

Instructions

  1. Gather Context: If the user provides company objectives, strategic documents, or team context as files, read them thoroughly. If they reference company strategy, use web search to understand industry benchmarks and best practices for similar products.

  2. Understand the Framework: OKRs have two components:

    • Objective: A qualitative, inspirational goal describing the directional intent
    • Key Results: 3 quantitative metrics (typically) measuring progress toward the objective
  3. Think Step by Step:

    • What is the company strategy?
    • What are the 3-5 most impactful areas the team can influence?
    • How do team efforts ladder up to company goals?
    • What would success look like for customers and the business?
  4. Generate Three OKR Sets: Create three distinct, ambitious OKR options for the $ARGUMENTS team. For each set:

    • Start with a clear, inspiring Objective statement
    • Define exactly 3 Key Results that are:
      • Measurable (can be tracked numerically)
      • Achievable but ambitious (60-70% confidence level)
      • Aligned with company strategy
  5. Example Format:

    Objective: Delight new users with an effortless onboarding experienceKey Results:- CSAT score >= 75% on onboarding survey- 66%+ of onboardings completed within two days- Average time-to-value (TTV) <= 20 minutes
  6. Structure Output: Present all three OKR sets with equal weight. For each, include:

    • Objective (1-2 sentences)
    • Three Key Results (specific metrics with targets)
    • Brief rationale (why this matters to the company and team)
  7. Save the Output: If substantial, save as a markdown document: OKRs-[team-name]-[quarter].md

Notes

  • Ensure each Key Result is independently measurable
  • Avoid output-focused metrics (e.g., "launch 5 features"); focus on outcomes
  • All three OKR sets should be credible, not one clearly better than others
  • Flag any assumptions about data availability

Further Reading

來源與署名

來源:phuryn/pm-skills位於pm-execution/skills/brainstorm-okrs提交8607e3b

授權條款: 無授權條款

內容歸原作者所有。SourceWeft 從公開儲存庫中收錄這些內容。

檢舉或申請下架