OKR Planning Framework — objectives and key results
The OKR framework on an interactive canvas: objectives and key results cascading from company to team to individual, plus the weekly and quarterly cadence that makes them work.
OKRs — objectives and key results — turn an ambitious goal into measurable progress: an objective says where you are going, key results say how you will know you got there, and the whole set cascades from company to team to individual.
OKR Planning Framework — objectives and key results
The interactive FlowJam canvas for this explanation — every lane, row and arrow above is a real QueryChart diagram you can open and edit.
How to read this visual
- Read the company row first: the objective and its key results define the direction for everything below.
- Follow the cascade down — team objectives align to company key results, individual objectives to team key results.
- Read the cadence row last: the weekly and quarterly boxes are what keep the static-looking objective rows alive.
The objective and its key results
"Company objective" is the qualitative goal — inspirational, ambitious, not guaranteed. "Company key results" make it measurable with three to five numbers. The two boxes define the shape of every OKR below: the objective answers where, the key results answer how much. The visual pairs them in the same row so the distinction stays visible.
The cascade
"Aligned team objectives" and "Team key results" cascade the company's ambition down one level: the team's objective supports a company objective rather than duplicating it, and its key results define the team's measurable contribution. "Individual objectives" and "Individual key results" continue the chain to the person. The point of the cascade is traceability — every key result in the company should trace up to a company key result.
The rhythm
"Weekly check-ins" update progress and surface blockers while there is still time to act, and "Quarterly review and reset" scores each key result, captures the learning and sets the next cycle's objectives. Both sit in the Cadence row, beneath the structure, because the structure is static and the cadence is what makes it work — an OKR cycle without the weekly and quarterly rhythm is a wish list.
Key relationships and takeaways
- An objective is qualitative and ambitious; key results make it measurable — the two never mix.
- The cascade gives every team and individual a line of sight to the company objective.
- Alignment means supporting a parent objective, not copying it.
- Key results should be ambitious but achievable — a perfect score every quarter means they were too easy.
- The cadence, not the structure, is what makes OKRs work.
When to use this visual
- Setting up an OKR cycle for the first time — the cascade shows how far the structure needs to go.
- Auditing an existing OKR: an objective with no key results, or key results that are tasks, is the common failure.
- Running a quarterly reset — score the old key results, then reuse the canvas for the new cycle.
How it works
Fill in your real objectives
Replace the company, team and individual boxes with your actual objectives and key results, keeping one objective and its key results per row.
Draw the alignment arrows
Add the arrows that show which team objective serves which company key result, and which individual objectives serve each team — alignment is a drawing exercise, and the canvas makes it visible.
Add a scoring column
Add a comment to each key result recording its current progress score and the evidence, so the canvas doubles as the live tracking sheet.
Date the review
Annotate the quarterly review box with the actual date and the scoring practice you use (0-1 or 0-100), and clear the key result scores when the new quarter starts.
Frequently asked questions
What are OKRs?
OKRs stand for objectives and key results. An objective is a short, qualitative, ambitious goal; key results are the measurable outcomes that define whether the objective was achieved, typically three to five per objective. The system's value is pairing the inspiration of a goal with the discipline of measurement, and cascading both from company to team to individual.
What is the difference between an objective and a key result?
An objective is direction: a qualitative statement of where you are going, deliberately ambitious. A key result is measurement: a specific number that says how you will know you arrived, like a retention percentage or a launch date. The common failure is writing key results that are tasks — "release the feature" — rather than outcomes with a number.
How far should OKRs cascade?
Until every person can trace their work to the company objective. The usual cascade is company to team to individual, though small companies stop at team and large ones add layers. The test is traceability: if an individual's key results cannot be traced up to a company key result, the alignment is decorative. The canvas's three rows model exactly this.
What makes OKRs fail?
The usual causes are key results that are tasks rather than outcomes, objectives set and never revisited, and a cadence that stops after the initial planning. OKRs are a rhythm, not a document — the weekly check-in and the quarterly scoring are what keep them honest. The visual puts the cadence in its own row so that dependency is impossible to miss.
Edit this visual in QueryChart (FlowJam)
Open this exact OKR canvas as your own chart and replace the prompts with your company's real objectives and key results.