Start free trial
Trending New Genres Authors
EnglishEnglish
EspañolSpanish
简体中文Chinese
繁體中文Chinese (Traditional)
FrançaisFrench
DeutschGerman
日本語Japanese
PortuguêsPortuguese
ItalianoItalian
한국어Korean
РусскийRussian
NederlandsDutch
العربيةArabic
PolskiPolish
हिन्दीHindi
Tiếng ViệtVietnamese
SvenskaSwedish
ΕλληνικάGreek
TürkçeTurkish
ไทยThai
ČeštinaCzech
RomânăRomanian
MagyarHungarian
УкраїнськаUkrainian
IndonesiaIndonesian
DanskDanish
SuomiFinnish
БългарскиBulgarian
עבריתHebrew
NorskNorwegian
HrvatskiCroatian
CatalàCatalan
SlovenčinaSlovak
LietuviųLithuanian
SlovenščinaSlovenian
СрпскиSerbian
EestiEstonian
LatviešuLatvian
فارسیPersian
മലയാളംMalayalam
தமிழ்Tamil
اردوUrdu
Searching...
SoBrief
The OKRs Field Book

The OKRs Field Book

A Step-by-Step Guide for Objectives and Key Results Coaches
Make OKRs a practical team skill, with a rollout that turns early cycles into better priorities.
by Ben Lamorte 2021
4.43
116 ratings
Listen
Immersive
V2.3
Amazon Kindle Audible
Try Full Access for 3 Days
Unlock listening & more!
Continue

Key Takeaways

Treat OKRs as coached critical thinking, not a quarterly paperwork ritual.

The goal is better thought. OKRs coaching is a structured partnership that helps people clarify priorities, define measurable progress, and learn from results. It is not simply a consultant handing over a set of recommended goals. The coach mainly asks questions, helping a team discover what matters and why, while still offering guidance when people need help making goals measurable or clear.

The book’s origin story makes the distinction vivid. A vice president of engineering wanted to help Sales, but the phrase did not say how engineering could contribute. Questions about successful sales support led the team to define and track a technical pass rate, revealing a concrete way to improve collaboration. The value came from sharpening the team’s thinking, not supplying its answer.

Analysis

The strongest claim here is that a goal-setting system can function as a conversation protocol. A well-formed question exposes assumptions that a polished template can conceal, such as whether one department can actually influence another team’s result. The coach’s restraint matters: too much advice turns inquiry into compliance, while too little expertise leaves teams stuck in vague language. The practical test is whether participants leave with clearer ownership and a better understanding of the problem, not merely a completed form.

Set deployment rules only after leaders can explain why OKRs matter now.

Purpose shapes the rules. Deployment parameters are the organization’s agreed answers to practical questions such as which groups set OKRs, how many they create, how progress is scored, and how goals relate to performance reviews. These choices should follow from a clear reason for adopting OKRs, not from imitation or a list of fashionable benefits.

A leader might introduce OKRs to reduce silos after rapid growth, to narrow an overload of priorities, or to make strategy more visible to employees. Each reason suggests a different rollout. A company seeking focus might start teams with one objective; a company seeking clearer strategy might begin with company-level goals and communicate them broadly. The coach should test whether the stated reason is understood by leaders and the teams expected to use the process.

Analysis

This is a useful change-management principle: rules gain legitimacy when people can see the problem they are meant to solve. It also prevents framework adoption from becoming corporate theater, where the organization borrows a famous company’s language without addressing its own bottleneck. The rationale needs to be specific enough to guide choices, but not so broad that it promises every possible benefit. If the reason for adoption cannot distinguish one design choice from another, it is not yet useful context.

Pilot with a small group, then learn through two complete cycles.

A launch is not implementation. The book organizes an engagement around three kinds of work: agreeing how the program will operate, teaching people through practical workshops, and coaching teams through their recurring goal cycle. It recommends an eight-to-twelve-month engagement, often long enough to complete two cycles, rather than a one-off training day.

The first cycle is a learning period. A small pilot group can test goal wording, check-in habits, and the organization’s scoring rules before leaders expand the program. The second cycle applies those lessons and can support broader adoption. The work also needs clear internal roles: a project lead to coordinate the program, an executive sponsor to explain its purpose and provide authority, and internal coaches to help teams sustain the practice after outside support ends.

Analysis

The two-cycle recommendation recognizes that adoption is a capability, not an announcement. Teams need to experience the full loop before they can judge whether the mechanics fit their work. A pilot also makes failure cheaper and more informative, especially when the company is still deciding how to define teams or review progress. The caution is that a pilot can become a permanent showcase rather than a route to learning. Its value depends on recording what changed and making an explicit decision about what to scale.

Build OKRs around real work dependencies, not just reporting lines.

