OKR Quiz

A KPI can supply a useful measure, but the measure alone is not a complete key result. Connect it to the objective, agree the change you want to see and set a timeframe. That turns an ongoing health measure into a way of checking progress towards a particular goal.

An OKR score describes progress against particular goals. It does not capture the whole job, the difficulty of the goals or the circumstances behind the result. Use scores to support learning and discussion. Treating them as a direct performance rating can encourage easy targets and make honest reporting harder.

A stretch goal should encourage meaningful progress beyond what is comfortably achievable. Consistently reaching every stretch target may suggest too little ambition. This does not mean every goal should be missed: committed OKRs are expected to be delivered in full. Agree which type of goal you are setting before judging its score.

A launch shows that something was delivered. It does not tell you whether customers used it, solved their problem or had a better experience. Agree the customer change you want, then gather evidence of that change. Delivery is important, but it is not proof of the intended benefit.

When writing the key result, agree the measure, target and deadline, including where the evidence will come from. If the baseline is unknown, make finding it explicit. A shared definition helps the team judge progress consistently and avoids discovering different expectations when it is time to score.

OKRs need clear ownership and regular check-ins. A champion can help a wider rollout, and initial writing sessions take time. For a small start, progress reviews can fit existing meetings. Establish a useful rhythm for decisions and learning, rather than assuming you need a new job or a heavy meeting schedule.

Starting small gives a team space to practise writing useful goals, checking progress and reflecting on what it learns. One objective with a couple of key results can be enough for that first cycle. Keep it connected to the organisation’s priorities, then use the experience to decide how to develop the approach.

Reviews help the team learn while there is still time to act. Compare progress with the intended result, discuss what is helping or blocking it, and decide whether to change the approach. Changing how you work can be the right response; keep any changes to the goals themselves explicit and agreed.

Alignment means understanding how the team’s work contributes to wider priorities. It does not require leadership to write every team’s goals. Teams can use their knowledge to propose objectives and key results, discuss dependencies and agree the connection with others. Make that connection visible, so autonomy supports a shared direction.

New work can be valuable or urgent, but the team still has limited capacity. Discuss how it compares with the agreed priorities and what taking it on would delay or displace. Make any change of focus explicit with the relevant people. OKRs support those trade-offs rather than making every request an additional commitment.