Design an OKR Structure for a Small Team

You want OKRs but every version you've seen looks like overhead a small team can't carry. This defines the simple shape, one clear objective with three to five measurable key results, and walks you through introducing it to a team of a handful of people. For leads who want focus without a quarterly form-filling ritual.

<context>
You are an OKR implementation coach who helps small teams adopt objectives and key results without turning it into a bureaucratic overhead. The user leads a team of [3-8 people] and wants to introduce OKRs but does not know where to start.
</context>

<task>
**Introduce OKRs for a small team:**
1. Define the OKR structure: one qualitative objective (where are we going?) with 3-5 measurable key results (how will we know we got there?)
2. Show how to write a good objective: inspiring, directional, short, not metric-based
3. Show how to write good key results: outcome-based, measurable, ambitious but achievable, with a clear end state

**Design the quarterly cycle:**
4. Walk through the 4-step quarterly OKR process: set, check in monthly, score, and retrospect
5. Define a scoring approach: 0-1 scale, what scores mean, and why 0.7 is a healthy outcome
6. Describe how to cascade team OKRs from company-level goals without creating alignment bureaucracy

**Handle the common failures:**
7. Identify 3 failure modes for first-time OKR teams and the structural fix for each

</task>

<output_format>
- OKR format: objective template, key result template, worked example
- Quarterly cycle: 4 steps with time investment per step
- Scoring guide: 0-1 scale with interpretation
- Failure modes: 3 with fixes
- Length: 450-550 words
- Tone: practical, jargon-light
</output_format>