Two hundred and fifty people. Three years on EOS. Rocks set every quarter. Level 10s on calendars across the org. By every external measure, the company is running a real operating system.
Last quarter closed at 58% of Rocks completed. Same as the quarter before. The Quarterly Conversation didn’t surface the slip until week ten, when the gap was already too wide to close.
You didn’t build the framework wrong. The problem is getting 250 people to actually use it. OKRs with EOS or Scaling Up are how you fix that without scrapping what you’ve spent three years building.
Where do OKRs fit when you’re already running EOS or Scaling Up? OKRs don’t replace your operating system. They sit underneath the priorities you’ve already set, adding the measurable signal that tells you, in week six, whether the work is actually moving the number. The framework picks the direction. OKRs tell you whether you’re getting there.
If your Rocks are hitting 60% and you can’t tell why until the postmortem, this is the layer that’s missing.
EOS and Scaling Up Leave a Visibility Gap at Scale: The Solution Is Using OKRS WITH EOS
EOS and Scaling Up are good frameworks. They get leadership aligned on direction. They build operating rhythm. They create accountability structures that work at the team level. Most companies running them are ahead of most companies that aren’t.
What they don’t do, on their own, is tell you whether a Rock or a quarterly priority is actually on pace at week six. The cadence they prescribe is built around status: who’s doing what, what’s blocked, what’s coming up next. Status gets reviewed. Progress doesn’t. The distinction matters more than most VPs catch on the first read of our writeup on the difference between reporting and progress.
That gap is invisible at twenty people. At two hundred and fifty, it compounds quarter over quarter. By the third or fourth slipped cycle, leadership is making strategic decisions on lagging signals. The framework is in place. The execution data isn’t.
Where OKRs With EOS Actually Plug In
The integration pattern is straightforward. The reason most VPs miss it is they treat OKRs as a competing methodology rather than a measurement layer.
Rocks become Objectives. A Rock states what the team will deliver this quarter. The Objective restates that as the outcome it’s supposed to create. Same intent, sharper framing.
Key results sit underneath each Rock. Two to four measurable milestones per Rock that tell the team, week to week, whether they’re on pace. This is what the framework leaves implicit and what most teams need explicit.
The Level 10 becomes the check-in. No new meeting. Same agenda, with one addition: each Rock owner reports the latest key result number and a confidence score, and the conversation moves from “what are you working on” to “are we going to hit this, and what changes if we won’t.”
The cadence is already there. The accountability structures are already there. You’re adding signal, not structure.
OKRs With Scaling Up: The Same Pattern, One Adjustment
Scaling Up’s structure is similar. Quarterly priorities map to objectives. Key results add the quantitative layer the One-Page Strategic Plan tends to leave at the strategic-theme level.
The one adjustment worth naming. Scaling Up often runs daily huddles and weekly leadership meetings. The OKR check-in lives in the weekly meeting, not the daily huddle. Daily huddles are designed for blockers and short-cycle coordination. The OKR conversation needs more time and a different question. Don’t try to compress it into the standup.
In a Scaling Up environment, the integration usually clicks faster than in EOS. The framework already emphasizes measurable priorities. OKRs just push that measurability one layer deeper, into the weekly review.
What Actually Changes in Your Operating Cadence
This is the part most VPs underestimate. The framework changes because the conversation changes, not because you’ve added a new ritual.
In a typical EOS or Scaling Up review, a Rock owner reports status. “We’re on track.” Or “We’re working on it.” That’s a self-assessment. It’s not a measurement.
With OKRs layered on, the same owner reports two things. The latest key result number, and a confidence score on a 0-to-1 scale in 0.1 increments on whether the target is still in reach. If the number is moving but confidence has dropped from 0.8 to 0.5, that’s a conversation. A reporting-only setup would never surface it. A measurement setup catches it on a Tuesday in week six, while there’s still time to do something about it.
That single change, repeated weekly, is what turns a 58% completion rate into a 75% one. Not a new framework. A new signal inside the framework you already have.
The Hard Part Isn’t the Methodology. It’s Adoption.
OKR Leader’s brand POV on this is simple. Adoption is the only metric that matters at launch. A beautifully designed OKR program that people don’t actually use is worse than a rough one that sticks. John Doerr’s framing in Measure What Matters lands the same way at every scale. The framework only works if it’s the framework people are actually running on Wednesday.
This matters more for VP Strategy roles than any other. The failure mode at scale is predictable. Leadership commits to the rollout. Training happens. Templates get distributed. Six weeks in, half the teams are using the new layer and half are quietly running the framework the way they always did. By month three, the program is dead in everything but name.
Three patterns help avoid that.
Start with one team that’s already running the framework well. Not the team that’s struggling. The team that has visibility on its priorities, hits its commitments, and will treat OKRs as a refinement rather than a rescue. That team’s results sell the rollout to everyone else.
Don’t tie OKR scores to performance reviews. Conflating goal-setting with comp produces sandbagging, not ambition. People set safe targets they know they can hit. The data stops being honest. The whole point of layering OKRs onto your framework is to get more truth into the cycle, not less.
Put the tooling on the same operating cadence the team already runs. If the Level 10 is on Tuesdays, the OKR check-in lives there. If the weekly leadership meeting is on Mondays, that’s where the data shows up. The fastest way to kill adoption is to ask people to manage two systems.
When OKRs With EOS or Scaling Up Don’t Add Value
Honest answer. If your framework is genuinely working, you don’t need this layer. Working means Rocks closing at 80% or above consistently, mid-cycle visibility on every priority, the Level 10 surfaces real decisions rather than status updates, and leadership doesn’t get surprised in week ten. Frequent recalibration is the variable that separates frameworks that work from frameworks that don’t.
If that’s the picture, OKRs are overhead. The frameworks were designed to do exactly what’s already happening.
If the picture is different, the gap isn’t in the framework. It’s in what the framework measures. That’s the layer to add.
You Built the Framework. Now Make It Measurable.
Your job isn’t to defend the operating system you’ve already invested in. It’s to make sure that operating system is producing the outcomes the company committed to. EOS and Scaling Up set the direction. OKRs tell you whether you’re getting there.
The 250 people in your org don’t need another methodology to learn. They need a measurement signal inside the cadence they already know.
Book a Demo to see how OKR Leader layers onto an EOS or Scaling Up rhythm without disrupting what’s already in place.
FAQs: OKRs With EOS or Scaling Up
Can you use OKRs with EOS?
Yes. OKRs with EOS work well as a complementary measurement layer, not a replacement for the framework. Rocks become Objectives, key results sit underneath each Rock as measurable milestones, and the Level 10 meeting becomes the natural home for the weekly check-in. You’re not adding a new methodology. You’re adding measurable signal to the priorities EOS has already structured.
How do OKRs and Scaling Up work together?
Scaling Up’s quarterly priorities map directly to OKR objectives. Key results add the quantitative layer the One-Page Strategic Plan often leaves at the strategic-theme level. The weekly leadership meeting (not the daily huddle) is where the OKR check-in lives. The framework provides the direction. OKRs provide the weekly progress signal.
Won’t adding OKRs create another layer of overhead?
It can, if you implement it as a parallel system. Done right, OKRs use the meetings, owners, and accountability structures your framework has already established. The check-in lives inside your existing cadence. You’re adding a confidence score and a key result number, not a new ritual.
What if our team is already executing well on EOS?
If Rocks are closing at 80% or higher consistently, leadership isn’t surprised in week ten, and the Level 10 surfaces real decisions, you may not need OKRs. The frameworks were designed to do that work. OKRs become valuable when there’s a visibility gap between what was committed and what’s actually getting done by mid-quarter.
How long does it take to layer OKRs onto an EOS or Scaling Up implementation?
A pilot with one team that’s already running the framework well typically takes one quarter. The first few weeks are spent translating Rocks or priorities into OKR format and running the new check-in inside the existing meeting. By week six, the data starts surfacing the visibility gaps. By the end of the cycle, the case for expanding to other teams writes itself.
TL;DR
EOS and Scaling Up set direction and build cadence. They don’t, on their own, generate the weekly progress signal that tells you whether a quarterly priority is actually on pace at week six. That’s the gap OKRs fill. Map Rocks or quarterly priorities to objectives. Add key results as measurable milestones underneath. Run the check-in inside the meeting cadence you already have. Track confidence scores alongside the metric. The framework you’ve already built becomes measurable, not replaced. Most 60% completion problems aren’t strategy problems. They’re measurement problems.
