The OKRs Field Book

1. OKRs Coaching is a Structured, Phased Engagement

Partnering with clients in a thought-provoking, creative, and structured process over three phases.

Structured engagement. Effective OKRs coaching follows a proven, multi-phase structure, typically spanning eight to twelve months. This extended duration, often encompassing two complete OKRs cycles, is crucial for embedding the methodology and ensuring sustained success, moving beyond initial enthusiasm to deep integration. The "crawl-walk-run" approach is key, starting small and scaling gradually.

Three distinct phases. The coaching engagement is divided into three critical phases, each with specific objectives and a shifting role for the coach.

• Phase 1: Deployment Coaching focuses on defining the program's foundational parameters.
• Phase 2: OKRs Training involves interactive workshops to build a shared understanding.
• Phase 3: OKRs Cycle Coaching guides clients through the iterative process of setting, monitoring, and reflecting on OKRs.

Long-term partnership. Unlike short-term consulting, OKRs coaching emphasizes an ongoing relationship, ensuring clients not only understand OKRs but also successfully implement and adapt them. This commitment allows for continuous learning and refinement, making the coach an invaluable partner in the client's journey to achieve measurable contributions and organizational learning.

2. Start with "Why Now?" to Define Deployment Parameters

The very first question you should address with your client is “Why OKRs?”

Foundational clarity. Before diving into implementation, it is imperative to establish a clear and compelling "why" for adopting OKRs. This initial step, often overlooked, ensures that the organization's leadership can articulate the specific problem OKRs are intended to solve, fostering genuine buy-in and preventing the initiative from being perceived as a mere trend or an additional burden.

Ten universal parameters. Once the "why" is established, the coach guides the client through defining ten universal deployment parameters that form the bedrock of their OKRs program. These parameters address critical operational questions, ensuring consistency and clarity across the organization.

• Level of OKRs (company, team, individual)
• Number of OKRs to set
• Scoring methodology and progress updates
• OKRs cycle length
• Types of key results (metric, baseline, milestone)
• Tools for drafting, publishing, and tracking
• Relationship to performance reviews
• Distinction from KPIs
• Alignment mechanisms
• Balance of top-down and bottom-up input

Contextualizing deployment. The client's unique motivation for OKRs directly informs the selection and customization of these parameters. For instance, a company seeking cross-functional alignment might prioritize merging dependent teams for OKR setting, while one focused on strategic communication might emphasize company-level OKRs. This tailored approach ensures the OKRs framework genuinely supports the client's specific organizational goals.

3. Strategic Team Definition Drives Cross-Functional Alignment

Your client’s definition of “team” can make or break their OKRs program.

Beyond the org chart. While simple, defining OKRs teams purely based on the organizational chart often leads to increased silo effects, counteracting the goal of cross-functional alignment. Effective OKRs coaching encourages clients to think strategically about team structures that foster collaboration and shared ownership, rather than reinforcing existing hierarchical divisions.

Three approaches to team definition:

• Merge highly dependent teams: Combine functional areas like product and engineering into a single "ProdEng" team to address critical interdependencies directly.
• Leverage existing cross-functional squads: If the client already operates with customer-centric or journey-based squads (e.g., "Buyer Squad," "Checkout Squad"), align OKRs with these established collaborative units.
• Define cross-functional teams based on top-level OKRs: Allow top-level objectives to organically lead to the formation of new, cross-functional teams dedicated to achieving those overarching goals, as seen with an "Organic Growth Squad."

Individual-level caution. Individual-level OKRs should be optional and introduced only after team-level success, if at all. Mandating individual OKRs often leads to task lists, increased overhead, and a potential diversion of focus from collective team objectives. Instead, individuals should engage by contributing to team OKRs, acting as internal coaches, or championing specific key results.

4. "Less is More" for Focused, Aspirational Key Results

A decade later, we find it unusual for a team to set more than three objectives.

Focus over breadth. The core principle of OKRs is to drive focus, and this is best achieved by limiting the number of objectives and key results. Overloading teams with too many OKRs dilutes effort and makes it difficult to prioritize what truly matters. The "less is more" mantra is paramount, encouraging teams to identify the most critical areas for improvement rather than attempting to map all work to OKRs.

Optimal OKR quantity. Most teams benefit from defining at most three objectives, each supported by no more than four key results. This narrow focus ensures that teams can dedicate sufficient attention and resources to achieve meaningful progress. While some support teams might define more OKRs to manage expectations and communicate non-priorities, this is an exception, not the rule.

Balancing internal and external. When defining objectives, teams should consider a balance between external, customer-facing goals and internal, process-improvement goals. This dual perspective ensures holistic growth and operational efficiency. Starting with just one or two objectives, perhaps one internal and one external, allows teams to build proficiency before expanding their scope in subsequent cycles.

