okr

OKRs (Andy Grove at Intel; popularized by John Doerr, Measure What Matters) pair a qualitative, time-bound objective with 3-5 quantitative key results, so a vague ambition becomes something you can score: hit every key result and the objective is met by definition.

The anatomy of objectives and key results, outcome-versus-output, scoring, cadence, alignment, and the pitfalls live in references/okr.md. Load that file before facilitating.

When to use

The user wants to convert a strategy or ambition into goals that can be measured and reviewed, usually for a quarter. OKRs are the goal-setting layer; for the broader performance-measurement frame that links goals across financial, customer, process, and learning perspectives, the balanced-scorecard skill is the companion. Use OKRs when the question is "what are we committing to achieve this period, and how will we know."

Language

Facilitate and write the document in the language the user is writing in. The reference file is English; keep the framework keyed to it regardless of output language.

Inputs

• SCOPE (required): the level (company, team, or individual) and the period (for example, Q3 2026).
• DIRECTION (optional): the strategy or higher-level OKRs these should align to.
• CONTEXT (optional): the current situation, constraints, and what the unit owns.