Please follow the attached instructions to implement the tracking code below....
Evaluation Kit
Request a Demo
Back to Blog

How AI Helps Executive Leaders Turn Strategy into Action Through OKRs 

Last Updated: June 16, 2026 | Part 3 of the Executive Series on How AI Helps Executive Leaders Develop and Execute a Winning Strategy 

By Jason Diamond Arnold, Director of Leadership Solutions, Inspire Software 

with Subject Matter Expert in AI Strategy and Executive Leadership, Chris Wollerman, CEO of Inspire Software 

Turning Strategy into Action Through OKRs 

A great strategy is only as valuable as an organization’s ability to execute it. Research on strategy execution has consistently shown that most strategies underperform not because they were wrong, but because they were never translated into goals that people across the organization understood, owned, and acted on[10]. 

In the AI era, that execution gap is now quantified. According to John Byron Hanby IV in The AI Strategy Blueprint, 97% of executives believe AI will transform their companies, yet only 4% generate substantial value from it[21]. This 97/4 gap is not a technology problem. It is the same execution problem that has slowed strategy for generations, now amplified by the speed and scale of AI — and it is the central executive challenge this series is written to address. 

Objectives and Key Results (OKRs) have emerged as one of the most widely adopted systems for closing that gap, popularized by John Doerr’s Measure What Matters[4] and refined by Paul Niven, Ben Lamorte[5], and Daniel Montgomery[7]. AI now accelerates every layer of the OKR system, from drafting corporate objectives to connecting departments and teams to coaching individuals through weekly execution. 

This article, Part 3 of the SCALE series, discusses how executive leaders can use AI to turn OKRs into measurable actions and why connect or cascade language distinguishes organizations that execute their strategy from those that only announce it.  

Executive Summary

This article is Part 3 of the executive series entitled, How AI Can Help Executive Leaders Develop and Execute a Winning Strategy. This article focuses on how to connect your strategy to the engine that powers it: Objectives and Key Results (OKRs). 

OKRs are not a new idea. The methodology traces back to Andy Grove at Intel in the 1970s and 1980s, was carried into Google by John Doerr, and has since been adopted across industries from manufacturing and healthcare to pharma and nonprofits[4]. AI has dramatically improved the speed and cost-effectiveness of doing OKRs well, from quality-checking objectives’ language to recommending lead measures for key results and providing coaching advice during meetings. 

Inspire Software[17] helps organizations align strategy with performance to promote effective execution and employee engagement through measurable outcomes. This article shows how executive teams can use AI to implement OKRs across corporate, department, team, and individual levels, connecting people to the strategy instead of just imposing it.

Why Are OKRs the Engine That Turns Strategy into Action? 

Most executive teams can produce a strategy. Many of those same teams are challenged to execute that strategy. Research from MIT Sloan Management Review found that, on average, less than a third of senior leaders below the C-suite could correctly identify even three of their own company’s top strategic priorities[10]. 

That is not a strategy problem. It is an execution problem; a failure to translate a strategy into a set of goals that the rest of the organization can see, internalize, and act on. Robert Kaplan and David Norton, the architects of the Balanced Scorecard, made the same point a generation earlier: the bottleneck is not strategy formulation, but the systems and language used to communicate and operationalize it[6]. 

OKRs, Objectives and Key Results, are the most widely adopted modern answer to that bottleneck. The objective is a qualitative description of what the organization is trying to accomplish and why. The key results are the quantitative outcomes that prove progress. 

“OKRs are simple to understand, but they are not so simple to do. There’s a lot more to using OKRs because when you’re really trying to implement a strategy, it goes beyond the framework of that strategy. It’s a lot about how you do it, how you communicate it, and how you assess your execution of what matters most to your company and your clients.” 

— Chris Wollerman, CEO, Inspire Software 

The OKR framework is easy to teach. The practice is where most organizations struggle, because doing OKRs well requires clarity at the top, alignment across the middle, ownership at the front line, and a steady cadence of team and one-to-one conversations that keep everyone accountable to the progress of strategy. AI has changed what is possible at each of those layers. 

How Do OKRs Differ from SMART Goals? 

OKRs are not in opposition to traditional SMART goals; many organizations use both. But the two frameworks were built for different purposes, operating on different time horizons, and answering different questions. Understanding the distinction matters because it shapes how executive teams use each framework to translate strategy into action. 

Different Origins, Different Purposes 

SMART goals were introduced in 1981 by George T. Doran in Management Review as a discipline for writing clearer managerial objectives. The acronym, Specific, Measurable, Attainable, Relevant, Time-bound, was designed to make any single goal more rigorous. It is a quality test for an individual goal statement, not a system for organizational alignment. 

