Page 138 · Module 06, Build Your Team · this screen continues that page

All 108 frameworks
6.2IntermediateModule 06 · Build Your Team

OKRs - Goals That Drive Action

Your team sets goals at the start of the quarter that nobody looks at again. Or your goals are

The prompt

Copy & paste ready
6.2OKRs - Goals That Drive Action
Act as an OKR coach and strategist. My business context : [COMPANY STAGE, TEAM SIZE, MAIN FOCUS] This quarter's priority : [THE ONE THING THAT MATTERS MOST] Current challenges : [WHAT IS HOLDING GROWTH BACK] Write 3 OKRs for this quarter: For each OKR: OBJECTIVE : Inspiring, qualitative direction (1 sentence) KEY RESULT 1 : Specific, measurable outcome with number KEY RESULT 2 : Specific, measurable outcome with number KEY RESULT 3 : Specific, measurable outcome with number Then: flag any Key Result that is actually a task disguised as an outcome - and rewrite it. Suggest a weekly check-in question for each OKR. Achieving Market Leadership Define Key Results Establish measurable outcomes Set Objective Drive Action Define market Launch feature X leadership goal and track adoption
LabelsReplace theseSwap the role below

LabelsReplace theseSwap the role below

Pro tip, from the book

The most common OKR failure is writing Key Results that measure activity instead of outcome. 'Conduct 20 customer interviews' is activity. 'Identify 3 validated insights that change our roadmap' is outcome. Your team can tick off activity without moving the needle. Only outcomes tell you if you're actually winning.

Who should run this prompt

Module role profile

Who should advise on people and leadership decisions? Leadership decisions are the highest-leverage decisions in any organisation — and the hardest to get right because the stakes are human. The roles on this page bring the perspectives of people who have seen hundreds of teams succeed and fail. Use them before hiring, before giving difficult feedback, before restructuring, and before having the conversations you have been avoiding.

Choose any role to drop it into the prompt above. Only the highlighted opening clause changes — the rest of the prompt stays exactly as printed.

Internal rolesThink from inside the organisation
Outside perspectivesChallenge your blind spots

◆◆◆◆◆ → ◆ seniority, board level down to specialist outside the organisation

How to make any role sharper

  1. Add years of experience: "...with 15 years in enterprise SaaS" produces different depth than just the title.
  2. Add what they care most about: "You care most about [X]" shapes every word of the output.
  3. Add their communication style: "Be direct. Flag risks first. No jargon." changes the tone entirely.
See also: 1.3 Role Prompting - The Expert Chair

Use this when

The problem it solves

so vague that you can't tell at the end of the quarter whether you achieved them. Activity is high, progress is unclear.

How the framework works

From the printed page

OKRs were developed by Andy Grove at Intel in the 1970s and popularised by John Doerr at Google. An Objective is a qualitative, inspiring statement of where you want to go. Key Results are 2–4 specific, measurable outcomes that prove you've arrived. The critical rule: Key Results measure outcomes, not activities. 'Launch the new feature' is a task. 'Achieve 40% feature adoption among active users within 60 days' is a Key Result. OKRs work because they separate what you want to achieve from how you'll know you've achieved it.

The method, in four moves

Do these in order
1

Write the Objective as something that would genuinely excite the team, not a business metric.

2

Key Results must be measurable, if you can't put a number on it, it's not a Key Result.

3

Set 3–5 OKRs per quarter. More dilutes focus. Fewer creates over-dependence on one outcome.

4

Review OKRs in weekly team meetings, not just at quarter end. Set goals your team actually works toward, not ones they forget by week two Hitting 100% of your Key Results every quarter isn't success, it's a sign you set them too safe. OKRs work as a stretch tool, not a performance review. If your team is always green, you're measuring comfort, not progress. Ambitious Targets Aren't the Point

Where the framework comes from

Andy Grove, Intel — MBO adapted to OKRs · John Doerr, Google, 1999

When this page changes, your copy of the book does not have to.

The book prints the framework. This page keeps it — and keeps the prompt current, because prompting technique moves faster than print does. When it moves, this page is rewritten and the code in your copy keeps pointing at it. No second edition, no replacement purchase, no account.

If something here looks wrong — a prompt that does not match its framework, a figure that reads oddly — tell Raphy. That correction reaches every printed copy at once.

Framework6.2 of 108
Printed onPages 137138
Prompt extracted18 Sept 2026
Costs to readNothing, no account

Copying is free. An account keeps them.

Nothing on this page is behind a login and nothing ever will be. Save any prompt to your own list, pick up on another device, and send a colleague a link with your name on it. No card, no trial, no paywall on the prompts themselves.

See how it works
Save this framework to your own list
Pick up where you left off on another device
Send a colleague a link with your name on it