How to Handle an Underperforming OKR

Time required ~60 min Plus follow-up actions

Frequency As needed Run per flagged red KR

Who's involved KR owner + manager + contributors for diagnosis

Output Recovery decision Fix, adjust, or retire

Before you start

You need at least 3–4 weeks of weekly check-in data on the KR — without that, you can't tell drift from noise. Also: the KR owner should be in the room. Diagnosing a KR without its owner present is performance review theatre, not problem-solving.

The 6 steps

6 steps · sequential

~5 min·Triggered by weekly check-in

Spot underperforming OKRs early

Identify issues before they derail the cycle. A KR stuck at the same percentage for three weeks is a signal, not noise.

Use Red/Yellow/Green status updates in weekly check-ins
Track confidence ratings (High/Medium/Low)
Watch for Key Results stuck at the same percentage for weeks
Encourage owners to raise concerns proactively

DecisionIf a KR is yellow for 2 weeks running, treat it as red. Yellow that doesn't move is red wearing a disguise.

~20 min·Diagnostic session

Diagnose the root cause

Understand why progress is lagging. Treating symptoms means the same KR will flag red next quarter for the same reason.

Ask the 5 Whys to drill into underlying issues
Separate internal blockers (resourcing, prioritization) from external blockers (market, customer, vendor)
Check for unrealistic goal-setting or unclear ownership
Involve contributors for a 360° view of the problem

Done whenYou can write the root cause in one sentence. If it takes a paragraph, you haven't found it yet.

~15 min·Same session

Reassess the Key Result

Decide whether to adapt, adjust, or stay the course. Three options, pick one — don't leave it in limbo.

If the KR is still achievable, create a recovery plan
If it's unrealistic, adjust the target or scope transparently
If priorities have shifted, consider retiring the KR (see Mid-Quarter Review)
Document the rationale for any changes

DecisionThree paths: recover (build a plan), adjust (lower the target), or retire (priorities changed). The wrong answer is "let's see how it goes" — that's how quarters die.

~15 min·If "recover" was the decision

Build a recovery plan

Create a clear, time-bound path to improvement. "Try harder" is not a recovery plan.

Define specific catch-up actions with deadlines
Reallocate resources to support the struggling KR
Assign a blocker owner to remove obstacles
Add mid-week progress check-ins for critical KRs

Done whenThe plan has named actions, named owners, and dated deadlines for the next 2 weeks. Not 13.

~10 min·Within 24 hours

Communicate adjustments

Maintain transparency and trust across teams. Silently editing KRs and hoping nobody notices is the fastest way to kill the OKR culture.

Share updates in weekly check-ins or all-hands
Clearly mark adjusted KRs in dashboards
Explain why changes were made to avoid confusion
Celebrate improvements, even partial recoveries

End of cycle·Feeds into the retro

Capture learnings in the retrospective

Prevent recurring issues in future cycles. If the same root cause shows up two cycles in a row, it's a systemic issue.

Discuss what caused underperformance in the retrospective
Identify systemic issues (overcommitment, misaligned metrics, lack of ownership)
Update your OKR playbook with new guardrails
Use learnings in the next planning session

What you'll have when you're done

Outputs of this workflow

A one-sentence root cause for why the KR is underperforming
A clear decision — recover, adjust, or retire — documented and communicated
A recovery plan (if applicable) with actions, owners, and 2-week deadlines
Mid-week check-ins scheduled for critical KRs until status changes
A retrospective input — what caused this, what guardrail prevents it next cycle

Spot at-risk OKRs early inside OKRs Tool.

AI-powered risk detection, weekly confidence trends, and Slack alerts when a KR is stuck — so you find drifting OKRs in week 3, not week 9. Free for up to 5 users.

Start free