At the 50-to-80-person stage, OKR management breaks down the moment the planning session ends. Objectives land in docs. Work happens everywhere else. Until those two things are in the same place, strategy stays theoretical.
_______________________________________________________________________________________________________
The planning session was good. Actually good.
Leadership aligned on the priorities. Teams had real input. You left with three company objectives, nine key results, and something rarer than either: genuine buy-in. People were nodding. Someone said it was the most focused they'd felt about a quarter in years.
That was eight weeks ago. Ask anyone on the team what the Q3 objectives are today.
Go on. Ask them.
This isn't a cynicism exercise. It's a pattern. And if you're between 50 and 80 people, it's almost certainly happening to you right now - not because your team doesn't care, but because your OKRs live in the wrong place.
The Doc Nobody Opens
After the planning session, the objectives go somewhere. A Notion page. A slide in the all-hands deck. A section of the company wiki that was last edited in November.
And then the quarter starts.
The sprint backlog fills up. The client escalation lands. The hiring process drags on. The product bug turns into a three-day incident. Everyone is working - genuinely working - on things that feel urgent and real. The OKRs are not urgent. They're not even visible. They're in the doc.
No one made a decision to ignore the objectives. The work just moved faster than the strategy did. And at 60 people, there's no founder in every room to pull the thread back. The misalignment compounds quietly, one week at a time, until you're sitting in a mid-quarter review wondering how a team this capable is only 30% of the way to a goal everyone agreed on.
A project manager shared this exact scenario recently on Reddit:
What It's Actually Costing You
The obvious cost is missed key results.
A target you set with conviction that you hit at 40% - or don't review at all.
But the less visible cost is what happens to decision-making when there's no shared thread.
At 20 people, misalignment corrects itself in the hallway. At 70, Product prioritises features that don't move the needle. Sales chases logos that don't fit the ICP. Marketing ships campaigns that weren't connected to the growth objective anyone signed off on. Each team is busy. None of it adds up.
And because the disconnect happens gradually - one week, one sprint, one deprioritised check-in at a time - it's invisible until the quarter is already over.
By then, all you can do is explain it.
The Check-In That Keeps Getting Skipped
The standard OKR advice is weekly check-ins.
It's good advice:
And yet, almost nobody at your stage follows it consistently.
Not because the team is undisciplined. Because the check-in competes with everything else - and everything else is on fire. A 30-minute sync about key result progress loses to a customer call every single time. So it gets pushed. Then pushed again. Then it becomes a mid-quarter review. Then an end-of-quarter post-mortem.
By the time anyone looks at the objectives honestly, it's too late to change anything. The quarter was built by the work that happened, not the work that was supposed to happen. The OKRs just watched.
When The Work And The Strategy Are In The Same Place
The fix isn't a better offsite. It isn't a stricter review cadence or a more elaborate cascade framework.
It's structural. OKRs need to live where work actually gets done.
When someone opens their task board on Monday morning, they should be able to see - without switching tools or navigating to a separate doc - which objective their work this week connects to.
When a team makes a prioritisation call mid-sprint, the key results should be visible in the room, not recalled from memory. Progress should update as work moves, not when someone remembers to log it manually.
That's not a reporting upgrade. It's the difference between a strategy that gets executed and one that gets archived.
The teams that make OKRs work at your stage aren't the ones with the most sophisticated frameworks. They're the ones that made the objectives impossible to ignore - by putting them in the same rhythm, the same tools, and the same conversations as the work itself.
Strategy doesn't drift when it's embedded. It only drifts when it's stored.