OKRs trace back to Andy Grove at Intel in the 1970s, where they were designed as a system for aligning what an organization is trying to accomplish (the objective) with the measurable outcomes that prove progress (the key results). John Doerr brought OKRs from Intel to Google, where the framework became the operating discipline that scaled the company through hyper-growth[4]. Paul Niven and Ben Lamorte later codified the modern practice of OKRs in Objectives and Key Results: Driving Focus, Alignment, and Engagement with OKRs[5], and Niven’s follow-up book, OKRs for Dummies[20], which simplifies how OKRs operate across multiple levels of an organization. 

The structural difference is significant. SMART describes the shape of a well-formed goal. OKRs describe the structure by which qualitative ambition is held accountable through quantitative outcomes, and how that accountability connects upward to corporate strategy and downward to team and individual contributions. 

Ambition: Attainable vs. Stretch 

One of the most consequential differences is how each framework treats ambition. The “A” in SMART stands for Attainable, which by design encourages goals an individual or team is confident they can achieve. That makes SMART goals well-suited to performance commitments where reliability matters more than reach. 

OKRs were built on a different philosophy. Following the Intel and Google practice, OKRs are intentionally ambitious, often called stretch goals, with the expectation that achieving roughly 70 percent of a key result represents strong performance. Hitting 100 percent of every OKR typically signals that the targets were set too conservatively. The point is to encode aspiration into the goal-setting process itself, not just into the strategy. 

This is why mature OKR practitioners distinguish between committed OKRs (which the team is expected to fully deliver) and aspirational OKRs (where ~70 percent achievement is the success line). SMART goals do not natively carry this distinction. 

Cadence: Annual vs. Quarterly 

SMART goals were originally framed for annual managerial planning cycles. The “T” (Time-bound) typically anchors to fiscal or calendar year horizons in traditional management practice. 

OKRs operate on a quarterly cadence, with weekly check-ins and quarterly reviews. This faster rhythm is one of the most underappreciated reasons OKRs scaled in technology companies first; the cadence matched the speed at which those organizations needed to adapt. In an environment where market conditions, customer needs, and competitive pressures shift continuously, an annual goal-setting cycle becomes obsolete before the year is half over. The quarterly OKR cadence allows organizations to reset, reconnect, and re-execute four times a year. 

Connection to Strategy 

SMART goals can stand alone. A single SMART goal is complete in itself (specific, measurable, attainable, relevant, time-bound), and does not require anything above or below it to be valid. 

OKRs are explicitly designed to connect. Corporate OKRs cascade (or, as Inspire prefers, connect) to department OKRs, which connect to team OKRs, which connect to individual OKRs. Key Results at one level can contribute to an objective above, either directly (to calculate progress) or indirectly (to show related contributions). This vertical connection is what makes OKRs an execution system rather than just a goal-setting technique. As Niven and Lamorte emphasize[5], it is this alignment property, not the acronym itself, that gives OKRs their organizational power. 

A Side-by-Side Comparison of SMART & OKRs 

Dimension SMART Goals OKRs 
Origin George T. Doran, 1981, Management Review Andy Grove at Intel (1970s); popularized at Google by John Doerr (2018) 
Primary purpose Quality test for a single goal statement System for aligning strategy across an organization 
Structure Single well-formed goal (Specific, Measurable, Attainable, Relevant, Time-bound) Two-part: qualitative Objective + 2–5 quantitative Key Results 
Ambition level Attainable by design (reliability overreach) Often aspirational; 70% achievement signals strong performance on stretch OKRs 
Typical cadence Annual Quarterly, frequent check-ins 
Connection to strategy Can stand alone Explicitly connects across corporate, department, team, and individual layers 
Best suited for Individual performance commitments; operational reliability; compliance work Strategic initiatives; cross-functional alignment; growth and innovation goals 
Performance review use Often tied directly to compensation and ratings Best decoupled from compensation to preserve stretch ambition 

When to Use Each Framework 

The practical answer for most executive teams is to use both, but for different purposes. 

Use SMART goals when: 

  • The goal is an individual performance commitment tied to a specific role or accountability. 
  • Reliability matters more than reach, particularly in compliance, audit, safety, and operational uptime objectives. 
  • The work is well-understood and the path to completion is largely known. 

Use OKRs when: 

  • The goal is strategic and requires alignment across multiple departments or teams. 
  • Ambition is more important than certainty, such as growth, innovation, or transformation initiatives. 
  • The work requires adaptive learning, and quarterly recalibration is more valuable than annual stability. 

In well-designed OKR systems, individual key results often look SMART: specific, measurable, and time-bound. The two frameworks reinforce rather than replace each other.  

How AI Helps Translate Between SMART Goals and OKRs 

