Your Team Has a Strategy. Almost Nobody Can Execute It.

Most scaling companies do not have an execution problem. They have a translation problem.

The strategy exists. The vision has been articulated. The all-hands deck is polished. And then Monday morning arrives, and 75% of the organization is working on something only loosely connected to any of it.

This guide breaks down why that happens, how the OKR framework and operating cadence are designed to close that gap, and what it actually takes to implement them in a scaling company. If you are a founder or COO, trying to make strategy stick below the leadership team, this is for you.

‍

The Strategy-Execution Gap: Why Most Teams Are Busy Going Nowhere

Here is a stat worth sitting with. Research shows 82% of executives feel aligned on strategy. Only 23% of their organization actually is. That gap  the void between what leadership believes the priorities are and what the team is actually working on, is what we call the Air Sandwich.

The Air Sandwich is not a communication failure. It is a systems failure. You can send the follow-up email, record the all-hands, and post the strategy doc in Notion. It will not matter if the organization has no operating rhythm that makes those priorities visible week over week.

What fills the Air Sandwich is not better communication. It is a cadence, a structured operating rhythm that connects the company's most important goals to what each person does on a given Tuesday. Without that rhythm, strategy happens only once a quarter at an offsite and then slowly evaporates.

The cost of leaving this gap open is not dramatic. It is quiet. Smart people work hard on the wrong things. Managers spend their time firefighting rather than developing people. The CEO becomes the only person who cares about the number on the scoreboard. Individually, everything looks fine. Collectively, it costs you quarters.

→ How to Avoid the 6 Fatal OKR Mistakes Startups Make

‍

What an Operating Cadence Actually Is

An operating cadence is the structured rhythm by which a team sets priorities, tracks progress, surfaces problems, and makes decisions together at regular intervals. It is not a meeting structure. It is an operating system.

Most teams have fragments of a cadence: a quarterly planning session here, a weekly standup there, a monthly review that keeps getting cancelled. What they rarely have is a coherent, connected rhythm in which each level of the organization reports on progress, surfaces blockers, and makes decisions that link back to the same set of goals.

A well-designed operating cadence runs on four levels.

Daily. A brief async or synchronous check-in. What am I working on today? Any blockers? The purpose is not accountability theatre. It is making work visible so problems surface before they become crises.

Weekly. A priority scorecard. Each team member reports on their top priorities for the week, their progress against quarterly goals, and any blockers they need help clearing. This is the most high-leverage habit a scaling team can build. When people report on their metrics every single week, they start to own them. The CEO stops being the only one who cares about the number.

Monthly. A metrics review, sometimes called an MBR, or monthly business review. Where are we tracking against quarterly objectives? What is at risk? What is the one constraint that needs to be unblocked this month? The monthly review is where the team diagnoses problems at the right altitude: not so close that you are in the weeds, not so far that you are just reviewing slides.

Quarterly. The OKR cycle. Set goals collaboratively, honestly assess the previous quarter, and cascade priorities from the company level down to teams and individuals. This is the strategic heartbeat of the organization.

The failure mode for most teams is that they design the quarterly layer and skip everything else. They set OKRs once and then have no system for keeping those goals alive in the daily and weekly work. Ninety days later, the OKRs sit in a Google Doc that nobody has opened, and the team wonders why the framework did not work.

The OKRs did not fail. The cadence was never built.

‍

How OKRs Actually Work  And Where Most Teams Get the Structure Wrong

OKRs stand for Objectives and Key Results. The framework is simple in concept and surprisingly easy to misapply in practice.

An Objective is qualitative. It describes where you want to go. It is directional, aspirational, and specific enough to be meaningful. It should not contain a metric. "Become the most trusted platform for sports fan data in North America" is an objective. "Grow revenue to $10M" is not that is a key result.

A Key Result is quantitative. It measures whether you achieved the objective. Two to five key results per objective is the right range. They must be numerical. "Improve customer satisfaction" is not a key result. "Increase NPS from 32 to 50 by the end of Q3."

Initiatives are the work itself, the tasks and projects that drive the key results. These are binary: done or not done. The most common OKR mistake is confusing key results with initiatives. "Redesign the onboarding flow" is an initiative. "Increase trial-to-paid conversion rate from 18% to 25%" is a key result.

OKRs work best when they are set at three levels and cascaded from the top down.

Company OKRs are set by the leadership team. They reflect the three to five most important things the organization needs to accomplish this quarter to move closer to its long-term vision.

Team OKRs are built by each team lead, in collaboration with their team. Each team's OKR should connect directly to a company's OKR. This is not a top-down mandate; it is a translation exercise. How does this team's work contribute to the company's most important goals?

Individual OKRs are set by each team member, again in collaboration with their manager. One or two objectives per person is the right number. They connect to a team's OKR. This is the link that makes strategy personal: not "the company wants to grow revenue" but "here is specifically what I am doing this quarter that moves that number."

