Most organisations that implement OKRs don't actually use them. They write them, publish them, review them quarterly, and then continue making decisions exactly as they always have. The OKRs sit in a spreadsheet or a tool. The work happens elsewhere. Nothing changes except the administrative overhead.
Christina Wodtke wrote Radical Focus to explain why this happens - and how to stop it. Written as a business fable, it is the most practical and honest account of OKR implementation available. Wodtke doesn't describe OKRs as they are supposed to work. She describes them as they actually fail, and what it takes to make them work instead.
If you have ever rolled out OKRs and found yourself wondering why nothing changed, this is the book you needed first.
The OKR framework is simple. One Objective - an inspiring, qualitative direction. Two to four Key Results - measurable outcomes that tell you whether you've arrived. Set quarterly. Checked weekly. Adjusted based on evidence.
The simplicity is deceptive. In practice, organisations make the same mistakes reliably: too many objectives, Key Results that are actually tasks, no weekly cadence, no meaningful accountability, and leaders who treat OKRs as a communications exercise rather than a focus mechanism. Wodtke dissects each of these failure modes with clarity and candour.
What makes Radical Focus important for engineering and product organisations is its insistence that OKRs are not about tracking work - they are about choosing what not to do. Focus is the point. Radical focus is the discipline of holding that focus under pressure, when the inbound is relentless and the temptation to spread effort is constant.
The most common OKR mistake is treating Key Results as tasks. "Launch the feature" is not a Key Result - it is a task. "Increase user activation rate from 34% to 60%" is a Key Result. The distinction matters because tasks measure effort and Key Results measure outcomes. Effort without outcome is not success.
Wodtke frames the OKR as a quarterly bet: we believe that if we achieve these outcomes, we will make meaningful progress towards our objective. That framing forces honesty. Is this Key Result actually the outcome we think matters? Or is it just the thing we planned to do?
Review your current Key Results. For each one, ask: is this a task (something we will do) or an outcome (something that will change in the world as a result)? Rewrite every task as the outcome it is intended to produce.
Wodtke is insistent on one ritual: the Monday check-in. Every week, the team gathers briefly to answer two questions - what is your confidence level (0–10) that you will hit each Key Result by the end of the quarter, and what are the top priorities this week that will move you towards them?
The confidence score is the mechanism. If it drops, something has changed. If it stays flat for weeks, something is wrong. If it climbs without the work actually changing, someone is being optimistic rather than honest. The score creates a weekly conversation about reality rather than aspiration.
Most organisations skip this ritual entirely, or run it monthly, or make it a reporting exercise rather than a thinking exercise. When they do, OKRs stop working - because the whole system depends on the weekly discipline of honest calibration.
Implement a 15-minute Monday OKR check-in this quarter. Three questions: confidence score for each Key Result, what changed last week, and what one thing will you do this week that most moves the needle. Keep it short and honest.
Wodtke introduces a concept that most OKR guides omit: health metrics. These are the numbers you cannot allow to degrade while you chase your objective. Retention. Revenue. System reliability. Team morale. The things that would break the business if they fell - but which don't belong as OKR Key Results because they are baseline requirements, not improvement targets.
The distinction matters because teams often damage existing performance in the pursuit of ambitious objectives. Health metrics are the circuit breakers - the signals that tell you the pursuit is costing too much.
Before finalising your OKRs, explicitly define your health metrics for the quarter. What numbers must not fall? Who owns monitoring them? What is the threshold at which you would pause or revisit the OKR?
The objective must be singular. Not three things you care equally about. One thing - the most important thing for this quarter. Wodtke is unambiguous: if you have three objectives, you have none. You have a prioritised list of things you are spreading your attention across.
This is where most leadership teams struggle. Everything feels important. The pressure to include more is relentless. But the power of OKRs is in the constraint they create. When there is one objective, every decision about where to invest time has a test: does this move the key results? If not, it waits.
Run a single-objective exercise with your team. Ask everyone independently to write down what they think the single most important outcome for the next quarter is. Compare the answers. If they differ, you have a prioritisation problem that no amount of OKR formatting will resolve.
Wodtke's fable illustrates this clearly: OKRs require psychological safety to function. If teams are afraid to report a declining confidence score, they won't. If leaders treat a missed OKR as a performance failure rather than a learning opportunity, teams will set safe OKRs. If the weekly check-in becomes a status update theatre, people will stop being honest.
OKRs are an information system. They only work if they surface accurate information. Accurate information only flows in cultures where bad news is welcomed rather than punished.
After your next OKR review, deliberately celebrate a missed Key Result where the team was honest about why it was missed and what they learned. Make it visible. This single act does more for OKR culture than any process documentation.
If you cannot describe your team's single most important outcome for this quarter in one sentence, you do not have focus - you have noise with a spreadsheet attached.
Weekly confidence scores are only useful if they are honest. When was the last time someone on your team reported a confidence score going down? If the answer is "never", you have a culture problem, not an OKR problem.
The teams that achieve their OKRs rarely do so by doing more. They do so by ruthlessly protecting focus and being willing to disappoint on the things that don't matter this quarter.
An OKR that everyone achieves every quarter is not an OKR. It is a target that has been reverse-engineered from what you were planning to do anyway.
The fable format of Radical Focus is deliberate. Wodtke knew that principles alone don't change behaviour. Watching a team fail and recover - recognisably, uncomfortably - does.
Write a single objective for the next quarter. Not a vision statement. Not a theme. One outcome that, if achieved, would make the quarter a clear success. If your team cannot agree, that disagreement is the most important thing to resolve.
Audit your current Key Results against the outcome test. Strike through any that are tasks. Rewrite them as measurable outcomes. If you can't identify the outcome, question whether it belongs in the OKR at all.
Define your health metrics before you finalise your OKRs. Write them down. Assign owners. Set the floor below which you would pause pursuit of the objective.
Schedule a 15-minute Monday check-in for the full quarter. Block it now. Make it non-negotiable. Keep it short, honest, and focused on the confidence score and the single most important thing this week.
Read the fable slowly. The protagonist's mistakes are not abstract. They are the mistakes your team is making right now. The recognition is useful.
"An OKR is a contract you make with your future self. It says: this is what I believe matters, and I am willing to make trade-offs to achieve it."
- Christina Wodtke