AI is particularly useful at the boundary between these frameworks. Many organizations have existing libraries of SMART goals embedded in performance management systems. Migrating to an OKR practice does not require throwing those away. AI can: 

  • Translate existing SMART goals into key results, identifying which SMART goals are really lagging measures of a strategic objective. 
  • Cluster SMART goals into objectives, surfacing the latent strategic ambition behind a department’s collection of individual commitments. 
  • Flag misclassification: goals labeled as OKRs that are really SMART commitments, or SMART goals that are actually aspirational stretch targets in disguise. 

For a deeper, step-by-step comparison of when to use each framework, and how to choose the right structure for your team or initiative, see Inspire’s companion guides on SMART vs. OKR goal-setting[15] and the side-by-side analysis of OKRs vs. SMART goals[16]. Both resources expand the principles introduced here and provide practical examples for selecting the goal structure that best fits your organization’s strategic intent.  

How Does AI Help Executives Translate Strategy into Corporate OKRs? 

Corporate OKRs sit at the top of the system. They are the bridge between the strategy map developed in Part 2 of this series and the day-to-day execution that follows. Paul Niven, a global OKR coach and Inspire partner, recommends building a strategy map first at the objective level, capturing the what and the why, before introducing the key results that will hold each objective accountable[5]. This sequencing matters: it forces the executive team to agree on what is and is not in scope before they collaborate on how to measure it. 

AI accelerates this corporate layer in several specific ways. 

Large language models have been trained on the canonical OKR literature (Doerr, Niven, and others), and have a reliable working knowledge of the methodology, including the rules that distinguish a strong objective from a vague one and a strong key result from a vanity metric. That shared baseline means an executive team can use AI as a structured collaborator rather than starting from a blank page.  

“Every model I’ve worked with extensively all have, in their large language models, a pretty good understanding of OKRs. So that’s a good strength to build on. When you start working with AI in those tools, you can count on the fact that you’re going to have a great collaborative session with the AI about some well-structured OKRs.” 

— Chris Wollerman

Practically, AI helps executive teams at the corporate layer in four ways: 

  • Drafting and pressure-testing objectives. AI can take a strategy map and propose corporate objectives in OKR form, then critique its own drafts for clarity, business value, and connection to the underlying strategic intent. 
  • Collaborating on proposed key results. Based on input from the user, AI can propose outcome-oriented key results and, critically, suggest lead-measure key results that provide an early signal, not just lagging outcomes at quarter-end. 
  • Quality-checking language. Inside a platform context like Inspire Software, AI can flag corporate OKRs that are unmeasurable, duplicative, or misaligned with the strategy map before they are published to the rest of the organization. 
  • Recommending who should align. AI can scan corporate key results and propose which departments and roles are the natural owners of the contributing work, reducing the political friction of determining who is responsible. 

What Is a Minimum Viable Strategy™? 

One pragmatic approach to the corporate layer comes from Daniel Montgomery, Managing Director of Agile Strategies and Inspire partner, who introduced the concept of Minimum Viable Strategy™[7] to developing and executing an effective strategy. The MVS idea is that an executive team is better served by a small number of clear, well-connected priorities than by an exhaustive strategic plan that no one can hold in their head. 

AI is well-suited to this discipline. It can compress, distill, and force-rank a long list of strategic ambitions into a defensible, short list of a viable strategy that helps the executive team articulate the trade-offs they are making by leaving items off the list. Combined with Niven’s recommendation to anchor strategy in a one-year horizon (rather than the increasingly obsolete three- to five-year strategic plan), AI gives executives the analytical leverage to operate with both focus and agility. 

How Should Departments Translate Corporate OKRs into Their Own OKRs? 

Once corporate objectives and key results (sometimes called CKRs) are set, the next level is the department. This is the first place where the executive team’s intent meets functional reality. It is at the department level where finance, sales, marketing, customer success, engineering, and operations each must answer the question: 

What does this corporate priority mean for us? 

It is also the first place where the connect-versus-cascade decision presents itself, and where many organizations go wrong. The default temptation is to simply assign each corporate key result to a department head and move on. That is fast, but it tends to produce shallow ownership and even shallower execution. 

AI changes the economics of doing this layer well. With a corporate objective and its key results loaded as context, a department leader can use AI to: 

  • Interpret the corporate intent. Ask the AI to explain, in the department’s functional language, what the corporate objective is really asking the department to contribute. 
  • Generate aligned department objectives. Draft a small set of department-level objectives that ladder up to the corporate OKR, with the AI challenging back on coverage gaps and overlaps. 
  • Build measurable key results. Propose 2–4 key results per objective, balancing lead measures (which the department can influence weekly) with lag measures (which prove the contribution to the corporate outcome). 
  • Identify dependencies. Surface the cross-functional handoffs that the department’s OKRs will require, so they can be negotiated up front rather than discovered during execution. 

