Framework · Strategy & vision · 3 min read
OKRs
Objectives and Key Results: one qualitative objective with 2–4 measurable key results per quarter or year, so a UX team can say what outcome it wants and how it will know it got there.
A qualitative outcome people care about. Not an activity.
e.g. make UX demand visibleMeasurable and time-bound.
e.g. 100% of requests via intakeMeasurable and time-bound.
e.g. capacity map reviewed monthlyOptional. Keep 2–4 in total.
e.g. workload score ≥ 3.5/5One Objective + 2–4 Key Results, per quarter or year
Use it when
- Your organisation plans with OKRs and the UX team needs its own, linked to product and business goals.
- You have a UX strategy and want to turn one pillar into something you can measure this quarter.
- Your team reports what it did ("we ran 12 tests") and you want it to report what changed.
How to use it
- Pick one outcome from your strategy. Start from a pillar or a problem on your roadmap. Write the Objective as a qualitative direction that people would care about. Output: one Objective sentence.
- Derive key results from goals and signals. Use Goals-Signals-Metrics: what is the goal, what signal would show progress, and what metric captures it? Turn the best metrics into 2–4 key results. Output: 2–4 draft key results.
- Make each key result measurable and time-bound. Each one needs a number, a baseline if you have it, and a date ("by end of Q2"). Remove any key result that is really a task. Output: final key results with numbers and dates.
- Check the set. Ask: if all key results are met, is the Objective achieved? Do you have the capacity to do the work? Is any key result easy to game? Output: a checked OKR set.
- Track and review on a cadence. Check progress monthly, score at the end of the quarter, and write down what you learned for the next set. Output: a short end-of-quarter review.
Worked example
The OKR example from the module, for a fictional internal operations platform.
| Key result | Measurable? | Time-bound? |
|---|---|---|
| KR1: 100% of UX requests from 5 domains go through one intake by end of Q2. | Yes, share of requests | Yes, end of Q2 |
| KR2: Capacity map reviewed monthly with domain leads (≥ 4 of 5 attending). | Yes, attendance | Yes, monthly |
| KR3: Designer-reported "workload sustainable" score ≥ 3.5/5. | Yes, survey score | Yes, within the period |
Notice that the Objective names an outcome (visibility), not an activity (building an intake form). The intake form is the work that gets you there.
Watch out for
- Activities as key results. "Launch the intake form" is a task. Ask "so that what?" until you reach a result you can measure.
- Too many key results. More than four splits attention. Keep 2–4 per objective.
- Vanity numbers. Counting sessions run or screens designed is easy to hit and says little. Measure change for users or the organisation.
- No capacity behind it. An OKR without the people and time to do the work is a wish. Check it against your capacity map.
Template
Copy this into your planning doc for each objective.
Period: Owner:
Objective (outcome, qualitative):
KR1: Baseline: Target: By:
KR2: Baseline: Target: By:
KR3 (optional): Baseline: Target: By:
Derived from (goal / signal):
Work that drives it (not KRs):
Capacity check: Yes / No
End-of-period score and learning:
- Lean UXJeff Gothelf & Josh SeidenBook · 3rd ed. 2021 (Amazon)
- Objectives and Key Results (OKRs) in UXNN/gVideo (external site)
- UX Goals vs. OKRs vs. KPIsNN/gVideo (external site)
"See on Amazon" links are affiliate links. As an Amazon Associate I earn from qualifying purchases, at no extra cost to you.