It doesn’t have to be an OKR, but it should be something

Two companies, two opposite failures, the same root cause. The first spends three weeks at the start of every quarter perfecting the wording of its OKRs. Is this an objective or a key result? Is it measurable enough? Does it ladder correctly to the company objective above it? There are alignment sessions, and then alignment sessions about the alignment sessions. By the fourth week the OKRs are beautifully phrased and fully cascaded across every team, and by the sixth week not a single person has looked at them again. They exist, pristine and ignored, in a document that will be opened next quarter only to be rewritten.

The second company has no goal system at all, because, as its leaders explain with some pride, they move too fast for that sort of thing. Priorities are set by whoever is most persuasive in the room on a given day, direction changes with the latest conversation, and the company is extremely busy moving in several directions at once. It mistakes this for speed.

Both companies are failing at exactly the same thing, from opposite ends. Neither has a working operating cadence. The first mistook the wording for the system. The second mistook having no system for being fast. And the title of this note is the resolution to both mistakes at once: it doesn’t have to be an OKR, but it should be something.

The methodology wars are a distraction

There is a genre of debate, endless and oddly heated, about which goal-setting framework is the correct one. OKRs versus the EOS model and its Rocks, versus V2MOM, versus a clean KPI tree, versus a single North Star metric with supporting inputs. Teams treat the choice of framework as the important decision, the thing that must be gotten right before they can succeed, and they will happily spend weeks on it. It is very nearly the least important part of the entire enterprise.

Every one of these frameworks is, underneath its particular vocabulary, just a container for the same underlying activity: deciding what matters, making it explicit and shared, and checking on it regularly enough to course-correct before the quarter is lost. They differ in terminology and ceremony, not in substance. A team that runs any of them with genuine discipline will outperform a team that runs the theoretically superior one without discipline, every time and not closely. The framework is the packaging. Arguing about the packaging is a comfortable way to feel productive while avoiding the actual work, which is operating the thing week after week once you have chosen it.

What actually matters: the cadence

The variable that determines whether a goal system works is not the wording and not the framework. It is the operating rhythm around it, and it comes down to three things specifically.

First, a regular beat where you set and confirm priorities, so that what matters is decided deliberately rather than drifting. Second, a regular beat where you inspect real progress against those priorities, honestly, in a way that forces decisions rather than merely reporting status. And third, a loop that connects the priorities to the actual weekly work, so the goals show up in how people decide what to do on an ordinary Tuesday, rather than living in a document they signed in week one and never reopened. The first beat without the second is a wish list. The second without the third is theater. All three together is an operating system.

This is where goal systems actually fail, and it is almost never at the goal itself. They fail at the cadence. The objective was usually fine. What was missing was the rhythm. It was set once and never inspected. Or it was inspected, but as a passive status read-out where everyone reported green and nothing changed. Or it was never connected to the daily work, so it detached from reality and was quietly abandoned by the middle of the quarter, without anyone ever formally deciding to abandon it. A mediocre goal on a tight, real cadence will outperform a perfectly worded one with no rhythm, because the cadence is the part that actually turns a goal into behavior. The wording is just the part that is easy to argue about.

But it does have to be something

The other half of the title is for the second company, the one convinced it is too fast for goals. It is wrong, and the error is a serious one rather than a harmless preference. The faster a company moves, the more it needs a lightweight, explicit operating system, not less, because speed without alignment is simply velocity in divergent directions. That feels like progress from the inside and is mostly motion. A company sprinting without shared priorities is not agile. It is just expensive and uncoordinated, and it will discover at the end of the quarter that its considerable energy went in a dozen directions and netted out to very little.

Having no operating system is not agility. It is being unmanaged, and unmanaged organizations do not stay fast. They stay busy, which is a different and far less useful thing. The good news is that the fix is small. You do not need a heavy framework. You need something: a short list of explicit, shared priorities, a single clear owner for each, and a regular check-in where you actually look at them and make decisions. That is the minimum viable operating system, and it is genuinely most of the available value. A company running that simple loop with discipline is operating. A company with elaborate OKRs it ignores, or with nothing at all, is not. The bar is not sophistication. The bar is having something real and running it consistently.

