OKR Check-In Templates · 7 min read

The 1:1 OKR Check-In Template: Five Questions That Surface What the Group Standup Hides

I've run OKRs for about a decade, and the single most wasted slot in that whole machine is the OKR portion of a manager-report 1:1. Most managers turn it into a status report they could've read in the tool. That's a miss. The 1:1 is the one place a person will tell you the real reason a key result is stuck, the reason they'd never say with seven peers watching. So I built this template to do one job: pull out the blocker the report won't volunteer in the group, then actually clear it.

By Max Bondarenko · Last updated June 2026

The template, up front

No buildup. Here are the five questions I ask in the OKR slice of a 1:1. They're not a status pull. Status lives in the tool already. These are tuned to get a person to name the thing they'd swallow in a room full of peers, and then to make it my problem to fix. Run them in order. The first one is soft on purpose. The last one is the whole point.

Why each question is there

Question one asks for the least-confident KR, not a green-yellow-red rundown. People will defend a number in a group because admitting doubt feels like admitting failure in front of peers. One-to-one, doubt is cheap to share and incredibly useful to hear. When someone says 'honestly, the activation KR, I think we're going to land at 24% not the 30% we committed,' you've just bought yourself five weeks to do something about it. Question two is the pry bar. The phrase 'the part you wouldn't say in the standup' gives explicit permission to drop the polished version. I've had a report tell me a KR was stalled because they didn't trust the data source, something they'd never raise in a group because it sounded like blaming the analytics team. That's gold, and it only comes out one-to-one.

Question three is the one managers skip and shouldn't. Half of stuck KRs are stuck on something the report literally cannot move, a pricing decision, a hire that's frozen, a competing priority handed down from someone two levels up. If it's mine to clear, my job in that 1:1 is to clear it, not to coach the person on grit. Question four forces a single lever instead of a wishlist, because 'what do you need' gets you a list of ten things and one real one. Make them pick the one. Question five is the quiet killer. A target set wrong in week one poisons every check-in after it. I'd much rather revise a wrong target early, in week 4 not week 12, while there's still runway to set a real one. A team I ran spent an entire quarter chasing a KR of 'ship 8 integrations' when the actual business need was two deep ones; we caught it in week 3 of the next quarter only because someone finally answered question five honestly. That conversation never happens in a standup. It happens here.

One thing I'll say flatly: if you only have time for two of these, ask three and five. Unblocking and target-correction are the two things a manager can do that the report cannot do alone. Everything else is conversation.

Scoring: read the state, then act

I don't score the person in a 1:1. I score the key result, and the score exists only to decide what I do next. Three states, and each one has a single action attached. If you can't name the action, the score is just a color.

How to actually run it

Async by default. I ask the report to drop short answers to the five questions in the 1:1 doc the day before, so the live time isn't spent reading numbers out loud. That turns a 20-minute status recital into a 7-minute conversation about the one or two KRs that are actually at risk. Who attends: just the two of you. The whole value here is that it's not the group; the second another person joins, the honest answer to question two evaporates. Keep the OKR portion to roughly 10 minutes inside a normal 1:1, and don't let it eat the career and feedback parts of the conversation, those matter more.

When to skip it: if every KR is genuinely on track and the async answers say so, skip the live OKR talk entirely and give the time back. Don't run the ritual for its own sake. And skip it the week of a real crisis too; nobody needs a structured check-in while the building is on fire. The template earns its place by catching the at-risk KR three weeks before it would've shown up red on the board. The rest of the time, get out of the way.