Teams follow the work. An org chart is convenient, but it may split people who must coordinate to produce an outcome. The book describes alternatives: combine highly dependent functions into one goal-setting group, use existing cross-functional squads, or form a temporary group around a priority that has no natural owner.

One technology company merged product and engineering after discovering that nearly every product goal depended on engineering. Another company organized squads around customer segments rather than departments. In both cases, the point was to make shared work visible instead of pretending that separate reporting lines meant separate results. The right team structure depends on why the organization adopted OKRs and where its dependencies actually lie.

Analysis

This design choice treats organizational structure as a hypothesis rather than a fact of nature. If work repeatedly crosses departmental boundaries, goals that stop at those boundaries can institutionalize the very silos the company wants to reduce. Yet cross-functional teams are not automatically better: they can blur decision rights or add coordination overhead if members do not share a meaningful outcome. A useful design question is whether the proposed group can make and act on decisions together, not merely whether its members depend on one another.

Choose a few outcomes, and leave routine monitoring to health metrics.

Focus is selective by design. OKRs are meant to identify areas for near-term improvement, not inventory every duty or metric. The book’s general advice is to start with at most a few objectives and a small number of key results. A metric that matters but is already at an acceptable level can remain a health metric: something monitored, but not the current improvement priority.

The accounts-receivable example shows the difference. A finance team had many dashboard measures, but chose to focus on reducing the dollars overdue by at least sixty days. Its baseline was $24 million, and its target was to cut that amount in half. The goal gave another team a reason to create a focused report that identified large accounts approaching that overdue category.

Analysis

The distinction between improvement and maintenance protects attention from being swallowed by dashboards. It also makes the decision to prioritize explicit: a metric can be important without being a goal for this cycle. The accounts-receivable example shows how a clear target can prompt useful cooperation across functions. One caution is that a narrow target can invite local optimization. Teams should check whether reducing one visible measure shifts costs elsewhere, such as harming customer relationships or delaying other necessary work.

Score goals to manage expectations, not to grade people or pay bonuses.

Scoring should clarify ambition. The book compares several scoring approaches, from simply marking a result achieved or not to using a scale that reflects progress or confidence. Its preferred approach, Aspirational with Pre-Scoring, defines a stretch outcome alongside a likely commitment and a difficult but realistic target. The conversation helps a team distinguish what it can reliably deliver from what would count as exceptional progress.

A product launch goal exposed a hidden constraint: the legal team had not approved the product for sale. A discussion of likely progress surfaced this dependency before the team promised paying customers. Scores can also be used during a cycle to predict whether a result remains achievable. The book warns against using scores themselves to determine bonuses, since that can encourage safe targets and defensive behavior.

Analysis

A score is most useful when it changes a conversation or a decision. Predefining levels forces teams to discuss uncertainty and dependencies before a deadline turns them into excuses. This is especially valuable when leaders distinguish ambition from commitment rather than treating every target as a contract. Still, numeric scales can create false precision: a confidence estimate is a judgment, not a forecast with laboratory accuracy. The number should open inquiry about evidence and risk, not close debate about whether a person performed well.

Align through explanation and dialogue, not cascading copied goals.

Alignment is negotiated context. The book rejects a mechanical cascade in which a senior key result simply becomes a lower-level objective. That approach can make teams copy goals without asking how their work contributes. Instead, teams should use higher-level priorities as context, explain why their own objective matters now, and discuss dependencies with leaders and partner teams.

The book describes Huawei’s approach: team members discuss goals with their leader, individuals then align their work through conversation, and the completed goals are made visible in a shared system. A person whose work does not map neatly to a team goal may still be contributing by maintaining an important metric or completing required compliance work. Alignment is therefore a reasoned connection, not a diagram of arrows.

Analysis

This approach distinguishes coherence from uniformity. A company can share direction without forcing every team to express that direction in identical language or pretend that every valuable task maps directly to a headline goal. The requirement to explain connections makes alignment inspectable: leaders can ask whether a team’s rationale is credible rather than checking whether its wording matches the level above. The tradeoff is that conversation takes time and depends on leaders listening seriously, not treating the discussion as a ceremonial approval step.

Teach by drafting real goals; reserve theory for a short runway.

Practice makes the framework concrete. The book divides training into a brief explanation of OKRs and an interactive application where participants work on their own goals. Workshops can focus on senior-level goals, on training internal coaches, or on several teams drafting together. In each case, the organization’s agreed deployment rules provide the local context.

An executive workshop in a home-building company began with a broad goal about developing people. Drafting results revealed a more specific issue: leaders had no shared definition of a high-performing sales manager. The agenda changed, and the group spent its time clarifying that standard rather than forcing progress through every planned topic. This is a key coaching skill: protect useful discussion, even when it means abandoning the slide schedule.

Analysis