5. Pre-Scoring Key Results Manages Expectations and Drives Learning

Nearly all of our clients find it valuable to establish scoring criteria up front.

Beyond binary outcomes. While simple, binary scoring (achieved/not achieved) can create a sense of failure for near misses and doesn't capture nuanced progress. The "Aspirational with Pre-Scoring" system, developed by Lamorte, offers a more sophisticated approach by defining three levels of achievement for each key result before the cycle begins. This proactive definition fosters clearer expectations and encourages stretch thinking.

The Aspirational with Pre-Scoring model:

• 0.3/Commit: A highly controllable level of progress, 90% likely to be achieved, requiring minimal external assistance. This is the team's commitment.
• 0.7/Target: A difficult but attainable level of progress, 50% likely to be achieved, representing the desired outcome.
• 1.0/Aspirational: An extremely ambitious outcome, 10-20% likely to be achieved, pushing the team beyond their comfort zone.

Driving critical conversations. Defining these pre-scores forces crucial conversations early in the OKRs cycle, aligning expectations and uncovering potential barriers. For example, an engineering manager might reveal legal constraints that make a proposed target unrealistic, leading to a more refined and achievable key result. This process transforms scoring from a mere evaluation tool into a powerful mechanism for communication, expectation management, and continuous learning.

6. OKRs are Distinct but Related to Performance Reviews and KPIs

OKRs and KPIs work together in tandem. A given KPI is a key result if it is the focus for near-term improvement.

Distinct but connected. OKRs and performance reviews, while related, must remain distinct. Conflating the two can discourage stretch goals and foster a culture of sandbagging. OKRs should not be the sole basis for calculating bonuses or formal performance evaluations. Instead, they serve as a framework for structured discussions within performance reviews, focusing on an individual's contribution to team objectives and their learning journey.

KPIs as building blocks. Key Performance Indicators (KPIs) are metrics that an organization tracks, but they lack a standard definition. A KPI becomes a key result when it is identified as a specific area for near-term, measurable improvement. If a KPI is already within an acceptable range and not a focus for immediate change, it is classified as a health metric, which is monitored but not actively driven by an OKR.

Strategic integration. The relationship between OKRs and KPIs is symbiotic:

• Metric key results often involve moving a specific KPI from X to Y.
• Milestone key results, while not directly moving a KPI, should be designed to impact a KPI in a future cycle.
• OKRs provide strategic context and focus for a subset of critical KPIs, elevating them to areas of active improvement.

This clear differentiation prevents redundancy and ensures that both systems contribute effectively to organizational goals without creating confusion or conflicting incentives.

7. OKRs Training is an Interactive Application, Not Just Theory

The best way to learn about OKRs is to get started on your actual OKRs.

Application-first approach. OKRs training workshops are most effective when they prioritize hands-on application over lengthy theoretical lectures. While a brief overview of OKRs history, definitions, and benefits is necessary, the majority of the workshop time should be dedicated to interactive exercises where participants apply the theory to draft and refine their actual OKRs. This "doing" aspect is crucial for internalizing the concepts.

Three types of workshops:

• Top-Level OKRs Workshop: Involves senior leadership to draft company-level OKRs, providing strategic context for the entire organization. Flexibility is key, allowing for impactful, unanticipated conversations.
• OKRs Expert Workshop: Designed to develop internal OKRs coaches, equipping them with the skills to support the program long-term. These workshops often use breakout groups where participants practice coaching each other.
• Team-Level OKRs Workshop: Focuses on drafting and refining OKRs for specific teams, ideally including members from multiple dependent teams to foster cross-functional alignment from the outset.

Customization and flexibility. Coaches should be prepared to customize workshop agendas and content to suit the client's specific needs and cultural nuances. This might involve combining elements from different workshop types or adapting to remote delivery formats. The goal is always to facilitate meaningful conversations and practical application, ensuring that participants leave with a tangible start on their OKRs.

8. The OKRs Cycle (Set, Check-in, Reflect) Ensures Continuous Impact

An effective coach ensures OKRs are integrated into daily work throughout the cycle.

Beyond initial excitement. While OKRs workshops generate enthusiasm, the true value of the framework lies in its continuous application through the OKRs cycle. A coach's role extends to guiding clients through three iterative steps, ensuring OKRs become an integral part of daily operations and drive sustained measurable progress.

Three steps of the OKRs cycle:

