Prompt library
Draft OKRs that measure outcomes
Converting outputs to the outcome each output should move is the core OKR discipline, and the self-audit for KR-hits-while-objective-fails catches the misalignment that makes teams cynical about the whole ritual. Anti-goals with floors prevent the classic quarter where growth eats quality.
Last reviewed July 17, 2026
The prompt
Draft OKRs for {{team}} for {{period}}.
Context and ambitions: {{context}}
Produce 2-3 objectives. For each:
1. Objective: qualitative, inspiring but falsifiable in spirit, describing a changed state of the world, not a project name.
2. 3 key results: each a metric movement (from X to Y by date), where X is the real current baseline from my context or [BASELINE?] if I did not give one. No activity KRs ("launch the feature" is output, not outcome; convert it to the metric the launch should move).
3. The anti-goal: the metric we must not sacrifice to hit these KRs, with its floor.
4. A confidence score per KR (0.5 is a proper stretch; 0.9 belongs in a roadmap, not an OKR).
Then audit your own draft: flag any KR that the team could hit while the objective fails, and fix it. That mismatch is the most common OKR bug.Run in idaptOpens a new chat with the prompt prefilled. Nothing sends until you press send.
Fill in the variables
| Variable | What it is | Example |
|---|---|---|
| {{team}} | Whose OKRs | the activation squad |
| {{period}} | The cycle | Q4 2026 |
| {{context}} | Current numbers and ambitions | signup-to-active is 22 percent, target mid-30s; support load must not grow |