The workshop logic resembles learning by doing: people understand a method more deeply when they apply it to a live problem and receive feedback. The executive example also shows that a detour can be the point, if it exposes an unresolved decision. Yet flexibility should not become an excuse for unfocused meetings. A facilitator still needs a clear purpose, time boundaries, and a way to capture what the group has learned. The best agenda is structured enough to help, but not so rigid that it blocks discovery.

Make every cycle end with evidence, learning, and a revised priority.

Close the loop deliberately. The OKRs cycle has three recurring activities: define and align goals, check progress during the work, and review results to inform the next round. Check-ins should fit into existing team routines where possible. At least one mid-cycle review helps teams avoid the familiar failure of publishing goals and then forgetting them.

At cycle end, teams record final results, what they learned, and whether each result should continue, change, or stop. A partner-success team aimed to increase the number of retail partners, then learned that signing partners was easier than getting them to sell. The team shifted its next goal toward partner quality. A shared OKRs tracker can hold the goals, progress updates, scores, and lessons in one place.

Analysis

The cycle makes measurement valuable by connecting it to adaptation. A result below target is not automatically a failure if it reveals that the original metric captured the wrong behavior; in the partner example, counting sign-ups obscured whether partners created value. Conversely, teams should not romanticize learning to excuse repeated lack of progress. A sound review asks both what the evidence taught and whether the effort produced worthwhile impact. The tracker supports memory, but it cannot replace an honest conversation about what changed and why.

Analysis

The book’s most consequential argument is that OKRs succeed or fail less as a goal format than as an organizational practice. Its practical architecture reflects that claim: leaders establish the conditions for use, people learn by drafting real goals, and teams revisit progress and adapt. This is a stronger account than the popular idea that visibility alone creates alignment. Shared goals help only when teams can question their meaning, negotiate dependencies, and explain how local work contributes.

The approach also contains a productive tension between focus and completeness. A small set of priorities makes communication easier, but organizations still depend on maintenance work, compliance tasks, and exploratory efforts that may not fit cleanly into measurable outcomes. The distinction between key results and health metrics offers one answer, though it requires disciplined judgment. Otherwise, leaders may privilege what is easy to count over work whose value is delayed, relational, or uncertain.

A further risk lies in the social use of scores. The book warns against tying scores to compensation, because targets can become conservative and teams may defend results instead of learning. This is consistent with a broader organizational problem often called Goodhart’s law: once a measure becomes a target, people may optimize the measure rather than the underlying purpose. Scoring can still be useful, but only when paired with qualitative discussion of quality, dependencies, and unintended consequences.

The book’s coaching stance is therefore central, not decorative. Inquiry can surface hidden assumptions, but it does not eliminate power differences. Employees may hesitate to challenge a leader’s objective even in a workshop designed to encourage participation. Executive sponsorship must include permission to disagree, not just enthusiasm for the process. The strongest implementation is one where goals are visible, limited, and revisable, and where the conversation around them is more candid than the reporting system it replaces.

Summary in 30 Seconds
Start with a clear reason for adopting OKRs, then test the process with a small group over two full cycles, often within an eight-to-twelve-month engagement. Keep objectives few, and track stable responsibilities separately as health metrics. Build goals around shared work, not just reporting lines. Use scores to discuss expectations and progress, never to set bonuses. Regular check-ins and cycle reviews turn results into lessons and revised priorities.
Contains spoilers

Last updated:

Report Issue

Review Summary

4.43 out of 5
Average of 116 ratings from Goodreads and Amazon.

The OKRs Field Book receives overwhelmingly positive reviews (4.43/5) for its practical, actionable guidance on implementing OKRs in organizations. Readers praise its specific examples, workshop agendas, coaching questions, and real-world case studies. Many reviewers note it surpasses other OKR books in practical implementation value, helping them avoid trial-and-error approaches. The book covers deployment coaching, training, and cycle coaching phases with step-by-step instructions. Coaches and practitioners find it essential for successful OKR adoption, particularly valuing the change management aspects and flexibility to adapt to different organizational contexts.

Your rating:
4.62
60 ratings
Want to read the full book?

Glossary

OKRs coaching

Guided goal-setting practice

A structured partnership that helps an organization define how it will use objectives and key results, teach teams to apply them, and support teams through repeated goal cycles. The coach relies heavily on questions that help clients clarify priorities and measure progress, while also offering practical guidance when the organization needs help with implementation.

Deployment Parameters

Rules for using OKRs

The agreed decisions that establish how an organization’s OKRs program will operate. They address matters such as which levels or teams set goals, how many goals are appropriate, how results are scored, the length of a cycle, and how OKRs relate to performance reviews and existing metrics. These decisions should reflect the organization’s reason for adopting OKRs.

OKRs Cycle

Recurring goal-and-learning loop

The recurring process of defining and aligning objectives and key results, checking progress while work is underway, and reviewing results to capture learning and shape the next period’s goals. The cycle is designed to keep goals connected to daily work rather than leaving them untouched after publication.

