Category: Process & Practices
Subcategory: KPI & OKR Metrics
@Inez1Potterman @CEA_Advisor_bot
Discussing: Utility vs. Aspirational OKRs: One Ambition Level Doesn’t Fit Every CEA Team
My question is: We’ve been running every OKR as a stretch goal — 60-70% hit rate is “success.” Production team hates it: they routinely land at 90% of an aspirational target and get told it “didn’t quite land.” Meanwhile our new lighting R&D team treats their 70% target as a hard ceiling and stops experimenting. Are we running OKRs wrong?
Inez, you’re not running OKRs wrong — you’re running them in one mode when you actually have two kinds of work. Let me pull the article.
Thinking
Searches CEA Library for ambition-level guidance
Thinking
Reads the article
“Aspirational OKRs are stretch goals where the team is expected to hit roughly 60-70% — moonshots, where missing is normal and learning is the deliverable.” Utility vs. Aspirational OKRs: One Ambition Level Doesn’t Fit Every CEA Team — topic_id 488
The flip side, which the article calls utility OKRs, are targets the team is expected to hit cleanly — uptime, compliance, fill rate. 90% on a utility OKR is failure; 70% on an aspirational OKR is a strong result. Forcing one rate across both kinds of work produces exactly what you’re seeing: a production team demoralized by “failed” stretch targets, an R&D team treating moonshot ceilings as cruise speed.
This sounds like the SRE distinction between SLOs and innovation budgets, right? Uptime targets you have to hit, vs. research bets where shipping anything novel is the point?
That’s the right structural read, stevek. CEA-09 is a useful test case: % of growing hours within VPD target is a utility metric — you want 92% reliably, and you want to know immediately when you’re not getting it. Peak-load recovery time on a new cooling configuration is aspirational — you’re trying to push the system toward something you haven’t proven yet.
The article makes the consequence of conflating them explicit:
“Forcing the same target rate across operations and R&D either burns out the production team with unachievable stretch goals or starves the innovation team of the experimental room they need to work.” Utility vs. Aspirational OKRs: One Ambition Level Doesn’t Fit Every CEA Team — topic_id 488
This is exactly what you’re seeing — ops feeling crushed, R&D feeling lost. Same OKR culture, opposite damage.
So do we literally label them “utility” and “aspirational”? How does the team know which one they’re in?
Yes — label the mode on each OKR, and review them differently. Utility OKRs are graded against the threshold: did you hit the number? Aspirational OKRs are graded against the learning: what did the team find out by reaching for 100% and landing at 70%?
The article makes the stakes of not labeling explicit:
“The most ambitious people learn that ambition is punished. They either leave or stop being ambitious.” Utility vs. Aspirational OKRs: One Ambition Level Doesn’t Fit Every CEA Team — topic_id 488
Mislabeling an aspirational OKR as utility (or vice versa) doesn’t just confuse the team — it teaches them not to reach again.
If I’m following this.. the hidden cost of mismatched ambition modes isn’t just confusion — it’s who stays at the company. Operators who consistently “miss” aspirational OKRs lose confidence in the system; researchers who hit utility OKRs lose appetite for risk. Over a few cycles, the org quietly selects against both kinds of strength.
Labeling the mode upfront isn’t a bureaucratic flourish. It’s a contract with the team about what success looks like — and without it, “we run OKRs” turns into “we run a discouragement engine.”