I once watched a leadership team spend three full days at an offsite "doing strategy." On day three, they walked out with eighteen company-level OKRs, color-coded by function, neatly aligned in a shared deck. Everyone felt great. The CEO emailed the company that evening to announce the new strategy. There was, in any meaningful sense, no strategy. There were eighteen measurable expressions of work the company had already decided to do, with numbers attached.
This is the most common planning mistake I see at mid-market scale, and it gets more expensive the bigger the company gets. OKRs are not a strategy. They are a measurement framework that assumes the strategic choices have already been made.
What OKRs are good at
OKRs are excellent at three things, and it's worth being explicit about them because the framework genuinely earns its place when used well. They translate ambition into measurable outcomes. They create a shared language across functions for what "progress" means. And they give a leadership team a way to talk about a quarter that isn't just a list of activities.
That's a lot. Used well, OKRs answer what and how much. What outcome are we trying to move? By how much? By when? Those are valuable questions, and getting precise answers to them is harder than it looks.
But notice what OKRs don't answer. They don't answer why this and not that. They don't tell you why your company chose the enterprise segment over the SMB segment, or the platform play over the verticalised one, or this customer problem over the four other problems you could credibly solve. OKRs sit downstream of those choices. They measure progress against decisions that have already been made elsewhere.
What strategy actually is
A strategy is a small set of trade-offs that determine where the company will and won't spend itself. Which customer. Which problem. Which channel. Which capabilities to build internally and which to buy. Most importantly: which credible options are you saying no to, and why.
A good strategy is almost always painful to read in draft, because the no's are explicit. "We will not pursue the mid-market in DACH this year, even though three competitors are." "We will not build our own onboarding tooling, even though our customers complain about it." That language makes people uncomfortable, which is precisely why most companies skip writing it. They go straight to the OKRs — which describe what teams will do — and treat the absence of trade-offs as agreement on direction.
It isn't agreement. It's a deferred argument. When the OKRs collide with reality in week six, the unspoken trade-offs have to be re-litigated under pressure, usually badly.
The tell that you've conflated them
If you can't answer the following question without reaching for your OKR deck, you're conflating: What did we decide not to do this year, and why?
A real strategy produces a fast, confident answer with three or four named opportunities and a reason for each. "We're not entering France because the sales motion would dilute the German team's focus." "We're not building the analytics module because Snowflake covers 80% of customer need and we'd rather invest in workflow." "We're not chasing the enterprise segment because the procurement cycle would starve the mid-market motion that's actually working."
If instead you reach for the OKR deck and say "well, here's what we're focused on," you don't have a strategy. You have a to-do list with KPIs. The deck describes what you'll measure. It doesn't describe why.
Why this matters in execution
A team executing against OKRs without an underlying strategy will hit the numbers and miss the company. They will optimise for whichever metric is most legible, ship the work that's most ship-able, and avoid the cross-functional bets that would have moved the strategic position because cross-functional bets are hard to fit into a quarterly KR. If the only thing keeping a team honest is the measurement framework, the team will eventually find ways to make the measurement framework happy without doing the underlying work.
The strategy is what tells you which numbers were worth chasing in the first place — and which apparently-green KR was actually pointed at the wrong outcome.
The right relationship between the two
Strategy first. OKRs second. The strategy names the trade-offs and the bets. The OKRs translate those bets into measurable progress that teams can be held to. Without the first layer, the second layer is just project management with metric flair. With both layers, the system can answer the most important quarterly question: not "did we hit our numbers?" but "did hitting our numbers move us toward the position we said we wanted?"
The Vindaris view
When strategic bets, the key results that measure them, and the work currently moving them all sit in one graph, the difference between strategy and OKRs stops being philosophical. The bets are entities. The KRs link to them. The work links to the KRs. When a quarter's KRs all close green but the strategic position hasn't shifted, you can see exactly why — and the next planning cycle starts from real diagnosis rather than from another offsite full of fresh numbers.