If this is your team’s first cycle of OKR, confidence scoring is the simplest habit you can build to keep your goals alive through the quarter. It takes 10 to 15 minutes a week. It does not need a new meeting on anyone’s calendar. Done well, it saves time, because you catch problems early instead of finding them at the end of the cycle when there is nothing left to do about them.
If you would rather watch it, the video above walks through the same agenda in under six minutes. Otherwise, here is how to run it.
What confidence scoring is
For each key result, the team gives a 0 to 1 score for how likely they are to hit the target.
1.0 means certain. 0 means no chance. Anything in between is the team’s gut feel. The point is not the number itself. The number is the conversation starter. A low score tells us we should be talking about what is blocking us. A high score tells us we should be talking about what is working so we can do more of it.
How the 0 to 1 scale works
Score each key result, not the whole objective.
- 1.0 means you are certain you will hit it. If every key result sits at 1.0, the goal probably was not ambitious enough.
- 0.7 is healthy confidence for a stretch goal. This is roughly where a well-set key result should sit early on.
- 0.5 is a coin-toss. It needs the most attention in your check-in.
- 0.3 or below is a red flag. Something has to change, or the target does. A score this low is not a failure, it is information.
The score itself matters less than the movement. A key result that drops from 0.7 to 0.4 in a week is telling you something while you still have time to act.
Plug it into a meeting you already have
This is not a new meeting. Put it inside one your team already runs. Sprint planning. The regular team sync. Whatever rhythm you already have.
Run it weekly, or every two weeks at most. A quarter goes by faster than you would think. If you only check in monthly, you will find out three weeks late that something has gone sideways.
If the discussion is not useful, your OKR probably needs a tweak. Reach out if you want a second pair of eyes.
The four things to talk about
For each key result, walk through four things:
- Confidence score. How likely are we, right now, to hit the target?
- Progress since last week. What actually happened.
- Focus for the week ahead. What we are doing next.
- Blockers and risks. What is slowing us down that the team can help with.
That is the whole agenda for each key result. Do not over-engineer it.
A worked example
Say the key result is: increase reorder rate from 45% to 70%.
If I think we will only get about halfway there, I score 0.5. If I think we will get most of the way, around 80% of the journey, I score 0.8. Do not overthink it. Gut feel is the point. Reorder rates take time to move, and a single week’s snapshot of the metric will not tell you whether the plan is working. The score is the team’s read on the plan, not the plan’s report card.
Then walk the four things:
- Confidence: 0.7
- Progress since last week: confirmed the plan, tested three redesigned order forms with customers, early signal looks good.
- Focus for the week ahead: test the new design with more customers.
- Blockers: support tickets are eating into our test time. Team needs a plan to handle that.
Done. Move on to the next key result.
When the team does not agree
If different people on the team give different scores, that is the most useful thing to surface.
Go with the lowest score until the team is aligned behind the plan.
A spread of scores means people do not share the same picture of what “on track” looks like. That is a conversation worth having before you do another week of work.
Keep it tight
The whole confidence-scoring agenda should run in 10 to 15 minutes. Might take a little longer the first time. After that it gets fast.
The trap is going deep on one key result and never getting to the rest. If a key result needs a real working session, park it. Book a 30-minute breakout straight after the meeting with the people who need to be there. Keep the weekly check-in moving.
Use whatever tool you like
You do not have to use a scoring sheet. If the team already lives in Jira, Linear or Notion, use that. What matters is that you capture the confidence score, what changed, and the metric where it moved.
We built because most teams want one ready to go. Take it, copy it, change it. Whatever works.
Make it safe
A high score is not a win. A low score is not a loss. The score is information. What the team does with it is the work.
The first few weeks will feel a little clunky. That is normal. Stick with it. By week four it should feel like the most useful 15 minutes of your team’s week.
What teams actually see
At Altro APAC, the leadership team credited the weekly check-ins and confidence scoring with a single-cycle lift: team effectiveness up 67%, connection to strategy up 74%, and psychological safety up 30%. The OKR itself was not dramatically different. The cadence was.
At MLC Life Insurance, the same weekly rhythm contributed to 88% of teams reporting better work visibility, 72% reporting higher productivity, and a 60% reduction in Finance’s end-of-month activity.
The pattern is the same. The score is the conversation starter. The conversation is what changes the outcome.
Get started
Grab and run it in your team’s next meeting.
If you want a hand getting the rhythm going with your team, book a free OKR Strategy Call. 15 minutes with Tim. We will sketch the cleanest way to bring weekly confidence scoring into your team.