How to choose your something

Choosing is far easier than the debates would suggest, once you accept that the framework barely matters. Pick the lightest framework your team will actually run, week after week, when it is busy and under pressure, because a system you abandon the moment things get hard is worth precisely nothing. Match the ceremony to your stage: a thirty-person company does not need OKRs cascaded across five organizational levels, and forcing that machinery onto it produces elaborate theater rather than focus, while quietly teaching everyone that the goal system is overhead to be endured. Optimize relentlessly for the question of whether you will still be doing this in week eight, not for whether the choice looks sophisticated to an outside observer or impressive in a board deck. The right answer is almost always lighter than your instinct, particularly early, and you can always add structure later when the company genuinely strains without it.

What a real weekly looks like

It helps to be concrete about the rhythm, because the word cadence can sound abstract until you see what it actually requires. A real weekly operating review is short, usually under an hour, and it is built around a single question: are we on track against the priorities we set, and if not, what are we going to do about it this week? It is not a meeting where each person narrates their activity. Activity is not progress, and a review that collects status updates produces the comfortable illusion of management without any of its substance.

The test of a real weekly is whether decisions get made in it. Something is flagged as off track, and rather than being noted for next time, it triggers a choice: reallocate effort, drop a lower priority, escalate a blocker, change the approach. If a week goes by where everything was reported green and nothing was decided, the review was theater, and the priorities have almost certainly already begun drifting away from the work without anyone noticing. The weekly is where the goals stay connected to reality, and that connection is held by forcing small course corrections continuously, while they are still small enough to be cheap.

What a real quarterly looks like

The quarterly beat does a different job. Where the weekly keeps you on track, the quarterly decides whether the track is still the right one. It is the moment to step back from execution and ask whether the priorities themselves still make sense given what the last three months actually taught you, to retire goals that no longer matter, and to set the small number that will define the next quarter. The most common failure here is treating the quarterly as a reporting exercise, a backward-looking scorecard of what got done, rather than a forward-looking decision about what to do next.

A good quarterly is ruthless about focus. It resists the temptation to carry forward everything plus a few new things, which is how priority lists swell until nothing is really a priority at all. It picks the few things that matter most for the next stage of the company and is willing to explicitly not do the rest, for now. The weekly and the quarterly together form the whole rhythm: the quarterly sets and resets the small set of things that matter, and the weekly keeps the work honestly connected to them. Neither does its job without the other, and with both in place almost any framework you choose will work.

The cadence that makes any of it work

Whatever container you choose, a few things separate a system that lives from one that decays into ignored documentation. There has to be a set rhythm, typically a weekly beat and a quarterly one, that happens whether or not anyone feels like it that week, because a cadence that runs only when convenient is not a cadence. The inspection has to be real: a review that surfaces what is off track and forces a decision about it, not a meeting where everyone reads their status aloud and leaves unchanged. The goals have to connect visibly to the weekly work, actually shaping what gets prioritized day to day, or they are a parallel fiction running alongside the real work. And there has to be a genuine willingness to re-plan mid-stream when reality changes, because a goal system that cannot adapt becomes a story everyone politely maintains while quietly doing something else entirely.

Get those right and almost any framework works. Get them wrong and the most elegantly worded OKRs in the company’s history will be forgotten by the second month of the quarter, which is the fate of most elegantly worded OKRs.

So stop arguing about whether it should be OKRs. The framework is a container. Pick the lightest one your team will actually run, and then move on with your life and your quarter. Put your energy where the outcome is genuinely decided, which is the cadence: the rhythm of setting priorities, inspecting them honestly, and re-planning when you must. It does not have to be an OKR. But it does have to be something, and that something has to have a heartbeat, because a goal system without a cadence is just a document, and a company without a goal system is just busy.

• • •

Levels Consulting helps growth-stage leaders see how their company actually operates, find the level where the real constraint lives, and build the operating system to fix it, then hand it off. Field Notes are short, practical pieces on organizational intelligence for the people running the machine.