The discipline at this level is to use AI as a collaborator that asks the department leader hard questions, not as a generator that produces an OKR draft to be rubber-stamped. The best practice that Inspire CEO Chris Wollerman repeatedly emphasizes is to instruct the AI to interrogate, not just produce. 

“Don’t just give it a prompt to say do this. Tell it to ask you questions as you’re working through it, and you’ll see you can come up with some robust alignment with AI. That’s the start of your execution.” 

— Chris Wollerman

What Is the Difference Between Cascading OKRs and Connecting Them? 

At Inspire, we encourage executive leaders to explore how to ‘connect’ OKRs to the corporate strategy, rather than just ‘cascade’ them down through the organization. Connecting OKRs describes how departments, teams, and individuals align their work to the corporate strategy. This is not a stylistic preference. It is a deliberate distinction grounded in behavioral science and designed to support agile strategy more effectively than simply cascading OKRs. 

Cascading, in its purest form, is top-down. An executive defines a key result, assigns responsibility, and hands it down for execution. The receiving team or individual inherits the goal and begins working toward it. Although it is an efficient way to operationalize the strategy, it can reduce people’s engagement with the work, especially if they are not involved in the cascading process. If the executive and receiving leader are cascading the OKRs together, there are less surprises and more buy-in. 

Connecting, by contrast, is a deliberate act of communication and collaboration. The corporate key result is communicated clearly. Expectations are set in a workshop or briefing. But the team or individual is invited to co-create how they will contribute. They are encouraged to explore which objective they will own, which key results they will commit to, and the trade-offs they recommend. The result is the same alignment, but with materially higher ownership. 

The behavioral science on this is well established. Self-Determination Theory, developed by Edward Deci and Richard Ryan, identifies three psychological needs (autonomy, competence, and relatedness) that drive intrinsic motivation and sustained performance[9]. Susan Fowler, in Master Your Motivation[8], translates this body of research into a practical framework for organizations: when employees are handed goals without input, autonomy is eroded; when they are invited to co-create them, autonomy is preserved and engagement increases during the pursuit of that objective. 

The choice between connect and cascade is therefore not just a semantic one. It is the difference between an organization that executes through compliance and one that inspires its people to execute through a partnership with the organization’s strategy.  

“The connect concept is to communicate the corporate key result, give a workshop to your teams and individuals on the expectations and what you really want to see as the outcome, but then let them collaborate at the team level or the department level to decide what’s the best approach. You’re going to get more buy-in because they helped create it. And you’re going to get better employee engagement and high performance because they can start to see the meaning in what they’re doing.” 

— Chris Wollerman
Note: When Cascading Is Actually the Right Move 

Connecting is the default. But there are situations where cascading is the correct discipline. 

Cascading to yourself. A CFO who owns the corporate key result on operating expense reduction can legitimately cascade that goal to themselves and a small executive sub-team. The measure is already known. The owner is already the executive. Cascading here is just a clean way to assign accountability. 

Cascading inside a conversation. When a leader sits with a team member and walks them through a goal in real time, explaining the context, expectations, and rationale, the act of “pushing the button” to cascade it becomes a collaborative moment rather than simply a top-down imposition. 

Cascading for compliance-driven work. Regulatory, safety, or audit-driven goals often have non-negotiable parameters. Pretending they are open for co-creation would be dishonest. Cascading clearly, with the reasoning explained, shows respect for the team’s intelligence. 
 
The principle is simple: cascade with intention, rarely by default. 

How Does AI Help Teams Connect to Corporate OKRs? 

Once department OKRs are set, the next level is the team, the working unit where most strategy execution actually happens. This is where the “connect” principle has the highest leverage. Team-level OKRs are where strategy becomes concrete: real deliverables, real customers, real numbers. 

AI accelerates the team level in three ways: 

1. Better-Quality Team OKR Drafting 

A team lead can give an AI tool for the corporate and department-level OKRs, the team’s charter, and historical performance data, then collaborate on a draft set of team OKRs. The AI then becomes a sparring partner, proposing objectives, pressure-testing the team’s alternatives, and challenging weak key results, until the team has a working draft in a fraction of the time an off-site planning session would take. The same working context lets the team pivot quickly as conditions change. 

2. Stronger Alignment Conversations 

AI can analyze a team’s proposed OKRs against the corporate strategy map for coverage gaps, redundancies with adjacent teams, and dependency risks. That analysis becomes the agenda for alignment conversations, not a substitute for them. 

3. Weekly Planning at the Team Level 

OKRs are not just a quarterly process; they are a weekly operating discipline. AI can identify the highest-leverage activities for the coming week by analyzing progress against key results and flagging goals most at risk of slipping. This is where the OKR system stops being a planning exercise and starts being an execution engine. 

