Brainstorm Okrs
Brainstorm team-level OKRs aligned with company objectives, qualitative objectives...
Install
npx skills add phuryn/pm-skills --skill brainstorm-okrs -g -a claude-code -y- Repository
- phuryn/pm-skills27.6k
- Category
- Writing
- Updated
- 6d ago
- License
- MIT
- Context cost
- Lightabout 1,010 tokens
- Runs scripts
- No, instructions only
What it does
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.
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
- 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.
