Brainstorm Okrs

by phuryn8607e3b07781No license26K starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 3 weeks ago

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-generated overview

Generates three alternative team-level OKR sets aligned with company strategy, each with an objective and three measurable key results.

What it does
This skill acts as a product leader that drafts three distinct, ambitious OKR sets for a named team, aligning them with company objectives. Each set contains an inspirational qualitative objective, exactly three quantitative key results with targets, and a brief rationale. It can read supplied strategy documents, optionally use web search for benchmarks, and save a substantial result as a markdown file named OKRs-[team-name]-[quarter].md.
When to use it
Use it when setting quarterly OKRs, aligning team goals with company strategy, or drafting objectives for a team. It also fits situations where someone wants to learn how to write effective OKRs or compare several strategic options before committing.
Requirements
No scripts are included; it is instructions only. It may read user-provided strategy files and optionally use web search, so network access helps but is not strictly required.

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

Source and attribution

Source:phuryn/pm-skillsinpm-execution/skills/brainstorm-okrsat commit8607e3b

License: No license

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal