# brainstorm okrs ## Metadata - Canonical URL: https://6ducklearn.com/skills/brainstorm-okrs/ - Markdown URL: https://6ducklearn.com/skills/brainstorm-okrs/index.md - Product: skills - Category: product-management - Tags: pm-execution, product-management, pm-skills - Updated: 2026-07-14T03:00:00.357428+00:00 ## Summary 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. ## Content # 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 experience Key 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 - [Objectives and Key Results (OKRs) 101](https://www.productcompass.pm/p/okrs-101-advanced-techniques) - [OKR vs KPI: What's the Difference?](https://www.productcompass.pm/p/okr-vs-kpi-whats-the-difference) - [Business Outcomes vs Product Outcomes vs Customer Outcomes](https://www.productcompass.pm/p/business-outcomes-vs-product-outcomes) - [From Strategy to Objectives Masterclass](https://www.productcompass.pm/p/product-vision-strategy-objectives-course) (video course) ## Related Skills - [create prd](https://6ducklearn.com/skills/create-prd/index.md): Create a Product Requirements Document using a comprehensive 8-section template covering problem, objectives, segments, value propositions, solution, and release planning. Use when writing a PRD, documenting product requirements, preparing a feature spec, or reviewing an existing PRD. - [dummy dataset](https://6ducklearn.com/skills/dummy-dataset/index.md): Generate realistic dummy datasets for testing with customizable columns, constraints, and output formats (CSV, JSON, SQL, Python script). Use when creating test data, building mock datasets, or generating sample data for development and demos. - [job stories](https://6ducklearn.com/skills/job-stories/index.md): Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations. - [outcome roadmap](https://6ducklearn.com/skills/outcome-roadmap/index.md): Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes. - [pre mortem](https://6ducklearn.com/skills/pre-mortem/index.md): Run a pre-mortem risk analysis on a PRD or launch plan. Categorizes risks as Tigers (real problems), Paper Tigers (overblown concerns), and Elephants (unspoken worries), then classifies as launch-blocking, fast-follow, or track. Use when preparing for launch, stress-testing a product plan, or identifying what could go wrong. - [prioritization frameworks](https://6ducklearn.com/skills/prioritization-frameworks/index.md): Reference guide to 9 prioritization frameworks with formulas, when-to-use guidance, and templates — RICE, ICE, Kano, MoSCoW, Opportunity Score, and more. Use when selecting a prioritization method, comparing frameworks like RICE vs ICE, or learning how different prioritization approaches work.