pm-okrs-kpis

Write and review OKRs, KPIs, and North Star Metrics derived from product strategy.

12|2|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-okrs-kpis-uxcel-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pm-okrs-kpis
Source: https://github.com/Uxcel-Lab/product-skills/tree/main/pm/deliverables/okrs-kpis
Command: npx skills add https://github.com/Uxcel-Lab/product-skills --skill pm-okrs-kpis-uxcel-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams routinely get goal sets that look tidy but misdirect work: objectives invented without strategy, key results that are activities in disguise, and targets that can be gamed. This Skill gates goal-writing on strategic context and enforces outcome-based, falsifiable metrics. ## Core Features & Use Cases - Context-gated goal writing: Establishes strategy, level, team size, cycle, and available data before drafting any OKR, and flags when no strategy exists. - Outcome-based key results: Enforces baseline-to-target numbers with units and timeframes, one focus objective per team per quarter, and a leading-plus-lagging metric mix. - Gaming guardrails and validation: Pairs aggressive targets with guardrail metrics and hands the finished goal set to a metric-validity audit lens. - Use Case: A product lead asks for Q3 OKRs for a growth squad. The Skill first asks what strategic priority the goals serve, then drafts one focus objective with 2-4 falsifiable KRs, each with a baseline, target, and guardrail metric. ## Quick Start Ask the assistant to write quarterly OKRs for your team based on your current product strategy, including baselines, targets, and guardrail metrics for each key result.

Frequently Asked Questions about pm-okrs-kpis

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write OKRs for a product team?▼

Start from an explicit product strategy, then define one focus objective per team per quarter with 2-4 key results. Each key result needs a baseline, target, unit, and timeframe, and must measure an outcome rather than a shipped deliverable or activity.

What is the difference between OKRs and KPIs?▼

KPIs are ongoing health signals like churn or DAU/MAU that persist across cycles, while OKRs are the quarterly push for change. A KPI can serve as a key result when an objective targets it, but a KPI dashboard is not an OKR set.

How do I choose a North Star Metric for my product?▼

Propose 2-3 candidates that unite customer value and business success, like time listening for Spotify or nights booked for Airbnb. Pressure-test the value-exchange logic before adopting, since a North Star should hold for years and a wrong one misguides strategy.

How do I stop teams from gaming their OKR targets?▼

Ask how someone could hit each number while making the product worse, then pair aggressive targets with a guardrail metric. For example, pair a session-duration target with a check that task completion time and support contacts stay flat.

When should a small team avoid full OKRs?▼

A small squad is often better served by a simpler levers framing: identify which metrics move the North Star and which is the bottleneck. A squad typically needs only 1-2 key results per objective and minimal planning ceremony.

Is 70 percent OKR achievement a failure?▼

No, roughly 70 percent achievement is healthy when stretch is designed into the goals. Separate aspirational OKRs from committed deliverables so a miss provides information rather than signaling betrayal.