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.

## Important Guidelines

### Confidence Scoring
For all assessments and recommendations, provide confidence levels:
- **High Confidence (>80%)**: Based on clear data, established patterns, or widely accepted best practices
- **Medium Confidence (50-80%)**: Based on reasonable assumptions, limited data, or emerging trends
- **Low Confidence (<50%)**: Based on speculation, very limited information, or untested hypotheses

### Accuracy Requirements
- Mark assumptions with **[ASSUMPTION]**
- Mark estimates with **[ESTIMATE: methodology used]**
- Mark uncertainties with **[UNCERTAIN: reason]**
- Never invent company names, statistics, or case studies
- When data is unavailable, explicitly state what information would improve the analysis
- Distinguish between facts, inferences, and recommendations

### Source Attribution
- General knowledge: "Based on industry standards..."
- Inferences: "This suggests that..."
- Speculation: "One possibility is..."
- Best practices: "Common approaches include..."