OKR Goal-Setting Framework Creator

Creates a complete quarterly OKR framework with key results, leading indicators, and risk flags.

Best For

•A VP setting quarterly goals after a company restructuring uses it to translate a vague strategic priority into objectives and measurable key results the whole team can rally behind
•A startup COO running the first formal OKR cycle uses the alignment table to show how each team's key results ladder up to company goals before the all-hands kickoff
•A team lead frustrated by task-focused 'key results' in past cycles uses the anti-patterns list to fix how the next OKR review meeting is run

Prompt Template

Create a quarterly OKR (Objectives and Key Results) framework for [TEAM/COMPANY NAME] in [QUARTER AND YEAR]. Current focus: [DESCRIBE YOUR MAIN STRATEGIC PRIORITY THIS QUARTER]. Recent context: [ANY KEY EVENTS, e.g. new product launch, restructuring, market shift]. For each of 3 Objectives: (1) write the Objective as an inspiring, qualitative statement of direction (not a metric), (2) write 3–4 Key Results per Objective, each must be: specific, measurable with a number or percentage, achievable in one quarter, and results-focused (not task-focused), (3) identify one leading indicator metric to track weekly as an early signal that you're on track, (4) flag one key risk that could prevent hitting this OKR. Also provide: a team-level OKR alignment table showing how each team's OKRs connect to the company OKRs, and 3 anti-patterns to avoid when running OKR review meetings.

Pro Tip

Describe the recent context (a launch, a reorg, a market shift) in specific detail, since the leading-indicator metric the model suggests is only useful if it reflects what actually changed for the team this quarter.

Example Output

A sample of what this prompt produces once you fill in the placeholders.

Objective: Make onboarding the reason customers stay past month one. Key Results: reduce time-to-first-value from 9 days to 4 days; increase week-1 feature activation from 40% to 65%; cut onboarding-related support tickets by 30%. Leading indicator: daily signup-to-activation rate tracked weekly. Risk: engineering bandwidth is already committed to the Q3 migration, which could delay the onboarding redesign.