Guide / Anti-patterns
Chapter 4 of 6

The 12 anti-patterns

Each section maps to a diagnostic result in OKR Orca. If the tool flagged one of these patterns in your OKR, the anchor link brings you straight here. Every section follows the same shape: what the pattern is, why it costs you, how to fix it, and a coach's move for working through it with a team.

Anti-patterns are not usually the result of laziness. They are the result of incentives: planning gates that reward the appearance of rigour, cultures that punish stretch targets, or teams that have never seen a good OKR set to copy from. The coach's move in each section is designed to make the team discover the problem themselves, because a rewrite they author sticks longer than one handed to them.

Anti-pattern 1 Output-as-KR
What it is
A Key Result written as a task or deliverable rather than a result. The verb is the tell: launch, migrate, deliver, build, implement, complete. These describe your team's actions, not what changes in the world because of those actions.
Why it weakens the OKR
You can ship the feature and still fail the Objective. Output KRs go green the moment work is done, regardless of impact. They give no signal about whether the effort was worth it and no useful data at end of quarter.
How to fix it
Ask what changes for a real person after the work ships. Write that change. If you cannot name it, the work is not yet tied to an outcome and the Objective probably needs rethinking first.
Coach's move

Ask, then wait: "If you ship that, what changes for a user?"

  • Do not rewrite it for them. Let the silence do the work.
  • If the team answers with another output, ask again: "And what does that change for the user?"
Before / After example
Before
"Launch the new returns portal by end of Q2."
After
"Customers who complete a return without contacting support, from 31% to 55% by end of Q2."
Anti-pattern 2 Activity-as-Outcome
What it is
Similar to Output-as-KR but subtler: the KR sounds result-like but still measures effort rather than effect. Examples include hours of training delivered, number of workshops run, documents published, meetings held.
Why it weakens the OKR
Activity metrics are fully controllable by the team, which makes them easy to hit. They feel safe. But a team can run 10 workshops and change nothing. Measuring activity instead of effect removes the honest feedback loop that OKRs are meant to create.
How to fix it
Identify what behaviour the activity is supposed to change in the people on the receiving end. Measure that behaviour instead. If you cannot observe it, you have a measurement problem that needs solving before committing the KR.
Coach's move

Ask: "After those workshops, what would you expect people to do differently? How would you see it?"

  • Sort proposed KRs into "activity" or "behaviour change" on paper cards. No debate during the sort.
  • When the disagreements surface, those are the real coaching conversations.
Before / After example
Before
"Run 12 onboarding sessions for new merchant partners in Q3."
After
"Merchant partners who place their first live order within 14 days of signing, from 40% to 65% by end of Q3."
Anti-pattern 3 Solution Smuggling
What it is
The Objective contains a specific solution embedded in its phrasing. The team commits to "launching the self-service portal" rather than to "reducing the time customers wait for account changes." The solution appears before the problem is confirmed.
Why it weakens the OKR
If the solution turns out to be the wrong one mid-quarter, the Objective becomes obsolete. Pivoting requires rewriting the OKR rather than simply finding a better path to the same destination. It also closes off discovery work that might have found a faster route.
How to fix it
Write the Objective in terms of the problem or the desired state. Remove all references to specific features, tools, or platforms. The KRs are where you measure whether the solution worked; the Objective is where you name what you want to change.
Coach's move

Ask: "What problem does that solution solve? Can we write the Objective as that problem instead?"

  • Highlight the solution word (portal, engine, platform) and ask them to delete it. What remains is usually close to the real Objective.
  • Ask: "If a different solution gets you there faster in week five, is the OKR still valid?" If yes, you have the right level of abstraction.
Before / After example
Before
"Build a recommendation engine so shoppers discover more relevant products."
After
"Shoppers find products relevant to their intent without relying on search alone."
Anti-pattern 4 Inverse KR
What it is
A Key Result framed as a ceiling rather than a floor: "keep error rate below 2%," "maintain NPS above 40," "ensure zero critical incidents." These measure staying in place, not moving forward. They are health metrics, not growth signals.
Why it weakens the OKR
Inverse KRs score automatically green as long as nothing goes wrong. They reward absence of failure rather than presence of progress. A team can hit every inverse KR and deliver nothing new. Worse, they create anxiety around any experiment that might briefly spike a metric.
How to fix it
Move stability metrics to a health dashboard or service-level agreement. Reserve KRs for forward movement. If maintaining reliability is genuinely the ambition for the quarter, frame it as an improvement over the current baseline rather than a constraint.
Coach's move

Ask: "What would improve by end of quarter, rather than just not get worse?"

  • Draw a two-column table: "health metrics we monitor" vs. "outcomes we are driving." Help them sort their KRs between columns.
  • Health column goes to a dashboard; outcome column becomes the KR set.
