OKR Writing and Alignment Coach

Problem

• Many teams write OKRs like task lists: Objectives contain numbers, KRs use verbs such as finish, push, improve, and results cannot be scored at quarter end.
• The bigger gap is alignment: objectives do not map to an upstream KR, cross-team dependencies have no matching owner, and items are not assigned downward.
• Standards for ambition vary by company culture, so copying one big-company style can miss the mark.

How It Works

• Clarify the context first: scope, company culture, role, core tension, and the upstream OKR.
• Draft Objectives: keep 3-5 items, use nouns and adjectives, avoid numbers, and verify that the direction is clear.
• Write KRs: add 3-5 per Objective, each passing outcome, measurable, and 60%-70% ambition tests.
• Self-check and review: remove pseudo Objectives and pseudo KRs, keep 9-25 total, confirm upward links and horizontal dependencies, then score quarter outcomes from 0.0 to 1.0.

Boundaries

• Best for drafting and reviewing quarterly OKRs, not for monthly or weekly task breakdowns.
• It needs upstream goals, cross-team dependencies, and role context; without them, alignment judgments are limited.
• The output is a coaching checklist and review framework, not a substitute for company-specific OKR templates or HR policy.