“We talk about the most important things I can do this week to make progress on this OKR, and collaborate with AI on that. Because you’ve got all your key results in there, and you can get some great ideas on what activities could help move you forward this week. If you don’t know where to start, AI can help give you insights on how to pursue what matters most to the team.” 

— Chris Wollerman

How Does AI Support Individual OKRs and One-on-Ones? 

The final level is the individual. This is where OKRs either become deeply personal or quietly invisible. Done well, individual OKRs give every employee a clear line of sight from their weekly work to the corporate strategy. Done poorly, they become an exercise that managers and employees alike resent. AI is the difference between these two outcomes for many organizations, because it lowers the cost of the conversations that make individual OKRs work. 

Connecting the Individual to the Strategy 

Inside a secure platform context, an employee can ask: “Given my role and our department’s OKRs, what would be the most meaningful objectives for me to own this quarter?” The AI surfaces candidates aligned with the employee’s role, the team’s purpose, and the company’s strategic direction. The employee chooses. The manager reviews. The result is a personal OKR the employee genuinely owns, because they chose it from a set of valid options rather than receiving an assignment. 

AI-Supported One-on-Ones 

The weekly or biweekly one-on-one is where individual OKRs can live or die. AI supports individuals by prompting honest self-assessment on progress, skill, and motivation, and by capturing a narrative around the numbers so the conversation is about meaning, not just status. 

AI can support managers by: 

  • Suggesting the agenda. Summarizing the employee’s OKR status, recent updates, and risks before the meeting. 
  • Suggesting coaching prompts. Recommending questions tailored to where the employee is on each goal, whether they need direction, support, or just acknowledgment. 
  • Capturing commitments. Drafting the meeting summary and the agreed-upon next steps so the manager can spend their time on the conversation rather than the documentation. 

Done well, this is where the OKR system becomes a development system. AI gives the manager more capacity to coach, which, according to Fowler’s research on motivation[8], is the single biggest determinant of whether an employee finds their work meaningful. 

What Are the Risks Executives Should Watch for Using AI as an OKR Engine? 

Using AI to operationalize OKRs is not without disruption. Three risks deserve executive attention.  

1. Shadow AI and Data Exposure 

When employees use whichever AI tools they personally prefer to draft strategic goals, sensitive corporate strategy can leak into public model training data. The mitigation is an explicit company AI policy that specifies which tools are sanctioned, what data can and cannot be entered into them, and the consequences. This applies at every layer of the OKR system, because OKR data is, by definition, strategic. 

2. Garbage In, Garbage Out 

Recent field research from Harvard Business School on what they termed the jagged technological frontier[13] confirmed that AI dramatically improves output quality on some tasks and degrades it on others. The decisive variable is the human in the loop. An OKR drafted by AI without human discernment is rarely a usable OKR. The right model is human-led, AI-accelerated — not AI-generated, human-approved. 

“You’ve got to have a human element at the start of it with good prompting when it comes to the usage of AI. You really need a human element that’s asking and then evaluating and discerning what you’re getting back from the AI, because it could be garbage in, garbage out. Software is only the tool that supports the human and the human decisions.” 

— Chris Wollerman

3. Integration Through Governed Connectivity 

A modern executive’s tech stack spans dozens of systems: finance, HR, sales, customer success, BI, and the strategy execution platform itself. OKRs lose their power when these systems do not talk to each other, because every status update becomes a manual artifact rather than a real-time signal. New protocols for connecting AI tools to enterprise data sources, such as the Model Context Protocol (MCP) announced by Anthropic in 2024[14], let a strategy execution platform connect simultaneously to a finance system, a BI tool, and a conversational AI assistant with governance preserved. Used well, this orchestration lets executives ask cross-system questions in plain language and get grounded answers; used carelessly, it expands the surface area for data exposure. Executive teams need to plan for both. 

How Long Does It Take to Implement an AI-Supported OKR Engine Within an Organization? 

Chris Wollerman frames the early stage of an OKR rollout as crawl, walk, run, with the first 90 days squarely in the crawl phase. The goal is not perfect execution. The goal is to get the system in motion, with enough discipline that the next 90 days can build on it. 

A minimum viable 90-day rollout looks like this: 

  • Weeks 1–2, Set the foundation. Confirm the corporate strategy (referencing the SCALE and MAP work from Parts 1 and 2 of Inspire’s Executive series of articles: How AI Can Help Executive Leaders Develop and Execute A Winning Strategy). Establish the company AI policy. Choose the strategy execution platform. 
  • Weeks 3–4, Draft corporate OKRs. Use AI as a structured collaborator to draft and pressure-test corporate objectives and key results. Publish them to the organization with context, not just content. 
  • Weeks 5–8, Connect departments and teams. Run alignment workshops. Departments and teams use AI to draft connected OKRs. Cross-functional dependencies are surfaced and negotiated up front. 
  • Weeks 9–10, Establish the operating rhythm. Weekly team meetings to review progress, flag blockers, and adjust. AI helps prepare the meetings and capture the outcomes. 
  • Weeks 11–12, Roll out One-on-Ones. Managers and Team Leaders begin AI-supported weekly or biweekly conversations with their team members. Individual OKRs are reviewed in the context of development, not just status. 

