OKR drafting and quality check

Purpose

Produce a small set of outcome-oriented objectives and measurable key results, then test every draft against the company's OKR rules. Reveal weak baselines, ambiguous metrics, missing owners, impossible dates, duplicated results, and broken parent-child alignment before the cycle begins.

Scope

Assess company, department, and team OKR drafts together with the strategy, annual priorities, metric dictionary, prior-cycle results, planning calendar, and OKR playbook. Cover objective wording, key-result metric, baseline, target, unit, due date, owner, confidence, dependencies, and alignment link.

Excluded: setting targets without evidence, grading employee performance, updating the goal system, or declaring an OKR achieved before results are recorded.

Data basis

• Draft OKR table with objective_id, objective, key_result_id, metric, baseline, target, unit, due_date, owner, confidence, and parent_id.
• Strategy and annual priorities, metric definitions, prior-cycle OKRs and outcomes, capacity assumptions, and dependency register.
• Company OKR playbook with scoring, stretch, cadence, and quality rules.

Result

Create an OKR quality sheet with one row per objective and key result, rule checks, evidence citations, status, suggested wording, and open point. Write a review memo grouping defects into measurement, alignment, ownership, ambition, duplication, and timing.

Quality criteria

• Every key result has a metric, baseline, target, unit, owner, and due date or a cited gap.
• A result measures an outcome or verifiable output, not an activity disguised as success.
• Target calculations use the metric dictionary and compatible baseline period.
• Parent links and duplicate metrics are checked across the entire supplied hierarchy.
• Suggested rewrites preserve intent and do not fabricate a target or baseline.

Instructions

Apply the playbook's scoring and ambition bands before general judgment. Treat “improve,” “support,” or “launch” as incomplete until the measurable result is stated. Reject a percentage change when the denominator is undefined or zero. Check that the due date falls inside the declared cycle and that the owner is a named role or person in the source. Flag key results that merely repeat a parent result, share an identical metric-target pair, or have no dependency path for a stated prerequisite. Keep the original draft beside every proposed rewrite.

Adapt before use

• Add the OKR playbook, strategy, metric dictionary, planning calendar, and prior-cycle results.
• Define scoring, stretch, confidence, owner, and cycle-date conventions.
• Map objective and key-result columns, parent links, and dependency identifiers.
• Set the acceptable number of objectives and results per level if the playbook specifies one.