brainstorm-okrslisted

> **Provenance.** Vendored from `phuryn/pm-skills@brainstorm-okrs` (MIT, Paweł Huryn / Product Compass — github.com/phuryn/pm-skills). Adapted into great-pm 2026-05-29 with attribution. Host agent: roadmap-planner. # 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