OKR Drafting With Leading Indicators
Drafts ambitious-but-measurable product OKRs with outcome key results, leading indicators, and anti-sandbagging checks.
Prompt
ROLE: You are a product leader who writes OKRs that drive focus instead of becoming a task list. CONTEXT: Time period: [QUARTER]. Company strategy this period: [STRATEGY]. Team's domain: [TEAM_DOMAIN]. Current baseline metrics: [BASELINES]. Known constraints: [CONSTRAINTS]. TASK: 1. Draft 1-2 Objectives: qualitative, inspirational, and tied to the company strategy. 2. For each Objective, write 3-4 Key Results that are outcomes (metric moves), each with a baseline, target, and confidence (0-1). 3. For each KR, name a leading indicator the team can watch weekly to know if it's on track. 4. Audit your own draft: flag any KR that is actually a task/output, any that is sandbagged (too easy), and any that is unmeasurable. 5. List the 3-5 initiatives most likely to move these KRs (clearly separated as bets, not commitments). OUTPUT FORMAT: Objectives and KRs in a structured block, a Leading Indicators table, a Self-audit note, and an Initiatives list. CONSTRAINTS: KRs measure outcomes, never 'launch X.' Targets should imply ~70% confidence (stretch, not safe). Call out any KR you cannot make measurable.
How to use this prompt
- 1
Copy the prompt above and paste it into ChatGPT, Claude, or Gemini — or open it in the visual Studio to edit each part on a canvas and run it with your own key.
- 2
Replace any bracketed placeholders with your specifics. The more concrete your context and constraints, the sharper the result — see the 5-part prompt structure.
- 3
Run it, then refine. Ask the model to critique and improve its own answer with self-critique prompting.
Techniques in this prompt
Assigns the model an expert persona so it adopts the right vocabulary, depth, and standards for the task.
Learn this techniqueRecommended models
Build on this prompt
Open it in the visual Studio to wire it into a full workflow with your own API key — or learn the craft behind prompts like this.
More in Product Management
Pressure-Tested Product Requirements Document
Drafts a complete, engineering-ready PRD with problem framing, scope boundaries, success metrics, and explicit non-goals.
RICE Prioritization Scoring Engine
Scores and ranks a backlog using RICE with transparent assumptions, sensitivity flags, and a defensible recommendation.
Jobs-To-Be-Done Interview Synthesis
Turns raw user interview notes into JTBD job statements, forces of progress, and prioritized opportunity areas.
Quarterly Product Roadmap Narrative
Builds an outcome-driven quarterly roadmap organized by themes and bets, with confidence levels and dependencies surfaced.