At the end of 90 days, an organization may not necessarily have mastered OKRs, but it will have done something more important: it will have started building an effective strategy execution engine. The corporate strategy will be visible in a language people understand. Departments and teams will have connected to it on their own terms. Managers, Team Leaders, and individuals will be in conversation about progress, not just performance. That is the crawl portion of implementing OKRs into your organization. The walk and the run come next, in subsequent quarters (and will be explored in future articles in this executive series). 

Why Are OKRs the Preferred Goal-Setting Method for Creating a Modern Strategy Execution Engine? 

The defining executive question of this AI moment is not whether to use AI in strategy execution. That decision has already been made by the market. The question is how to use it and whether the way an organization uses AI strengthens the human dimensions of execution or substitutes for them. 

OKRs are the engine that turns strategy into action because they are simultaneously rigorous and human. The rigor comes from the structure of qualitative objectives and is held accountable by quantitative key results. Humanity comes from connecting people to the strategy, inviting them into a partnership in their contributions, and supporting them through weekly conversations that treat them as valued contributors—not just part of the strategy engine. 

AI raises the bar on both dimensions. It makes the rigor of setting goals aligned with strategy more effective and efficient to create, while sustaining the human element of an effective goal-setting process. But only if executive teams encourage the discipline of connection over the convenience of cascading alone. The organizations that get this right will execute strategies more effectively than their competitors. 

Inspire Software[17] partners with strategy practitioners like Paul Niven[5] and Daniel Montgomery[7], behavioral scientists like Susan Fowler[8], and a community of strategy and leadership development experts, coaches, and consultants to help organizations align strategy with performance to inspire effective execution and employee engagement through meaningful, measurable results. 

The next article in this series will explore how AI supports the weekly execution cadence through one-on-ones, team meetings, and check-ins that turn an OKR system into a continuous performance practice that stays aligned with strategy. 

About the Author: Jason Diamond Arnold is Director of Leadership Solutions at Inspire Software and the author of multiple works on self-leadership, leadership development, and organizational performance. This article is Part 3 of an executive thought leadership series produced in partnership with Chris Wollerman, CEO of Inspire Software. 

Frequently Asked Questions 

What are OKRs, and how do they differ from SMART goals? 

OKRs (Objectives and Key Results) pair a qualitative objective (what an organization is trying to do and why) with quantitative key results that show progress (what the people pursuing the objective have achieved or not). SMART goals describe the shape of a single well-formed goal (specific, measurable, attainable, relevant, time-bound). The two frameworks are complementary: SMART describes the quality of any goal; OKRs describe the structure that connects qualitative ambition to quantitative measurable outcomes. For a deeper, step-by-step comparison, see Inspire’s companion guides[15] and[16]. 

Why does Inspire use the word “connect” instead of “cascade”? 

Cascading implies top-down imposition: a leader hands a goal to a team or individual to execute. Connecting implies co-creation: the leader communicates the corporate objective, sets expectations, and invites teams and individuals to define how they will contribute. Behavioral science research, including Self-Determination Theory (SDT) and the work of Susan Fowler[8], shows that co-creation produces materially higher engagement and ownership than imposition. Some cascading is appropriate, for example, when a CFO assigns a corporate financial goal to themselves, or when a regulatory goal has non-negotiable parameters; but connection should be the default. 

How can AI help an executive team draft better corporate OKRs? 

AI can take a strategy map and collaboratively propose corporate objectives in OKR form, generate candidate key results that balance lead and lag measures, quality-check the language of objectives for clarity and measurability, and recommend which departments should connect to each corporate key result. The discipline is to instruct the AI to interrogate the executive team’s thinking rather than simply produce drafts for approval. 

What is the biggest risk in using AI to draft OKRs? 

The two largest risks are data exposure (employees putting strategic goals into open AI tools that may use the data for training) and shallow output quality (accepting AI-drafted OKRs without sufficient human discernment). The mitigations are a clear company AI policy and a working model of human-led, AI-accelerated drafting rather than AI-generated, human-approved. 

Can a company implement an AI-supported OKR system in 90 days? 

Yes, with a realistic and disciplined implementation. A 90-day rollout typically establishes corporate OKRs, connects departments and teams to them, and begins the weekly operating rhythm of team meetings and one-on-ones. It does not produce OKR mastery. The walk-and-run phases occur in subsequent quarters as the organization deepens its practice of weekly planning, continuous performance conversations, and quarterly reviews. 

