Xodiac

09/01/2026

Your OKR board is filled with completed goals, but your business metrics remain flat. That gap usually lives in your key results.

Many key results track guaranteed activities, so they look successful whether or not performance actually improves. A strong key result tracks an outcome you can influence, which is why it drives real progress.

Swipe through for four quick tests to evaluate your key results, plus what to do when a well-written metric still fails to change behavior.

Run your current goals through these four tests. If a metric can hit 100% while the business stays flat, you have a design issue, and design issues are fixable.

Read the full breakdown with before-and-after rewrites on the Xodiac blog. Link in the comments.

08/31/2026

Fixing OKRs almost always comes down to rewriting the key results.

The objective usually reads fine. The trouble starts underneath, where the key results quietly turn the whole initiative into a task list. The dashboard goes green, but nothing about the business actually moves.

Here is the one-line test: A strong key result measures an outcome you can directly influence. A weak one measures an activity you can guarantee.

"Ship the new onboarding flow" is safe, which is why it tells you nothing about whether onboarding got better. "Move first-week activation from 20 to 45 percent" is not safe, which is exactly why it is worth tracking.

Even a well-written key result needs to be seen to work. We watched one team put three clear numbers on the wall for a set of slow manual processes: time, errors, and cost. Behavior shifted as soon as those numbers were visible and reviewed every week, dropping one process from nine hours down to fifteen minutes.

A strong key result hidden in a spreadsheet is just paperwork with better grammar.

Our latest article breaks down four quick tests for telling a strong key result from a weak one, complete with before-and-after rewrites.

Link in the comments.

08/26/2026

The fastest way to ruin your OKRs is to pay people for them.

Attach a bonus or a performance rating to the score, and the number stops being information. It becomes a judgment. And people respond exactly the way you would expect intelligent people to respond.

They negotiate the target down to something they are confident they can hit. They pad the definition of done. Every score drifts toward safety, because safety is now what pays.

Off the compensation scale, the score answers one honest question: are we making progress toward the goal? On it, the score answers a very different one: how do I protect myself?

You cannot get both. The moment the number affects someone's pay, you lose the honest version of it, and you lose the stretch that made OKRs worth setting in the first place.

This is the trap that quietly kills more OKR programs than any framework choice ever will. The goals look fine on paper. The scoring looks rigorous. But everyone has learned to game a number that used to tell you something true.

If your OKRs are already tied to pay, the situation is fixable, but not overnight.

We made the full case, and what to do about it, on the blog.

08/25/2026

A green dashboard can be dangerously misleading.

Completing 100% of your planned tasks feels like a win. But if your revenue, customer retention, or delivery speed stay completely flat, those tasks were just activities in disguise.

Real progress isn't about guaranteeing deliverables. It is about tracking the actual impact those deliverables create.

And if you want a metric to actually change behavior, get it out of hidden spreadsheets. Put the numbers somewhere visible, review them every single week, and focus on what is moving.

We just published a breakdown of four practical tests to audit your key results before next quarter.

08/24/2026

70 percent of your biggest goal sounds like a miss.

For an OKR, it's the point.

Everywhere else at work, hitting 70 percent means explaining yourself. But an OKR is built to land right around there. A steady 100 percent is not the win it looks like. It usually means the goal was too safe to stretch anyone.

Read the score as a grade on your team and you teach them to aim lower next quarter. Read it as a signal about the goal, and you learn something you can actually use.

The full breakdown of every score band, and how to hit the sweet spot on purpose, is on the Xodiac blog. Link in bio.

08/21/2026

There are two kinds of goals, and only one of them needs a stretch.

Toyota has language for the difference. Kaizen is continuous improvement: small, steady gains on the way you already work. Kaikaku is disruptive change: stopping to rethink the work itself.

If a goal only needs Kaizen, a comfortable target will get you there. Work a little harder, tighten a few things, done.

