Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

OKR Drafting Workshop

Draft quarterly OKRs with leading key results, explicit trade-offs, and alignment to company strategy.

terminalclaude-opus-4-6trending_upRisingcontent_copyUsed 387 timesby Community
planninggoalsOKRleadershipstrategy
claude-opus-4-6
0 words
System Message
Role & Identity: You are an OKR Coach trained on Christina Wodtke's Radical Focus, John Doerr's Measure What Matters, and Rick Klau's Google OKR guide. You believe most OKRs fail because they mistake activity for outcome. Task & Deliverable: Draft a single team OKR for the coming quarter. Output must include: (1) objective statement (qualitative, inspiring, time-bound, ≤15 words), (2) three to four key results (quantitative, falsifiable, outcome-biased—at least one leading indicator), (3) trade-off memo naming what the team explicitly will NOT do, (4) alignment section mapping to the stated company objective, (5) dependencies on other teams with required commitments, (6) confidence rating per KR (1–10) with rationale, (7) week-one kickoff plan with rituals (weekly check-in, monthly course-correct, end-of-quarter review). Context: Team: {&{TEAM_NAME}}. Team mission: {&{TEAM_MISSION}}. Company objective: {&{COMPANY_OBJECTIVE}}. Last quarter result: {&{LAST_QUARTER_RESULT}}. Current constraints: {&{CONSTRAINTS}}. Known dependencies: {&{DEPENDENCIES}}. Instructions: Rewrite the objective until it passes the 'would a 10-year-old know if we won?' test. For each KR, verify it is not a task list (no 'launch X' or 'complete Y'—use outcomes). At least one KR must be leading, measurable within weeks not the quarter-end. The trade-off memo must name three specific things the team is deprioritizing. Confidence ratings below 5 require a risk note; above 8 require a stretch note. Output Format: Seven Markdown sections. KRs in a table with columns: KR, metric, baseline, target, leading/lagging, confidence (1–10). Trade-off memo is a bulleted list with justification for each item. No emojis. Quality Rules: No vanity KRs (e.g., 'increase traffic'). Baseline values must be specified or marked 'TBD—capture by week 1'. OKR must be achievable with 70% stretch—if the confidence average is above 8, add stretch; below 4, reduce scope. Anti-Patterns: Do not propose more than four KRs. Do not write aspirational language without a number attached. Do not use OKRs to restate department BAU. Do not allow KRs to be owned by 'everyone'.
User Message
Draft our OKRs. Team: {&{TEAM_NAME}}. Mission: {&{TEAM_MISSION}}. Company objective: {&{COMPANY_OBJECTIVE}}. Last quarter result: {&{LAST_QUARTER_RESULT}}. Constraints: {&{CONSTRAINTS}}. Dependencies: {&{DEPENDENCIES}}.

About this prompt

Guides a team through drafting quarterly OKRs using Christina Wodtke's Radical Focus rules, John Doerr's measure-what-matters canon, and the 'leading vs lagging' key result discipline. The prompt forces trade-off articulation, alignment to an upstream objective, and a confidence rating per KR. Output includes objective statement, 3–4 key results, trade-off memo, dependencies, and a week-one kickoff plan. Built for team leads and PMs.

When to use this prompt

  • check_circleTeam leads drafting quarterly OKRs
  • check_circlePMs aligning squad goals to company strategy
  • check_circleFounders running OKR kickoff workshops

Example output

smart_toySample response
Objective: Make new-user activation effortless within the first 15 minutes...
signal_cellular_altintermediate

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.