How do OKRs relate to continuous performance management? 

OKRs provide the structure of what the organization is trying to accomplish, who is connected to each priority, and how progress is measured. Continuous performance management provides cadence through weekly one-on-ones, team check-ins, and quarterly reviews, keeping the OKR system accurate and accountable. The two are inseparable: an OKR system without a performance cadence becomes a planning artifact; a performance cadence without OKRs becomes feedback without direction. 

What role does Minimum Viable Strategy™ play in OKR design? 

Daniel Montgomery’s Minimum Viable Strategy™[7] principle argues that an executive team is better served by a small number of clear, well-connected priorities than by an exhaustive plan that is difficult to live up to. In the context of OKRs, this means resisting the temptation to set too many corporate objectives. AI can help force-rank a long list of strategic ambitions into a defensible short list and articulate the trade-offs of the items left off it. 

What is MCP, and why does it matter for strategy execution? 

Model Context Protocol (MCP) is an open standard introduced by Anthropic in 2024[14] that enables AI assistants to securely connect to enterprise data sources, such as finance systems, BI tools, strategy execution platforms, and others, while preserving governance. For executive teams, MCP-enabled orchestration enables asking cross-system questions in plain language and receiving grounded, real-time answers. For example, an executive could ask their AI assistant to draft an OKR for reducing operating expenses, drawing live data from the company’s financial system, and have the resulting OKR written back to the strategy execution platform, all within a single conversation, with appropriate enterprise controls. 

Resources 

Inspire Software Resources 

[2] Arnold, J. D. (2026). How AI Helps Executive Leaders Develop a Winning Strategy (Part 1, SCALE Framework). Inspire Software. https://blog.inspiresoftware.com/how-ai-helps-executive-leaders-develop-a-winning-strategy 

[3] Arnold, J. D. (2026). How AI Helps Executive Leaders Visualize and Communicate Strategy (Part 2, MAP Framework). Inspire Software. https://blog.inspiresoftware.com/how-ai-helps-executive-leaders-visualize-and-communicate-strategy 

[15] Arnold, J. D. (2018). SMART or OKR: A Step-By-Step Guide to Selecting Your Goal Structure. Inspire Software. https://blog.inspiresoftware.com/smart-okr-goal-structure-guide 

[16] Arnold, J. D. (2018). OKRs vs. SMART Goals: Choosing the Right Goal Framework for Your Organization. Inspire Software. https://blog.inspiresoftware.com/okrs-vs-smartgoals 

[11] Inspire Software (2025). The State of Strategy Execution in 2025 (Whitepaper). Inspire Software. https://www.inspiresoftware.com/ 

[12] Inspire Software (2025). The Six Steps to a Winning Strategy (eBook). Inspire Software. https://www.inspiresoftware.com/ 

[17] Inspire Software (2026). Inspire Software — Strategy Execution Platform. Inspire Software. https://www.inspiresoftware.com/ 

[18] Wollerman, C. (2026). Chris Wollerman — CEO, Inspire Software (LinkedIn profile). LinkedIn. https://www.linkedin.com/in/chris-wollerman/ 

[19] Arnold, J. D. (2026). Jason Diamond Arnold — Director of Leadership Solutions, Inspire Software (LinkedIn profile). LinkedIn. https://www.linkedin.com/in/jasondiamondarnold/ 

OKR Methodology and Strategy Execution 

[4] Doerr, J. (2018). Measure What Matters: How Google, Bono, and the Gates Foundation Rock the World with OKRs. Portfolio / Penguin. https://www.whatmatters.com/the-book 

[5] Niven, P. R., & Lamorte, B. (2016). Objectives and Key Results: Driving Focus, Alignment, and Engagement with OKRs. Wiley. https://www.wiley.com/en-us/Objectives+and+Key+Results%3A+Driving+Focus%2C+Alignment%2C+and+Engagement+with+OKRs-p-9781119252399 

[7] Montgomery, D. (2018). Start Less, Finish More: Building Strategic Agility with OKRs (introducing Minimum Viable Strategy™). Agile Strategies Press. https://www.agilestrategies.com/ 

[6] Kaplan, R. S., & Norton, D. P. (2000). The Strategy-Focused Organization: How Balanced Scorecard Companies Thrive in the New Business Environment. Harvard Business School Press. https://store.hbr.org/product/the-strategy-focused-organization-how-balanced-scorecard-companies-thrive-in-the-new-business-environment/1747 

[10] Sull, D., Sull, C., & Yoder, J. (2018). No One Knows Your Strategy — Not Even Your Top Leaders. MIT Sloan Management Review. https://sloanreview.mit.edu/article/no-one-knows-your-strategy-not-even-your-top-leaders/ 