The cascade is what closes the Air Sandwich. When every individual can draw a line from their weekly priorities to their team's OKR to the company objective, the strategy is no longer a slide deck. It is a shared operating reality.

→ Step-by-Step: How to Use OKRs to Become a Better Manager

‍

Why OKR Rollouts Fail

OKRs have been around since the 1970s. Intel used them. Google credits them with much of its early growth. And yet most OKR rollouts at scaling companies fail within two quarters. Why?

Our Team Dynamics Assessment has run across 900-plus respondents since 2020, points to a consistent pattern. The issue is almost never the framework. It is almost always one of three failure modes.

Goals set from the top down, without participation. When the leadership team sets the OKRs and hands them down to the team, people do not own them the same way. Research on goal-setting is consistent here: participation in the goal-setting process drives ownership in a way that assigned goals do not. The team members who build the OKR are the ones who care about the scoreboard.

The cadence is never established. This is the most common failure mode. The OKRs are set. The kick-off happens. And then there is no weekly check-in structure, no monthly metrics review, no moment in the calendar where progress becomes visible. Goals reviewed only once at the end of the quarter are not goals; they are aspirations.

The Vision Gap. Our TDA data finds that Vision is consistently the lowest-scoring level in the Six Levels of High-Performing Teams framework, averaging 3.69 out of 7 across all respondents. And it drops further as companies scale. We tracked this longitudinally with StellarAlgo: as they grew from 30 to 90 people, Vision scores fell from 4.42 to 4.13.

This is what we call the Vision Ceiling. Teams develop enough psychological safety to show up and do the work. But they cannot articulate where the work is going or why it matters. Comfort and clarity are not the same thing. And you cannot execute a strategy your team cannot see.

OKRs, when implemented with a real cadence, are the mechanism for closing the Vision Ceiling. They operationalize strategy, turning a slide at an all-hands into a number on a weekly scorecard that every team member owns.

→ Decision-Making Techniques and Tools for Leaders

‍

The Human Side: Why OKRs Without Psychological Safety Become Theatre

Here is the thing most OKR guides miss. The framework is a tool. Whether it works depends almost entirely on the culture into which it is being installed.

If people do not feel safe reporting that a key result is off track, the weekly scorecard becomes a performance review. Everyone reports green. Problems stay hidden until they become crises. The OKR system becomes a source of anxiety rather than clarity, and people quietly stop engaging with it.

The research on psychological safety, led by Amy Edmondson at Harvard, is consistent on this point: teams that feel safe surfacing problems and flagging risks outperform those that do not on almost every measurable dimension. OKRs amplify this dynamic in both directions. In a psychologically safe team, weekly scorecards surface problems early, when they are still solvable. In a team that lacks safety, they surface only the sanitized version of reality.

This connects directly to where OKRs sit in the Six Levels of High-Performing Teams framework. Empowerment, the second level, is the condition under which OKRs actually work. An empowered team owns the goal. They set it collaboratively, report on it honestly, and hold each other accountable to it without needing the manager to run every check-in.

The Empowerment Spectrum runs from Controlled to Managed to Coached to Empowered. Most scaling teams sit somewhere between Managed and Coached: the manager sets direction, the team reports on activity, and accountability still flows upward.

The operating cadence, when it is working well, moves teams toward Empowered, where the team owns the scoreboard, surfaces blockers proactively, and the manager's job shifts from tracking progress to removing obstacles. Getting there is not purely a systems design problem. It requires building the conditions of safety, clarity, and shared ownership that make the system trustworthy. 

‍

How to Implement OKRs at a Scaling Company

Implementation is where most rollouts die. Not the design phase, not the kick-off, not the first quarter. The second quarter, when the novelty has worn off, and the cadence starts slipping.

A good implementation follows three phases, not a fixed timeline, but a logical sequence.

Phase 1: Diagnostic and Strategy Clarity.

Before writing a single OKR, the most important question is: why is execution breaking down? Where are decisions getting stuck? Is the Vision gap a leadership alignment problem or a communication problem? Does the team have a clear decision-making framework, such as a RACI or DRI model, or is everything escalating to the top?

The diagnostic phase answers those questions. Then comes a strategy clarity session with the leadership team: a working session, not a presentation, where leadership aligns on the three to five most important priorities for the quarter and agrees on how to measure them. This is the foundation on which everything else is built. If the leadership team is not aligned on what matters most, the OKR cascade below it will only widen the misalignment.

If a full leadership offsite is the right time to do this work, the strategy clarity session can serve as the anchor of that event.

Phase 2: OKR Build and Cascade.

With strategic clarity established, the OKR-setting process runs from the top down across three levels. The keyword here is participative design. Team leads and their people build the OKRs together, connecting team objectives to company objectives. This is not a template exercise  it is a structured conversation about what each team is actually responsible for moving.