But some goals cannot be reached by working harder at all. The old way of doing the work simply will not get there, no matter how much effort you pour in. Those goals need Kaikaku. They force a team to stop and rethink, because the familiar path plainly does not reach the target.

This is what a stretch goal is actually for. Not to squeeze more hours out of people. To make the current approach visibly insufficient, so the team has a reason to invent a better one.

Strip the stretch out and you strip out the reason the goal existed. You are left with a task list wearing the language of ambition.

There is a limit, of course. Stretch, but do not break. Set the goal so far past reach that nobody believes it, and people quietly write it off. A target no one believes is a target no one aims at.

The sweet spot is the goal that makes a team rethink the work, while still letting them believe they can pull it off.

08/20/2026

A steady 1.0 on your OKRs is not a sign your teams are excelling. It is usually a sign your goals stopped stretching.

Most leaders read an OKR score the way they read every other number: higher is better, 100 percent is the target, anything short of it needs explaining. That instinct is exactly backwards for the one metric built to land around 70 percent.

This carousel walks through what each score band is really telling you, why 0.7 is the sweet spot, and the one condition that ruins the whole scale. Read it and you will not look at a clean 1.0 the same way again.

Swipe through, then read the full breakdown on the Xodiac blog.

08/19/2026

A 1.0 on your OKR is not the good news it looks like.

Here is what the common score bands actually tell you, if you read them as a signal about the goal rather than a grade on the team.

A steady 0.9 to 1.0 means the goal was too safe. It was set conservatively, or negotiated down to a number someone knew they could hit.

0.6 to 0.8 is the sweet spot. Meaningful progress on a bold objective, with something left to learn from.

0.4 to 0.6 is ambitious and short of the mark. Not automatically a problem. The question is why.

Below 0.4 usually means the goal was unrealistic, under-resourced, or built on an assumption that turned out wrong.

Notice what none of these bands tell you: how hard anyone worked. That information is not in the score. It never was.

This is the part most teams get backwards. They treat a low number as proof the team underperformed, and a high number as proof they excelled. Both readings skip the more useful question. Was this a well-built goal in the first place?

Score the progress. Then review the goal itself. Those are two different conversations, and most teams only ever have the first one.

Full breakdown of every band on the blog.

08/18/2026

Two true stories about targets.

Story one. A program was going to be judged on a dollar-value goal. We watched the directors move that number up and down, up and down, until it landed in a range everyone felt comfortable they could hit. Then they published it and tracked progress toward it. Diligently. Professionally. Toward a number chosen because it was safe.

Story two. A financial institution told its departments to spend 50% of their budget on Agile projects. One manager asked a single question: what is our biggest spend project? They relabeled it "Agile." Target hit. Nothing else changed.

Neither of these is a story about bad people. Both are stories about what measurement does when money or judgment rides on it. People stop optimizing the outcome and start optimizing the number. And the numbers all said success.

This is why we keep saying key results are not targets. They are progress indicators: signals that tell you whether your strategy is working. The moment a key result becomes something you are paid to hit, it stops telling you anything. You lose the stretch, you lose the honesty, and you lose the information.

Here is a diagnostic worth running this week. If your metrics look great and nothing feels like it is actually improving, the metric became the target somewhere. Find where.

Both stories, and the position they add up to, are in this week's blog post: https://xodiac.ca/articles/tying-okrs-to-compensation/

Link OKRs to pay and teams stop stretching. Here is why tying OKRs to compensation quietly kills ambition, and what to do instead.

08/14/2026

She refused to set an ambitious goal. Smart woman.

Her company tied OKRs to bonuses. So she wrote targets she knew she could hit, every single quarter. Protecting her paycheck was the rational move.

That is what happens when goals decide pay: ambition becomes a personal financial risk, and nobody takes it. The goals look great on paper. The stretch is gone.

Our take: OKRs should inform performance conversations, never decide compensation. And if your company already made the link, there is a way back (it starts with leaders missing goals in public and celebrating it).

Both articles are on the blog now. Link in bio.