[20] Niven, P. R. (2023). OKRs for Dummies. Wiley. https://www.amazon.com/OKRs-Dummies-Business-Personal-Finance/dp/1394183488 

Behavioral Science Foundations 

[8] Fowler, S. (2019). Master Your Motivation: Three Scientific Truths for Achieving Your Goals. Berrett-Koehler. https://www.bkconnection.com/books/title/master-your-motivation 

[9] Deci, E. L., & Ryan, R. M. (2000). The “What” and “Why” of Goal Pursuits: Human Needs and the Self-Determination of Behavior. Psychological Inquiry, 11(4), 227–268. https://selfdeterminationtheory.org/SDT/documents/2000_DeciRyan_PIWhatWhy.pdf 

AI in Strategy and Knowledge Work 

[13] Dell’Acqua, F., et al. (2023). Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of AI on Knowledge Worker Productivity and Quality. Harvard Business School Working Paper 24-013. https://www.hbs.edu/ris/Publication%20Files/24-013_d9b45b68-9e74-42d6-a1c6-c72fb70c7282.pdf 

[14] Anthropic (2024). Introducing the Model Context Protocol. Anthropic. https://www.anthropic.com/news/model-context-protocol 

[21] Hanby, J. B., IV (2025). The AI Strategy Blueprint. https://www.amazon.com/s?k=AI+Strategy+Blueprint+Hanby 

© 2026 Inspire Software. Part 3 of the Executive Series on How AI Helps Executive Leaders Develop and Execute a Winning Strategy. See also: Part 1: Developing a Winning Strategy and Part 2: Visualizing and Communicating Strategy. 

About the Author: Jason Diamond Arnold

Jason Diamond Arnold is the Director of Leadership Solutions and an OKR and Performance Coach at Inspire Software, a strategy execution and performance management platform that helps organizations align goals, execute strategy, and improve leadership performance across teams.

With more than 25 years of experience in leadership development, organizational performance, and strategy execution, Jason works with executives, managers, and teams to translate leadership theory into practical systems that drive measurable business results. Through Inspire Software’s OKR framework, coaching programs, and leadership development tools, he helps organizations strengthen strategic alignment, improve employee engagement, and build high-performance cultures.

Jason’s work bridges behavioral science, leadership development, and performance technology, helping organizations move from strategy planning to consistent execution. He has coached leaders across industries including technology, retail, and professional sports, helping teams improve accountability, strategic focus, and measurable performance outcomes.

Experience and Background

Before joining Inspire Software, Jason worked as a product manager and consultant, collaborating with major organizations including Apple, Sephora, the NBA, and Verizon. His work has focused on helping organizations align leadership practices with measurable performance systems.

Jason is currently pursuing a PhD in Leadership at the University of San Diego and is a candidate for certification through the International Coaching Federation (ICF). He also serves as a Lecturer at the University of San Diego School of Leadership, where he teaches and researches modern leadership frameworks and organizational development.

With more than 1,000 hours of coaching and consulting experience, Jason specializes in helping organizations implement leadership systems that support strategic alignment, goal management, and sustainable performance improvement.

Areas of Expertise

  • Jason specializes in leadership development and strategy execution, including:
  • OKR Implementation and Coaching: Helping organizations implement Objectives and Key Results (OKRs) to align teams around measurable strategic goals.
  • Leadership Development and Organizational Coaching: Supporting leaders in building effective leadership practices that drive accountability, engagement, and performance.
  • Strategic Alignment and Performance Management: Helping organizations connect leadership behaviors, team goals, and measurable performance outcomes.
  • Managerial Leadership and Self-Leadership: Equipping managers and employees with the tools to align individual performance with company strategy.
  • Performance Excellence and Behavioral Leadership Science: Using research-based leadership frameworks to help organizations improve team performance and operational efficiency.

Coaching Impact

  • Jason has helped organizations improve leadership performance and operational outcomes across industries.
  • Examples of his work include:
  • Global Retail Organization: Led leadership alignment and strategic restructuring initiatives that improved operational efficiency by 30 percent.
  • Professional Sports Organization: Coached leadership teams to align career development with strategic goals, improving team collaboration and performance by 25 percent.
  • Technology and Software Teams: Implemented coaching and leadership alignment programs that increased engagement and improved goal achievement metrics by 40 percent.

Leadership and Thought Leadership at Inspire Software

As Director of Leadership Solutions at Inspire Software, Jason helps shape how leadership development integrates with strategy execution technology.

He has contributed more than 100 thought leadership articles, research projects, eBooks, and podcasts focused on leadership, OKRs, and performance management. His work helps organizations combine leadership development with modern strategy execution tools to create cultures of accountability, alignment, and sustained performance.

At Inspire Software, Jason’s work focuses on aligning leadership theory, behavioral science, and technology to help organizations build high-performing teams and execute strategy more effectively.

Additional Posts