What we offer Our method Who we help Blog About Contact Take the assessment
← Back to Blog OKRs

AI Can Write Your OKRs. That Was Never the Hard Part.

Ask almost any AI tool to draft an OKR today and it will hand you something correctly formatted in under a second — a verb, an outcome, three plausible key results with dates and targets attached. It's fast, it's fluent, and it looks like the finished thing. One 2026 industry survey of 200 organizations found 83% now use AI somewhere in their OKR process — worth noting that survey was run by an OKR software vendor, not an independent body, but the direction of the number rings true from what we see in workshops. AI adoption here is real and it's happening fast.

None of that is a problem. What's worth being honest about is what it actually solved.

What AI is genuinely good at

Staring at a blank box is the single biggest reason OKR-writing sessions stall. Someone has a vague sense of what matters to them but no sentence yet, and a blank cursor is a hostile environment for turning a vague sense into a sentence. AI is a legitimately good tool for breaking that stall — take a rough idea, get back something in roughly the right shape, and edit from there instead of starting from nothing. That's a real, useful improvement in how fast a first draft appears.

It's also reliably good at the mechanics: strong verb instead of a vague one, a metric with a unit attached, a date that isn't just "soon." The syntax of a well-formed OKR is a solved problem, and AI solves it well.

What it can't tell you

A well-formatted objective and a well-owned one are not the same claim, and the gap between them is exactly where OKR programs actually fail. AI can guarantee the first. Nothing except an honest conversation with a real person can guarantee the second.

Correctly formatted and actually true are two different properties of a sentence. AI checks the first. Only a room full of people who have to defend their answers out loud checks the second.

Three things a generated OKR can't tell you, no matter how well-written it is:

Here's the part that makes this easy to miss: a generated OKR and a genuinely owned one can read completely identically on the page. Same verb, same outcome, same well-formed key results with dates and targets attached. Nothing in the sentence itself tells you which one has a real person behind it, which one connects to a priority the leadership team actually argued over, and which one is just a plausible string of words with no conviction attached. That's exactly why it's such an easy gap to fall into — there's no formatting tell for it. The only way to find out is to ask, out loud, in the room.

Where this leaves the honest answer

Use AI for what it's actually good at: turning a rough idea into a properly-shaped first draft, fast, so the conversation can start from something concrete instead of a blank page. That's a genuine time saver and there's no reason to avoid it.

Don't let the fluency of the output stand in for the three things it can't produce. Before an OKR is finished — generated with AI assistance or not — it's worth checking it against three plain questions: Is there one named person who said, out loud, "this is mine"? Does it map to a strategic priority the group actually weighed against the alternatives? And would the person who owns it still write this exact sentence if asked to defend it in the room, not just approve it in a document?

This is the structural reason Keel runs contribution scoring as its own step, separate from and prior to OKR writing. It exists specifically to answer the ownership and priority questions with a real, argued-over group decision — before anyone, human or AI, drafts a single sentence. The draft can come from anywhere. The commitment behind it can't.

Curious where your own execution is strong — and where the risk sits?

Take the 5-minute assessment