The cadence architecture is also defined in this phase: what the weekly check-in looks like, how the monthly review is structured, and how the quarterly retrospective connects to the next cycle.

Phase 3: Rhythm Installation.

This is the phase most implementations skip entirely. It is not enough to design the cadence; someone has to actually run the first several cycles, troubleshoot when it slips, and coach managers on using the weekly check-in as a coaching tool rather than a status meeting.

The goal of this phase is independence, not dependency. A well-implemented operating cadence runs without the people who designed it in the room. The test is whether the rhythm holds when the manager is on vacation. If it does not, the system has not been installed; it has been performed.

The right timeline for moving through these phases depends on the team, the starting point, and what the diagnostic reveals. That conversation belongs in a strategy call, not on a webpage.

‍

What Good Looks Like: StellarAlgo and the Heated Offsite

In mid-2021, StellarAlgo's leadership team sat in a conference room and fought about priorities for most of an afternoon. The Calgary-based sports data startup had grown to 40-plus people, just raised a Series A, and had more inbound demand than they could serve. Every direction looked like a good one. And the team did not have the resources to pursue all of them.

What happened next is the part worth paying attention to. They did not defer to the CEO. They did not table the conversation for next quarter. They hashed out their disagreements, real and unfiltered, and emerged with a decision: they would not try to be everything to everyone. They would double down on sports-fan data and say no to everything that did not connect to it.

The operating clarity from that session changed how the team executed. Debates about direction stopped happening in every meeting because the direction was settled. People could move faster, confidently decline distractions, and connect their daily work to a shared set of priorities.

Three years later, the NBA took a strategic stake in StellarAlgo, making it the official fan engagement platform for the entire league. A 50-person team from Calgary beat every global consulting firm and enterprise vendor for the deal.

That is what strategic clarity actually produces. Not a prettier strategy deck. A faster, more focused team that can win deals they have no business winning because every person on the team knows what winning looks like.

‍

What to Look for in an OKR Implementation Consultant

Not all OKR engagements are structured the same way, and the differences matter more than most buyers realize when they are evaluating options.

A session-only approach, one workshop to set the OKRs and hand over a template, addresses the design problem but not the implementation problem. The cadence does not get installed. Managers are not coached on running check-ins. And three months later, the rollout has the same failure modes as the last one.

The more important questions to ask any consultant are about what happens after the OKRs are set. How is the cadence being supported through early cycles? What does manager coaching look like? How is the diagnostic being used to customize the design rather than applying a generic template?

A few principles worth holding:

At Unicorn Labs, our work in this space is grounded in the Six Levels of High-Performing Teams framework and informed by TDA benchmark data across 900-plus respondents. If you want to talk through what this looks like for your specific team and stage, the strategy call is the right starting point  no pitch deck, just a diagnostic conversation.

‍

Frequently Asked Questions:

‍

OKR Facilitation Across Canada and the US

We work with scaling companies from coast to coast. Most of our in-person engagements run in Toronto, Vancouver, Calgary, Ottawa, and Montreal, with strong demand across the US from our clients in New York, San Francisco, and Chicago.

All engagements are available either virtually or in a hybrid format. The diagnostic and strategy clarity sessions run particularly well in person when geography allows. Implementation coaching often runs virtually, which reduces travel burden on the team without sacrificing quality.

Whether you are a Toronto-based Series B trying to get your leadership team rowing in the same direction, or a Vancouver startup scaling into the US market and trying to keep strategy consistent across time zones, the engagement is built to meet you where you are.

‍

The Cost of the Air Sandwich Is Already Adding Up

Every quarter your team runs without a clear operating cadence is a quarter where smart people work hard in slightly different directions. That is not a people problem. It is a systems problem. And it has a cost: slower decisions, duplicated effort, and leaders too busy firefighting to develop the people under them.

The companies that scale well are not the ones with the best strategy deck. They are the ones who figured out how to translate strategy into what happens on a Tuesday morning. That is the work. And it is learnable.

If you want to talk through what this looks like for your team, the strategy call is the right first step, 45 minutes, no pitch deck, just a real conversation about where execution is breaking and what it would take to fix it.

Not ready to talk? Start with the Leadership Vault, the OKR playbook and 22 other resources that are free to explore.

‍

From the Blog:

These posts go deeper into the components covered in this guide.

• How to Avoid the 6 Fatal OKR Mistakes Startups Make — the most common ways a well-intentioned rollout falls apart, and how to sidestep each one before it costs you a quarter.
• Step-by-Step: How to Use OKRs to Become a Better Manager — a practical walkthrough for managers who want to turn OKRs into a weekly coaching rhythm, not just a tracking exercise.
• Decision-Making Techniques and Tools for Leaders and Managers — how to build the decision-making framework your team needs to move faster without escalating everything to the top.