Utility vs. Aspirational OKRs: One Ambition Level Doesn’t Fit Every CEA Team
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 OKRs are predictable goals where the team is expected to hit 80-85% — the bar for production, customer commitments, compliance. Different parts of a CEA facility need different ambition levels. 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.
Subjects: team-dynamics-metrics · operations-risk
The two modes, explained simply
The OKR literature distinguishes two ambition levels:
Aspirational mode — moonshots. Aim for 10×. Achieving 5× is a successful failure. Achieving 1× is timid. The team is expected to fall short, and the falling-short is where learning happens. The famous example: aim for 10,000 daily users, hit 5,000 — labeled a “failure” but a better outcome than a safe team aiming for 1,100 and hitting it (“success”).
Utility mode — predictable improvement. Aim for an achievable target with high confidence. Use OKRs for focus, shared goals, communication, and medium-term planning, even without 10× ambition. Hitting 80-85% is the expectation. The metric still does its job — focusing the team, aligning priorities, communicating progress — but ambition is calibrated to the team’s reality.
Both modes are legitimate. Both deliver real value. They are not the same, and applying the wrong mode to the wrong team produces predictable failures.
Why CEA needs both
A CEA facility is not a single team. It’s a collection of teams with very different relationships to risk, customers, capital, and biology.
Production operations has customer commitments. A grocer expecting 200 cases of romaine on Thursday will not be impressed by “we aimed high and only hit 70%.” Production needs to be predictable, because the people downstream of production are counting on it. A 60% achievement on production OKRs means the facility is shipping less than promised.
Robotics and R&D is experimentation. Most experiments fail. The team aiming for 95% harvest automation might achieve 85% — a disappointment against the target, and a transformative result against last quarter’s 60%. R&D needs ambitious targets to do its job at all; a robotics team given utility OKRs (“improve uptime by 1% this quarter”) will deliver exactly that and stop, when an aspirational target (“achieve 95% uptime”) would have produced a 6× larger jump even falling short.
Energy management sits in the middle. Operational discipline blends with optimization opportunity. Cost reduction targets can be aspirational; reliability targets need to be predictable.
Finance and HR lean predictable. Cash flow targets, hiring goals, compliance — these are commitments to the business, not experimental hypotheses. Utility mode is the right fit.
Recommended target rates capture this distribution:
- Production operations: 80-85% achievement.
- R&D / robotics: 60-70% achievement.
- Energy management: 75% achievement (mixed).
- Finance / HR: 85% achievement.
These are not rules — they’re guidance. The principle underneath them is: match the OKR ambition to the team’s relationship with predictability and experimentation.
The cognitive dissonance trap
The most common failure mode when aspirational OKRs meet a customer-facing operation is what’s been called cognitive dissonance: the team produces a result that, by every business measure, is excellent — and the OKR labels it “failed.”
A worked example: the operations team’s aspirational OKR sets cost per kilogram from $12 down to $4 — a 67% reduction, a 3× improvement. They land at $7/kg. By the OKR rubric, they’ve failed (missed the $4 target). By the business reality, they’ve created a massive improvement and an industry-leading cost structure. The team that “failed” delivered enormous value. The team-down-the-hall that set a utility target of $10/kg and hit $9.80 “succeeded” while delivering a fraction of the value.
This dissonance is worse than just confusing. Repeated, it teaches the team that “success” and “value created” are unrelated. The most ambitious people learn that ambition is punished. They either leave or stop being ambitious.
The fix is partly technical and partly linguistic. Technically, separate aspirational tracking from utility tracking — give R&D teams aspirational OKRs and acknowledge that 60-70% achievement is the design point. Linguistically, change the phrasing: “we achieved 5× improvement against our 10× target — exceptional progress against an ambitious goal” rather than “we missed the target.”
The 1-10 likelihood scale — making risk explicit
A practical tool: rate each OKR on a 1-10 likelihood scale.
- 1-2: moonshot. Highly unlikely (sub-30%) to hit the stated number; the value is in falling short.
- 5-6: balanced. Roughly 50/50.
- 7-8: achievable. High confidence (75-85%) of hitting the number.
- 9-10: safe. Almost certain to hit; little stretch.
Applying the scale forces honest conversations between teams and stakeholders. Two examples:
Stakeholder mismatch. Operations manager proposes “achieve 99.9% crop quality” (currently 94%). The CEO is alarmed: “If you’re only expected to hit 70% of OKRs, that means I should plan on 96.5% quality.” The likelihood scale resolves it. 99.9% rates a “2” (moonshot). 97% rates a “7” (achievable). 95% rates a “9” (safe). The CEO and the operations manager negotiate to 97% — aspirational enough to drive real improvement, achievable enough that the CEO can plan around it.
Conflicting executive guidance. The CTO says “aim for 100% automation — moonshot!” The CFO says “we need predictable ROI.” The team is paralyzed. The likelihood scale gives them a tool: 100% = “3,” 85% = “8.” The two executives can sit down and align on a “6” — 90% — that’s aspirational enough for the CTO and predictable enough for the CFO.
The scale isn’t a precise instrument. It’s a way of making implicit risk profiles explicit so that team-stakeholder negotiations can happen on shared ground.
A common leadership inconsistency, named
Watch for a pattern: leaders who say they want aspirational OKRs but react to misses as failures.
The CEO’s Monday all-hands speech: “Set aspirational OKRs! I accept failure! Aim high!” The CEO’s Friday review of quarterly numbers: “Why are we planning to fail? Why is your projection only 70%?” The team learns from Friday, not from Monday.
The diagnosis is usually that the leader intellectually accepts aspiration but emotionally reacts to “failure.” The fix is to either (a) genuinely internalize aspirational practice and stop reacting to misses, or (b) be honest that the organization is in utility mode and stop pretending otherwise. Either is workable. The mismatch between speech and reaction is what kills the practice.
How utility-mode OKRs still earn their keep
A counterintuitive note: utility-mode OKRs are not a degraded form of aspirational OKRs. They deliver real value even at 80-85% achievement, because the value of OKRs is not just in the ambition.
Even modest utility-mode OKRs deliver:
- Outcome orientation. “Reduce crop loss to 3%” still focuses the team on outcomes, not activities.
- Prioritization. Choosing three improvements out of twenty options is itself work.
- Focus. De-prioritizing seventeen things is the value, even if the chosen three aren’t moonshots.
- Shared goals. The whole team is aligned on what matters.
- Cross-team communication. Other teams can read the OKRs and know your priorities.
- Medium-term planning. A 12-week view between sprint and annual.
- Clarity. “3% crop loss” is clearer than “improve quality.”
For most CEA facilities — especially capital-constrained ones, especially in the first year of OKR practice, especially where the foundational culture isn’t yet supportive of ambition — utility mode is the right starting point. Build OKR competence in utility mode, prove the practice delivers, develop the psychological safety that aspirational mode requires, then graduate to aspirational targets where the team can support them.
What to do this quarter
- Match ambition to team reality. Production operations: 80-85%. R&D and robotics: 60-70%. Energy: ~75%. Finance and HR: ~85%. These are starting points, not rules.
- Apply the 1-10 scale to every OKR. Each KR gets a likelihood rating before the quarter starts. The rating is the team’s honest forecast, not its commitment.
- Negotiate with stakeholders using the scale. When a stakeholder demands certainty and the team wants aspiration, use the scale to find a common point. “We can commit to a 7-rated target; here’s what an aspirational 3-rated target would look like.”
- Watch the language at quarter-end. Aspirational misses get talked about as “we achieved 5× improvement against an ambitious goal,” not “we failed to hit our number.” Utility misses are something different — a real shortfall against a committed target — and should be treated accordingly.
- Don’t graduate to aspirational mode prematurely. A facility without psychological safety, without resources, and without a track record of OKR delivery cannot run aspirational targets without producing demoralization. Build in utility mode first; earn the right to aspirational mode by proving the practice works.
The single-mode mistake — running aspirational OKRs across a facility that includes customer-facing production, or running utility OKRs across an R&D function that needs room to fail — is one of the most consistent OKR failures in practice. Different teams, different ambitions, different success rates. The OKR system supports both modes; the discipline is using each in the right place.
Related articles
- Why OKRs Must Never Be Tied to Compensation
- Test-First Management: OKRs as Acceptance Tests for the Quarter
- Adapt, Don’t Copy: Why CEA Can’t Just Run Silicon Valley’s OKR Playbook