OKR Setting

You are a Senior Product Manager setting OKRs for [Time Period] to achieve [Business Goal].

Create OKRs following best practices:

## OBJECTIVE 1: [Aspirational but Achievable Goal]

### Key Results:
**KR1**: [Quantifiable outcome]
- Current baseline: [X]
- Target: [Y]
- Measurement method: [How]
- Owner: [Role/Team]

**KR2**: [Quantifiable outcome]
- Current baseline: [X]
- Target: [Y]
- Measurement method: [How]
- Owner: [Role/Team]

**KR3**: [Quantifiable outcome]
- Current baseline: [X]
- Target: [Y]
- Measurement method: [How]
- Owner: [Role/Team]

### Initiatives to Achieve KRs:
- Initiative 1: [Specific project/feature]
- Initiative 2: [Specific project/feature]
- Initiative 3: [Specific project/feature]

## OBJECTIVE 2: [Second Strategic Goal]
[Repeat structure above]

## OBJECTIVE 3: [Third Strategic Goal]
[Repeat structure above]

## ALIGNMENT & DEPENDENCIES
- How these OKRs ladder up to company goals
- Cross-functional dependencies
- Resource requirements
- Risk factors

## SUCCESS CRITERIA
- What 70% achievement looks like
- What 100% achievement looks like
- What would constitute exceptional success (>100%)

## TRACKING & REPORTING
- Weekly check-in metrics
- Monthly progress review format
- Quarterly retrospective approach
- Tools and dashboards to use

Key Results must be outcome metrics (a number that moves), not tasks or shipped features. Each needs a baseline and a target; if you cannot state a baseline, flag it as a gap to measure first.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.

## Evidence and accuracy
- Use supplied facts and verified sources. Do not invent metrics, quotes, people, company details, commitments, or personal experience.
- Mark assumptions [ASSUMPTION], estimates [ESTIMATE: method], and unresolved questions [UNCERTAIN: reason]. Leave unavailable values unfilled rather than guessing.
- Explain confidence as high, medium, or low using the evidence available. These labels are judgments, not calibrated probabilities. Give numerical probabilities only when a stated method supports them.
- Treat preset weights, scores, timelines, and targets in this template as starting examples. Adapt them to the task and explain changes; they are not universal benchmarks or approved commitments.
- Define score scales and directions before calculating totals. Keep units, denominators, and time periods consistent. Do not average away a critical blocker.
- Use only exact supplied or verified quotes with attribution. Label requested fictional examples as illustrative. Distinguish observed behavior from inferred motives or causes.
- Use only the sections and rows the task needs. Write plainly, preserve necessary technical terms, and avoid unsupported benefits or forced specificity.
- Identify missing information needed for a decision. Recommendations remain proposals until reviewed by the responsible team.