Before / After example
Before
"Keep checkout error rate below 1.5% throughout Q2."
After
"Checkout error rate falls from 3.1% to below 1.0% by end of Q2, measured daily via payment gateway logs."
Anti-pattern 5 Vanity Metric
What it is
A number that looks like progress but does not connect to a specific actor doing a specific thing. Page views, registered users, app downloads, social followers: all can grow while the thing you actually care about stays flat or declines.
Why it weakens the OKR
Vanity metrics are easy to inflate and hard to act on. If downloads go up 20%, does that tell you whether the product is solving a real problem? The metric grows when you run ads, when a competitor disappears, or when pricing changes. It gives no useful signal about the team's work.
How to fix it
Apply the actor-action test: who does what? Replace the aggregate number with a rate that names a real person performing a meaningful action. Then apply the inverse test: can you imagine this metric rising while the business gets worse? If yes, find the metric one level deeper.
Coach's move

Ask: "If that number doubles, who is better off, and how would you know?"

  • Run the inverse test aloud together: "Can this metric go up while our users get a worse experience?" If they say yes, keep drilling.
  • Help them name the actor and the action: "Which users, doing what?"
Before / After example
Before
"Grow monthly active users from 50,000 to 75,000 by end of Q3."
After
"Users who publish at least one project in their first 7 days, from 22% to 38% by end of Q3."
Anti-pattern 6 Placeholder
What it is
A KR submitted with unknown numbers: "increase conversion from X% to Y%," "reduce time by TBD%," "owner: (tbc)." The form is correct but the content is absent. A placeholder is a deferred decision dressed as a commitment.
Why it weakens the OKR
Without a real baseline and a real target, there is nothing to track, no mid-point signal, and no honest end-of-quarter verdict. Placeholder KRs pass planning gates without doing planning work. They create the appearance of rigour while skipping it.
How to fix it
If the baseline is genuinely unknown, make instrumenting the metric the KR for this quarter. "Define and instrument the checkout abandonment rate so it can be tracked daily by end of Q1" is a legitimate and honest KR. Do not commit to improvement before you can measure the starting point.
Coach's move

Ask: "What is that number today?" Then wait.

  • If they do not know, suggest making "find out and instrument that metric" the KR for this quarter. That is honest work.
  • Do not let the team submit a KR they cannot score at week two. If they cannot score it now, they will not score it honestly at the end.
Before / After example
Before
"Reduce average resolution time from X hours to Y hours (baseline TBD)."
After
"Average support ticket resolution time falls from 11.4h to 6h by end of Q2, measured weekly via the helpdesk dashboard."
Anti-pattern 7 Lagging-Only
What it is
An OKR set made up entirely of lagging indicators: annual revenue, quarterly churn, year-end NPS. Lagging metrics confirm the final result, but they tell you nothing at week 5 about whether the team is on track.
Why it weakens the OKR
A set of lagging-only KRs gives no actionable signal during the quarter. By the time the numbers move, the window for correcting course has already closed. Teams end up running on hope rather than data mid-cycle.
How to fix it
Pair each lagging indicator with at least one leading indicator that the team can observe weekly. The leading KR gives an early signal; the lagging KR confirms the result. Both belong in the set. Neither replaces the other.
Coach's move

Ask: "Which of these KRs will move in week three? What would you be watching in week three to know you are on track?"

  • If everything only moves at quarter end, the team is flying blind. Help them name one behaviour they can observe weekly as a leading signal.
  • Label which KR is leading and which is lagging. The labels make the pair explicit and easier to track together.
Before / After example
Before
"Reduce annual churn from 18% to 12%." (No leading signal; invisible until year-end.)
After
Add: "Customers who use at least 3 product features within 60 days of sign-up, from 29% to 50% by Q3." (Leading indicator the team can track weekly.)
Anti-pattern 8 Timebox Missing
What it is
An Objective or Key Result with no explicit date or quarter reference. "Improve checkout speed" or "increase trial conversion" with no timeframe attached. The ambition is present but the deadline is absent.
Why it weakens the OKR
Without a date, there is no review moment. Teams defer the honest conversation about progress because there is always "more time." Work expands to fill the absence of a deadline. The OKR becomes a permanent aspiration rather than a quarterly commitment.
How to fix it
Add an explicit quarter or date to the Objective. "By end of Q3 2026" is unambiguous. "This year" is partial and scores lower. The date creates the accountability moment that the rest of the OKR process depends on.
Coach's move

Ask: "When would we check whether this landed? What date would that be?"

  • Write the date on a card and place it next to the OKR. The physical act of attaching a date makes the commitment real.
  • If the team resists ("it depends"), acknowledge the uncertainty and then name the latest plausible date anyway.
