--- title: "Why Great OKRs Start With Better Strategic Conversations" url: "https://www.collective-genius.com/insights/why-great-okrs-start-with-better-strategic-conversations-mqq2wv0m" author: "Jeff James Martin" organization: "Collective Genius" date_published: "2024-11-19T08:00:00.000Z" date_modified: "2026-07-10T17:35:57.560Z" reading_time_minutes: 11 cluster: "Operating Rhythm" tags: ["OKRs", "Strategic Planning", "Operating Rhythm", "Team Alignment", "Accountability", "Organizational Visibility", "Organizational Intelligence"] description: "Great OKRs start with better strategic conversations. Learn why discussing how objectives will be achieved creates clearer, more actionable key results and stronger organizational execution." --- # Why Great OKRs Start With Better Strategic Conversations Great OKRs start with better strategic conversations because teams need to understand how an objective will be achieved before they can define strong key results. The best OKR process clarifies strategy, assumptions, dependencies, ownership, and visible outcomes before execution begins. Most organizations try to improve their OKRs by improving the wording. They debate whether objectives should be more inspiring. They adjust key results to make them more measurable. They ask whether the OKRs are too ambitious, too easy, too broad, or too tactical. These details matter, but they often miss the deeper issue. Weak OKRs usually begin before the writing starts. They begin with weak strategic conversations. A team can write a clean objective and measurable key results, but if the conversation underneath the OKR is shallow, the OKR will still be weak. The objective may sound important, but the team may not understand why it matters. The key results may be measurable, but they may not represent meaningful progress. The team may agree to the OKR, but still disagree about how the work should actually be achieved. This is one of the most common reasons OKRs fail. Organizations move too quickly from “What do we want to accomplish?” to “How will we measure it?” without spending enough time on the most important question: How are we actually going to achieve this objective? That conversation is where the quality of the OKR is created. Great OKRs do not start with templates. They start with better thinking. They start with better strategic conversations. ## OKRs Are Only as Strong as the Conversation Behind Them OKRs are often treated as a writing exercise. A team sits in a planning session, reviews a company priority, writes an objective, and creates two or three key results. If the wording is clear and the metrics are measurable, the OKR is considered good. But measurable does not always mean meaningful. A key result can be measurable and still fail to guide execution. It can be specific and still fail to capture the real work required. It can look clean on paper and still leave the team unclear on what must change. This happens when the team has not gone deep enough into the objective. Why does this objective matter now? What is preventing us from achieving it today? What must change in the business for this objective to become real? Which teams need to coordinate? What trade-offs are required? What would success look like if we could actually see it? What are we assuming? What are we avoiding? These are not administrative questions. They are strategic questions. They help the team understand the work behind the outcome. A strong OKR is the result of that conversation. The objective captures the priority. The key results capture the visible evidence that the priority has been achieved. But the discussion creates the quality. Without the discussion, OKRs become language. With the discussion, OKRs become execution. ## The Missing Step Is Discussing the How Many organizations skip the most valuable part of OKR creation. They define the objective. Then they immediately define the key results. The missing step is the discussion of how the objective will be achieved. This step matters because the path to the objective determines what the key results should be. If the objective is to improve customer retention, the team first needs to understand why retention is not where it should be. Is the issue poor customer fit? Weak onboarding? Product gaps? Slow time to value? Lack of executive sponsorship? Support quality? Pricing expectations? Customer education? Each answer leads to different key results. If the team skips that discussion, the key results may measure the wrong things. The same is true for revenue growth, operational efficiency, product adoption, employee engagement, margin improvement, or market expansion. The objective may be clear, but the pathway to achieving it is what determines whether the OKR becomes actionable. This is why strategic conversation matters so much. The best OKR conversations do not stop at what the team wants. They explore what the team believes must happen. That conversation reveals assumptions, constraints, dependencies, risks, and trade-offs. It allows teams to identify whether the objective belongs to one team, requires cross-functional ownership, or should move to a sub-team. It helps leaders understand where the organization must coordinate. The how conversation turns an objective into an execution plan. ## Strategy Is the How, Not Just the Goal One of the reasons OKRs become weak is that organizations confuse goals with strategy. Goals describe what the organization wants. Strategy describes how the organization intends to achieve it. OKRs sit between strategy and execution. They translate strategic intent into measurable progress. But when the strategic conversation is missing, OKRs are often asked to do work they were never designed to do. An objective may say, “Improve enterprise customer retention.” That is a goal. The strategic question is how. Will the company improve retention by narrowing customer fit? By improving onboarding? By strengthening customer success capacity? By changing product packaging? By improving executive business reviews? By reducing implementation friction? By increasing product usage? Each path reflects a different strategy. Each path requires different teams. Each path creates different key results. This is why OKRs should be aligned to the one-year plan. The one-year plan gives the organization a strategic context for what matters most and why. The OKR conversation then helps teams define how their part of the organization will contribute. When strategy is missing, OKRs become a list of desired outcomes. When strategy is clear, OKRs become a mechanism for coordinated execution. ## Better Conversations Create Better Key Results The quality of key results improves when teams discuss the objective deeply enough. A weak key result may measure activity. A stronger key result measures progress. A weak key result may track whether work happened. A stronger key result shows whether the objective became real. A weak key result may be vague. A stronger key result is visible when completed. This distinction matters. If a team cannot define what a key result looks like when it is done, the key result is probably not strong enough. A key result should be clear enough that leaders and teams can recognize whether meaningful progress has occurred. For example, a team might write, “Improve cross-functional alignment.” That may describe a real need, but it does not yet define a visible result. What would improved alignment look like? Faster decisions? Fewer unresolved dependencies? Clearer ownership across initiatives? Reduced conflict between sales and product? Better shared understanding of priorities? The answer depends on the conversation. A better key result might define a visible change in how the system works. The team might commit to resolving ownership for the top cross-functional initiatives, reducing decision delays on high-priority work, or creating shared readiness criteria before launch. The key result becomes stronger because the team understands the real issue. This is why the conversation must precede the metric. The metric should express understanding. It should not replace it. ## Strategic Conversation Reduces Misalignment Misalignment often begins quietly. People nod in agreement during planning, but they leave the room with different interpretations of what was decided. One person believes the priority is growth. Another believes it is profitability. One team believes speed matters most. Another believes quality matters most. One department believes the objective requires product changes. Another believes it requires customer process changes. The OKR may appear aligned, but the understanding is not. Strategic conversation reduces this risk. When teams discuss how an objective will be achieved, differences become visible earlier. Leaders can identify competing assumptions. Teams can clarify dependencies. Trade-offs can be discussed before execution begins. This is especially important in Team-of-Teams organizations. As companies grow, outcomes become more cross-functional. A single objective may require several teams to coordinate around a shared result. Without deeper conversation, each team may write OKRs from its own point of view. With deeper conversation, teams can understand how their work connects. This is why great OKRs are not created by one person in isolation. They are created through dialogue. The dialogue strengthens alignment because it forces teams to test whether they actually understand the objective in the same way. Alignment is not agreement with words. Alignment is shared understanding of direction, trade-offs, ownership, and action. ## The Delete, Move, and Combine Method Depends on Conversation The delete, move, and combine method works because it forces strategic discussion. When teams propose objectives, not every objective should survive. Some objectives should be deleted because they are not important enough, not timely enough, or not connected strongly enough to the one-year plan. Some objectives should be moved because they belong to a different level. A company-level objective may actually belong to a department. A department objective may belong to a sub-team. A proposed objective may be better treated as an initiative. Some objectives should be combined because multiple teams are describing related work that belongs together. This process cannot be done well without conversation. Leaders and teams need to understand why the objective exists, what outcome it supports, who should own it, and how it connects to the broader plan. The discussion helps reveal whether the objective is real strategy, functional preference, duplicated effort, or tactical work. The value of delete, move, and combine is not just a cleaner list of OKRs. The value is the alignment created through the process. Teams learn what matters most. Leaders clarify trade-offs. Ownership becomes more accurate. Cross-functional dependencies surface earlier. The organization becomes more disciplined about what deserves focus. That discipline is one of the most important ingredients in better OKRs. ## Operating Rhythm Gives the Conversation a Place to Continue Great OKR conversations do not end when the OKRs are written. Execution creates new information. Assumptions are tested. Dependencies appear. Customer signals change. Capacity constraints emerge. Teams discover that some parts of the objective are harder than expected. This is why OKRs need Operating Rhythm. Operating Rhythm creates recurring structure for reviewing progress, surfacing obstacles, making decisions, reinforcing accountability, and learning from execution. It gives the organization a way to continue the strategic conversation throughout the quarter or year. Without Operating Rhythm, OKRs become static. They are written, shared, and then slowly disconnected from daily work. Teams return to urgency. Leaders revisit priorities informally. Decisions happen outside the system. Learning remains local. With Operating Rhythm, OKRs stay alive. Teams review whether progress is real. Leaders discuss whether assumptions are holding. Cross-functional dependencies are surfaced. Key results become a basis for learning, not just reporting. This is why the OKR process should not be separated from the operating system. The writing session creates initial clarity. Operating Rhythm sustains and improves that clarity over time. ## Better OKRs Require Visibility Visibility is essential to OKR quality. Teams need to see how their objectives connect to the company one-year plan. They need to see how their work connects to other teams. Leaders need to see whether objectives are aligned, duplicated, overloaded, or disconnected. Without visibility, OKRs remain trapped inside teams. A department may create a strong OKR, but another department may unknowingly create a conflicting OKR. A team may depend on another team’s work, but the dependency may not surface until execution is already underway. Leaders may believe the organization is aligned because every team has OKRs, but no one has examined the full system. In Peak OS, OKRs are visible across the organization. This matters because visibility turns OKRs into a coordination tool. Teams can see where collaboration is required. Leaders can identify where objectives overlap. Sub-teams can understand how their work supports team priorities. The organization can detect misalignment earlier. Visibility also improves the strategic conversation. When everyone can see the system, the conversation becomes more accurate. Teams are not discussing objectives in isolation. They are discussing how the organization will execute together. That is where OKRs become more powerful. ## OKRs Should Create Organizational Learning A strong OKR system does more than track progress. It helps the organization learn. At the end of a cycle, the question should not only be, “Did we hit the key results?” The deeper questions are: What did we learn about the objective? What did we misunderstand? Where did execution slow? Which dependencies were underestimated? Which assumptions were wrong? What should change in our operating system? What should change in next cycle’s planning? This is where Organizational Intelligence becomes important. Organizational Intelligence is the ability of the organization to understand reality, recognize patterns, learn from experience, improve decisions, and adapt execution over time. OKRs can support this capability if they are used as part of a learning system. When teams review OKRs only as performance targets, they miss much of the value. When teams review OKRs as learning tools, they improve future execution. A missed key result may reveal weak ownership, poor visibility, unrealistic capacity assumptions, delayed decisions, or cross-functional friction. A successful key result may reveal a repeatable pattern the organization should scale. The OKR conversation should create learning before, during, and after execution. This is how OKRs become part of continuous improvement. ## Why Peak OS Starts With the Conversation Peak OS treats OKRs differently because it treats execution differently. OKRs are not a standalone goal framework. They are part of a larger organizational execution system. The process begins with the one-year plan. Each team creates its own one-year plan. Teams discuss how objectives will be achieved. Proposed objectives are refined through delete, move, and combine. Key results are created only after the team understands what success must look like. OKRs are made visible across the organization. Operating Rhythm keeps them active. Organizational Intelligence helps the company learn from execution. This approach makes the conversation central. The conversation is not a soft step. It is the work. It is where strategy is clarified. It is where alignment is tested. It is where ownership becomes accurate. It is where key results become actionable. It is where cross-functional dependencies become visible. Peak OS recognizes that the quality of execution depends on the quality of thinking that precedes it. Better OKRs start with better strategic conversations because teams cannot execute clearly if they have not first understood the work clearly. ## Better Conversations Create Better Execution Organizations often want better OKRs because they want better results. But better results do not come from better wording alone. They come from better alignment, stronger thinking, clearer ownership, more visible outcomes, and a deeper understanding of how work will be achieved. That begins with conversation. The best OKR conversations slow down long enough to create clarity before speeding up execution. They help teams understand the one-year plan. They help leaders test assumptions. They help teams clarify how objectives will be achieved. They help create key results that are visible and actionable. They help the organization narrow its priorities and coordinate across teams. In fast-moving environments, this matters even more. Speed without clarity creates drift. Productivity without alignment creates fragmentation. Metrics without understanding create false confidence. Great OKRs help organizations move faster because they create shared understanding before execution begins. That is why great OKRs start with better strategic conversations. ## Related Insights What Is Peak OS? [https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx](https://www.collective-genius.com/insights/what-is-peak-os-mq7jqhdx) What Is Organizational Execution? [https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p](https://www.collective-genius.com/insights/what-is-organizational-execution-mq4rcx9p) What Is Organizational Intelligence? [https://www.collective-genius.com/insights/what-is-organizational-intelligence-mq7jys1i](https://www.collective-genius.com/insights/what-is-organizational-intelligence-mq7jys1i) What Is a Business Operating System? [https://www.collective-genius.com/insights/what-is-a-business-operating-system-mq4qmt39](https://www.collective-genius.com/insights/what-is-a-business-operating-system-mq4qmt39) What Is Operating Rhythm? [https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur](https://www.collective-genius.com/insights/what-is-operating-rhythm-mq4qywur) ## Key Takeaways - Great OKRs begin before the writing starts. - Teams need to discuss how the objective will be achieved. - Strategy is the how, not just the goal. - Better conversations create better key results. - Visible key results improve accountability. - Operating Rhythm keeps OKRs alive during execution. - Peak OS uses OKRs as part of a broader organizational execution system. ## Frequently Asked Questions ### Why do great OKRs start with better strategic conversations? Great OKRs start with better strategic conversations because teams need to understand why the objective matters, how it will be achieved, what trade-offs are required, and what visible results should define success. ### Why do weak OKRs happen? Weak OKRs often happen when teams move too quickly from objectives to metrics without discussing strategy, assumptions, dependencies, ownership, and execution path. ### What is the most important question to ask before writing key results? The most important question is: how are we actually going to achieve this objective? The answer helps teams define stronger and more actionable key results. ### Why is discussing the “how” important for OKRs? Discussing the how helps teams understand the real work required, identify obstacles, clarify dependencies, and write key results that reflect meaningful progress. ### What makes a key result strong? A strong key result is clear, visible, actionable, and tied to meaningful progress. The team should be able to describe what the key result looks like when completed. ### How does Operating Rhythm support OKRs? Operating Rhythm keeps OKRs active by creating recurring opportunities to review progress, surface issues, make decisions, and learn from execution. ### How does visibility improve OKR alignment? Visibility allows teams to see how their OKRs connect to the company plan, other teams, shared dependencies, and cross-functional priorities. ### How does Peak OS improve OKR conversations? Peak OS improves OKR conversations by aligning OKRs to the one-year plan, creating team-level plans, using delete, move, and combine, making OKRs visible, and reviewing progress through Operating Rhythm. Source: https://www.collective-genius.com/insights/why-great-okrs-start-with-better-strategic-conversations-mqq2wv0m