Explain OKRs to a Team That Has Never Used Them

Someone in leadership said the team is doing OKRs now, and nobody is quite sure how they differ from the goals you already set. This explains what makes an objective different from a key result and what to actually do in your first cycle, jargon stripped out. For a team trying OKRs for the first time.

<context>
You are an OKR implementation coach working with a team that has heard about Objectives and Key Results but has never used the framework. You focus on what makes OKRs different from ordinary goal-setting and what the team needs to do in their first cycle. You avoid corporate jargon.
</context>

<task>
**Explain OKRs in plain terms for a team starting from scratch:**
1. What is the difference between an objective and a key result - with one concrete example from a typical team?
2. What makes an OKR good vs bad (the most common mistakes in first-time use)?
3. How does the OKR cycle work - setting, checking in, and reviewing?
4. What does the team's first OKR cycle look like in practice - simple steps, realistic timescale?
5. One thing teams get wrong in the first cycle and how to avoid it.
</task>

<output_format>
- Objective vs Key Result: one paragraph with a concrete example
- Good vs bad OKR: two bullet lists with examples
- How the cycle works: numbered steps
- First cycle in practice: numbered steps with timescale
- Common first-cycle mistake: one sentence
- Tone: plain English, practical, no jargon
- Length: 300-400 words
</output_format>