Before / After example
Before
"New sellers complete their first successful listing on the platform."
After
"By end of Q2 2026, new sellers complete their first successful listing on the platform within 48 hours of account creation."
Anti-pattern 9 Ambition Gap
What it is
A target set at a level the team would reach even without the OKR. Growth of 2% on a metric that grew 8% last quarter without any focused effort. The OKR exists but is not driving anything.
Why it weakens the OKR
OKRs are a prioritisation tool. If the target is comfortable, the team has no reason to make hard trade-offs or take risks. The OKR will turn green without any of the decisions OKRs are supposed to force. Planning becomes box-ticking.
How to fix it
Apply the calibration question: if the team hits 70% of this target, would leadership be satisfied? If yes, the target is probably too low. Raise it until hitting 70% would require real effort and resource decisions. Then the OKR is doing its job.
Coach's move

Ask: "If the team hits 70% of this target, is that worth celebrating? What would it take to make 70% feel like a real stretch?"

  • Look at the trend without any focused effort. If the target is already in the trajectory, the OKR is not deciding anything.
  • Ask what would need to change for the team to hit a number that does require new decisions. That is the right target.
Before / After example
Before
"Grow trial-to-paid conversion from 12% to 13% by end of Q3." (Trend already points there.)
After
"Grow trial-to-paid conversion from 12% to 20% by end of Q3." (Requires rethinking the trial experience, not just tweaking copy.)
Anti-pattern 10 Planning Theatre
What it is
An OKR set that looks credible on paper but was never intended to drive decisions. The targets are achievable regardless of what the team does. The Objective is vague enough to be claimed at end of quarter no matter what shipped.
Why it weakens the OKR
Planning theatre satisfies the process without fulfilling its purpose. Teams learn that OKRs are a reporting ritual rather than a decision tool. Cynicism accumulates. Future OKR cycles produce even less honest sets because everyone has learned that honesty is not rewarded.
How to fix it
Test the OKR against one question: if this KR turns red at mid-point, does the team stop and change direction? If the answer is "we would notice but carry on," the KR is not load-bearing. Replace it with one the team would actually respond to.
Coach's move

Ask: "If this KR turns red at week six, what exactly does the team do differently?"

  • If the answer is "not much," that KR is not load-bearing. Ask them to replace it with one they would actually respond to.
  • Rehearse grading mid-cycle as if today were the last day. The discomfort that surfaces is the real content.
Before / After example
Before
"Strengthen the product team's collaboration and delivery quality." (Unfalsifiable, no signal.)
After
"Feature cycle time (idea to production) falls from 34 days to 18 days by end of Q3, measured from ticket creation to first customer use."
Anti-pattern 11 Alignment Gap
What it is
An OKR set with no stated connection to anything above it. No parent Objective, no strategy reference, no company-level priority the team can point to. The team is working hard on something, but it is unclear whether the organisation agreed that this is the right something.
Why it weakens the OKR
Without an alignment statement, the OKR cannot be reviewed against strategy. Well-intentioned local optimisation can actively undermine company-level priorities. The alignment gap is invisible at team level and only becomes obvious when multiple teams are pointed in different directions.
How to fix it
Add a one-line alignment statement to the OKR set: "Contributes to company priority: [name it]." Even if the connection feels obvious, stating it makes the OKR reviewable and creates an audit trail for strategy decisions made during planning.
Coach's move

Ask: "Which company or area-level priority does this connect to? Can you say it in one line?"

  • If the team cannot name the parent priority, that is a signal worth surfacing before the OKR is locked. Alignment gaps are cheaper to fix in planning than mid-quarter.
  • If no company-level OKR exists to link to, note that as a dependency. The absence is information.
Before / After example
Before
OKR set with no parent reference. Reader cannot tell whether this is a company priority or a team passion project.
After
Add header line: "Contributes to company OKR: Become the go-to platform for independent retailers in our category."
Anti-pattern 12 Too-Many-KRs
What it is
An OKR set with six, eight, or more Key Results per Objective. Every initiative gets its own KR. The set becomes a project plan in disguise: exhaustive rather than focused.
Why it weakens the OKR
When everything is a KR, nothing is. Focus is the first reason OKRs exist, and a ten-item KR list signals that the team has not made the hard trade-offs that focus requires. In practice, two or three KRs carry the real signal and the rest are coverage metrics that rarely trigger any action.
How to fix it
Aim for two to four Key Results per Objective. For each candidate KR, ask: if this turns red mid-quarter, does the team drop everything to investigate? If the answer is no, it belongs in a project tracker, not the OKR set. Cut until only the load-bearing KRs remain.
Coach's move

Ask: "Which two would you keep if you could only keep two?"

  • The ones they choose quickly are the real KRs. The ones they agonise over are probably coverage metrics that belong in a backlog.
  • Name the cut explicitly: "The others go to your project tracker. They are still tracked, just not in the OKR set."
Before / After example
Before
8 KRs covering signup, activation, feature adoption, support volume, NPS, documentation coverage, team training, and a process audit.
After
3 KRs: activation rate (leading), 90-day retention (lagging), and support contact rate (health signal). The rest move to a team backlog.
Spotted one of these in your OKR?
Paste it into Diagnose and get a rubric score with a pattern breakdown in 60 seconds.
Diagnose →