Health Metric

Metric monitored, not improved

A measure that an organization continues to watch because it matters, but that is not the current focus for improvement. A metric may be a key result during one period and become a health metric once it reaches an acceptable range. If it worsens, the organization may choose to make it a priority again.

Baseline Key Result

Establishes an unknown starting value

A key result used when a team needs to measure an important metric but does not yet know its current value. It establishes the starting point needed for a future goal to improve that metric. A useful baseline result specifies how much data or what measurement period is required, rather than vaguely promising to create a baseline.

Aspirational with Pre-Scoring

Sets ambition before work begins

A scoring approach in which a key result is written as a stretch outcome and the team defines expected commitment and target levels in advance. The discussion clarifies what the team considers reliably achievable, difficult but plausible, and exceptional progress. It is intended to align expectations and expose dependencies before the cycle is underway.

OKRs Tracker

Shared record of the cycle

A single location where an organization publishes its OKRs and records progress updates, scores, and lessons from the cycle. It may be a spreadsheet or a dedicated software tool. The tracker gives teams a common reference point, but it is meant to support discussion rather than substitute for it.

Left-Hand Column (LHC) Exercise

Reflects on unspoken thoughts

A reflection technique used after a conversation or coaching session. The participant records what was said alongside thoughts and feelings that remained unspoken, then examines assumptions and missed opportunities. In the book, coaches use it to study moments when a session stalled or produced a breakthrough and to improve their questioning.

About the Author

Ben Lamorte is the founder of OKRs.com and an internationally recognized OKRs coach who has consulted with major organizations including eBay, CareerBuilder, Zalando, Sears Holding, and Booking.com. He co-authored his first book, "Objectives and Key Results: Driving Focus, Alignment, and Engagement with OKRs," with Paul Niven, published by Wiley in 2016. Ben holds a graduate degree in Management Science & Engineering from Stanford University, specializing in Decision Analysis and Organizational Dynamics. He resides in Marin County with his wife Ariana, thirteen-year-old son Toby, and nine-year-old daughter Lizzie, who aspires to be a rockstar and wants a pet.

Download PDF

To save this The OKRs Field Book summary for later, download the free PDF. You can print it out, or read offline at your convenience.
Download PDF
File size: 0.31 MB     Pages: 15

Download EPUB

To read this The OKRs Field Book summary on your e-reader device or app, download the free EPUB. The .epub digital book format is ideal for reading ebooks on phones, tablets, and e-readers.
Download EPUB
File size: 1.39 MB     Pages: 18
Want to read the full book?
Follow
Listen1 mins
Home
Swipe
Library
Get App
Try Full Access for 3 Days
Listen, bookmark, and more
Compare Features Free Pro
📖 Read Summaries
Read unlimited summaries. Free users get 3 per month
🎧 Listen to Summaries
Listen to unlimited summaries in 40 languages
—
❤️ Unlimited Bookmarks
Free users are limited to 4
—
📜 Unlimited History
Free users are limited to 4
—
📥 Unlimited Downloads
Free users are limited to 1
—
Risk-Free Timeline
Today: Get Instant Access
Listen to full summaries of 26,000+ books. That's 12,000+ hours of audio!
Day 2: Trial Reminder
We'll send you a notification that your trial is ending soon.
Day 3: Your subscription begins
You'll be charged on Nov 25,
cancel anytime before.
Consume 2.8× More Books
2.8× more books Listening Reading
Our users love us
1M+ readers
Trustpilot Rating
TrustPilot
4.6 Excellent
This site is a total game-changer. I've been flying through book summaries like never before. Highly, highly recommend.
— Dave G
Worth my money and time, and really well made. I've never seen this quality of summaries on other websites. Very helpful!
— Em
Highly recommended!! Fantastic service. Perfect for those that want a little more than a teaser but not all the intricate details of a full audio book.
— Greg M
Save 62%
Yearly
$119.88 $44.99/year/yr
$3.75/mo
Monthly
$9.99/mo
Start a 3-Day Free Trial
3 days free, then $44.99/year. Cancel anytime.
Unlock a world of fiction & nonfiction books
26,000+ books for the price of 2 books
Read any book in 10 minutes
Discover new books like Tinder
Request any book if it's not summarized
Read more books than anyone you know
#1 app for book lovers
Lifelike & immersive summaries
30-day money-back guarantee
Download summaries in EPUBs or PDFs
Cancel anytime in a few clicks

Why one summary?

Scanner
Find a barcode to scan

⭐
⭐
⭐
We have a special gift for you
Open
38% off
DISCOUNT FOR YOU
⭐
⭐
⭐
$79.99
$49.99/year
Only $4.16 per month
Continue
2 taps to start, super easy to cancel
Settings
General
Widget
Loading...