OKR Mistake: Sandbagging Goals
Sandbagging is setting easily hit Key Results so scores look perfect. It thrives when OKR scores are tied tightly to bonuses or punishment. Fix with stretch vs committed labels, fair scoring culture, and leadership that rewards ambition and honesty.
Overview
Sandbagging destroys the learning value of OKRs and makes performance management less accurate, not more.
Why it matters
If every KR is 1.0, you are not stretching — you are forecasting conservatively under a different name.
Examples
Team hits 100% every quarter for three years — goals were too safe.
Best practices
- Separate compensation from stretch OKR scores.
- Celebrate strong 0.7 stretch outcomes.
- Use committed KRs for operational must-hit metrics.
Common mistakes
Guarantees next cycle sandbagging.
Coach ambition; keep pay systems separate.
Frequently asked questions
How do I detect sandbagging?
Look for permanent 1.0 scores, low variance, and KRs that match already-committed forecasts without upside.