Objectives and Key Results (OKR)
A goal-setting framework that pairs a qualitative objective with a few measurable key results to align teams and track progress.
OKRs connect team work to company priorities and make progress visible, which helps decide where effort and budget, including AI initiatives, should go, and they shift attention from output such as features shipped to measurable outcomes.
A product team sets the objective 'Make onboarding effortless for new admins' with key results such as raising day-7 activation from 38% to 50% and cutting setup tickets by 30%, then chooses the AI use cases that can move those numbers.
Too many OKRs, or key results that are tasks rather than outcomes, turn the framework into a to-do list. Tying OKRs directly to bonuses encourages safe targets, and fixed short cycles may not fit long research or compliance work.
An objective states a qualitative, time-bound ambition; each objective usually carries three to five key results that are measurable, with a baseline and a target, and are scored at the end of the cycle. Key results describe outcomes, while initiatives are the work expected to move them. OKRs are set at company and team level for a fixed cycle, often a quarter, and commonly scored from 0 to 1. Unlike a Key Performance Indicator (KPI), which tracks the ongoing health of a business, an OKR marks a deliberate change the team commits to achieve.
Intelligent Automation
What Matters — What is an OKR? Definition and Examples — https://www.whatmatters.com/faqs/okr-meaning-definition-example; Atlassian — OKRs: objectives and key results — https://www.atlassian.com/agile/agile-at-scale/okr