• Step 1: Set and Align OKRs: Involves refining initial drafts, ensuring vertical and horizontal alignment, and publishing final OKRs in a central "OKRs tracker." This step leverages the "7 steps for creating team-level OKRs" (mission, alignment check, objectives, draft KRs, convert tasks, challenge KRs, refine KRs).
• Step 2: Check-in and Monitor: Integrates OKRs into existing team meetings, avoiding the creation of excessive new processes. Champions provide regular updates on progress, predicted scores, blockers, and next steps, often using a structured template or set of questions. A formal mid-cycle review with multiple teams focuses on "big wins" and "big learns."
• Step 3: Reflect and Reset: This crucial learning phase involves documenting final scores, capturing insights from the cycle, and applying these learnings to draft OKRs for the next period. Key results are classified as "Keep," "Modify," or "Remove" based on their impact and relevance.

Learning as accountability. The coach holds the client accountable not just for achieving key results, but for the learning derived from the process. This continuous feedback loop strengthens the organization's goal-setting muscle and ensures that OKRs evolve to meet changing business needs.

9. Transform Tasks into Measurable Outcomes: The Essence of Key Results

What is the intended outcome of the task?

Output vs. outcome. A common pitfall in OKRs implementation is mistaking a list of tasks or activities for key results. Effective OKRs coaching focuses on guiding clients to articulate the intended outcome or measurable result of their efforts, rather than simply listing work output. This distinction is fundamental to ensuring OKRs drive meaningful progress.

Coaching for clarity:

• Questioning the "why": When presented with a task-like key result (e.g., "develop a demo"), the coach asks, "What is the intended outcome of developing this demo? How will we know it's a success?"
• Quantifying impact: The conversation shifts from merely completing an action to measuring its effect (e.g., "3 customers sign an agreement to purchase Product X after viewing the new Product X demo").
• Using pre-scoring: Defining commit, target, and aspirational levels for a key result helps clarify what constitutes a measurable outcome at different stages, even if the initial draft is a milestone.

Eight characteristics of effective key results. To ensure high-quality key results, coaches guide clients to refine them against eight criteria: "Key," Specific, Measurable, Results (not tasks), Clear, Aspirational, Scored, and Championed. This checklist helps transform vague intentions into precise, actionable, and accountable metrics that truly reflect progress towards an objective.

10. Embrace Inquiry and Reflection: The Coach's Core Skill

Great mentors and coaches tend to emphasize asking questions over giving advice.

Inquiry over advocacy. At its heart, OKRs coaching is an inquiry-based practice, not a consulting service that simply provides answers. The coach's primary role is to ask structured, thought-provoking questions that empower clients to discover their own solutions and insights. This approach fosters critical reflection, a cornerstone of effective OKRs implementation.

The power of questions:

• Mission questions: "Why do we exist? Whom do we serve?"
• Objective questions: "What is the most important area to focus on making measurable progress? Why now?"
• Key result questions: "How will we know the objective will be achieved? What is the intended outcome of this task?"
• Reflection questions: "What did we learn? How will we apply this learning?"

Critical reflection tools. Tools like the Left-Hand Column (LHC) exercise are invaluable for coaches to analyze their own thought processes during sessions, identifying breakthroughs and areas for improvement. By consistently asking "why" and "how," coaches facilitate a deeper understanding of the business and the OKRs process itself, enabling clients to make informed decisions and drive their own success.

11. Avoid Common Pitfalls: From Silos to "Set-it-and-Forget-it"

You need not hold your client accountable for achieving a given key result. However, as an OKRs coach, you do hold your client accountable for learning.

Proactive problem-solving. Successful OKRs implementation requires anticipating and actively mitigating common pitfalls that can derail progress. A skilled OKRs coach guides clients away from these traps, ensuring the framework delivers its intended benefits of focus, alignment, and engagement.

Key pitfalls and solutions:

• Siloed OKRs: Defining teams purely by org chart often reinforces silos.
  • Solution: Encourage cross-functional team definitions, merge dependent teams, or form squads based on top-level objectives.
• "Set-it-and-forget-it": Teams define OKRs but fail to integrate them into daily work or review progress.
  • Solution: Integrate OKRs into existing team meetings, establish a clear check-in cadence, and use tools like a "Working Agreement Canvas" to formalize commitment.
• Direct cascade: Mechanically turning higher-level key results into lower-level objectives, stifling bottom-up input and creativity.
  • Solution: Use higher-level OKRs as context, but encourage teams to develop their own objectives and key results through intentional dialogue, validating alignment through discussion, not rigid hierarchy.
• Too many OKRs/task lists: Overloading teams with objectives or writing key results as mere tasks.
  • Solution: Enforce "less is more" (1-3 objectives, 2-4 KRs), and coach teams to convert tasks into measurable outcomes, focusing on the "intended outcome" of activities.

Learning as the ultimate goal. The primary accountability for an OKRs coach is to ensure continuous learning throughout the cycle. By addressing these pitfalls proactively and fostering a culture of reflection and adaptation, coaches empower organizations to build a sustainable and impactful OKRs program.

Last updated: February 15, 2026