This set builds vocabulary for setting and tracking ambitious, measurable team goals.
0 / 5 completed
1 / 5
At standup, a dev references the team's ambitious, qualitative goal for the quarter paired with specific, measurable outcomes used to track progress toward it. What framework is this?
OKRs pair a qualitative, ambitious Objective with specific, measurable Key Results used to track progress toward it, giving a team both direction and a concrete way to know whether they're succeeding. This structure distinguishes OKRs from a vague goal statement with no measurable outcome. It is widely used across tech companies for quarterly or annual planning.
2 / 5
During a design review, the team debates whether a specific key result is genuinely measurable enough to track progress objectively. Which quality are they evaluating?
A well-formed key result should be quantifiable, with a clear numeric target and a way to objectively measure progress, rather than a vague statement open to subjective interpretation. Without measurability, a key result fails to serve its core purpose of tracking real progress. This quantifiability requirement is a defining characteristic distinguishing key results from qualitative objectives.
3 / 5
In a code review, a dev references a mid-quarter meeting where the team reviews current progress against each key result's target. What is this practice called?
A check-in reviews current progress against each key result's target partway through the tracking period, letting a team catch a stalled or off-track goal early enough to course-correct. Without periodic check-ins, a goal set at the start of a quarter can go unexamined until it's too late to act on the finding. Regular check-ins are a core part of making OKRs an active management tool rather than a static document.
4 / 5
An incident report style retro shows a team consistently hit 100% of every key result every quarter with no variance. What issue does this suggest?
OKRs are often intended as ambitious stretch goals, so consistently hitting exactly 100% every quarter can actually indicate targets were set too conservatively rather than reflecting genuinely stretching, well-calibrated goals. Some frameworks expect partial completion, like 70%, as a healthy sign of ambition. This pattern is a common discussion point when retrospecting on an organization's goal-setting calibration.
5 / 5
During a PR review, a teammate asks how an OKR differs from a simple task list or backlog item. What is the key distinction?
A task or backlog item tracks a single discrete unit of work, while an OKR operates at a higher level, defining an ambitious goal and the measurable outcomes that indicate progress toward it, often spanning many individual tasks across a team. This makes OKRs a planning and alignment tool rather than a execution-tracking mechanism. Teams typically use both together, with tasks contributing toward broader OKR-tracked outcomes.