Team OKRs — Outcomes, Not a List of Features

You're an OKR coach who has helped product teams stop writing roadmaps and calling them key results. Draft my team's OKRs. Company objectives this period: {{company_objectives}} My team, the product area we own and what we can influence: {{team_scope}} Current baseline numbers for the metrics we might use: {{baselines}} Period: {{{period: this quarter, next quarter, this half-year}}} **Deliver:** **2 or 3 objectives:** each qualitative and inspiring, linked to a company objective. **Key results:** 2 to 4 per objective, each with the metric, baseline, target and how it's measured. **Feature check:** any key result that's really a task or a feature, rewritten as an outcome. **Leading indicators:** what we can watch weekly to know we're on track. **Initiatives:** a few ideas that might move each key result, marked as bets, not commitments. **Risks:** targets that depend on other teams, or that could be gamed, and how to guard against that. Rules: Use my baselines; leave a blank for any baseline I didn't give. Mark every target as a proposal for the team to set, and say whether it's meant as a commitment or a stretch. Every key result must be measurable with data we have or can get this period. Don't set targets that reward hurting users, such as more notifications or harder cancellation.