OKR goal setting tends to break down before the quarter even starts. Objectives get written by leadership, handed down to teams, and quietly ignored by the people doing the work. These seven steps fix the process from the inside out.
_______________________________________________________________________________________________________
The objectives looked great on paper.
Ambitious but achievable. Clearly written. Tied to the business priorities leadership had been discussing for months. The CEO presented them at the all-hands. There was a slide. There was applause, or something close to it.
Three weeks later, the team leads had questions nobody could answer. Which objective owned the product roadmap? Who was accountable for key result three? Did the sales target assume the new hire was already ramped?
The goals weren't bad. But the people responsible for hitting them had no hand in shaping them. And that gap - between who sets the objectives and who lives with them - is where OKR goal setting fails at your stage, almost every time.
Why isolation is the real problem
At 50 to 80 people, you're past the stage where the founder can set direction and have it felt immediately at every level. But you're not yet the size where formal planning infrastructure runs itself.
That middle ground is dangerous. Leadership sets goals with full strategic context. Teams receive them without it. Nobody pushes back - not because the goals are right, but because the process didn't create space to push back. The result is a set of objectives that technically cascades but practically doesn't connect. People work. The OKRs watch.
The fix isn't softer goals or longer planning sessions. It's a different process - one that builds ownership into the goal itself, from step one.
Step 1. Start with company context, not company objectives
Before anyone writes an objective, share the strategic picture. Revenue targets, growth constraints, where the business is behind, where it has momentum. Not as a briefing - as a genuine input to the goal-setting conversation.
When teams understand the context, they write better objectives. They also ask better questions. Both are valuable.
Step 2. Let teams draft their own objectives first
Resist the instinct to cascade from the top down. Instead, ask each team lead to draft their objectives before the leadership set is finalised. What does their team need to accomplish this quarter? What would meaningful progress look like?
The drafts won't be perfect. That's the point. The conversation that follows - aligning team drafts to company priorities - is where real ownership gets built.
Step 3. Write key results with the people measuring them
Key results fail when they're assigned rather than agreed. The person accountable for a key result needs to believe the number is achievable, understand how it'll be measured, and have had a hand in setting it.
A key result written in a leadership offsite and handed to a team lead on a slide is a target. A key result written with that team lead is a commitment. The difference shows up in Q2, Q3, and Q4.
Step 4. Stress-test for conflicts before you publish
Objectives across teams will conflict. Product wants to slow down to reduce technical debt. Sales wants to accelerate. Marketing is planning a campaign that needs engineering time nobody has allocated.
Run a cross-team review before the objectives are finalised. Surface the conflicts deliberately. Resolve them explicitly. An unresolved tension in week one becomes a political problem in week eight.
Step 5. Limit objectives ruthlessly
The pressure at the 50-to-80-person stage is to honour every team's priorities by making them all official objectives. Resist it. Three to four company objectives maximum. Two to three per team.
When everything is a priority, the OKR becomes a to-do list with better branding. Focus is the point. If an initiative matters, it'll show up in the key results. If it doesn't show up there, it probably wasn't a quarterly priority - it was a standing responsibility.
Step 6. Assign one owner per key result
Not a team. Not a function. One person.
Shared ownership is unowned. When a key result is behind at the mid-quarter review, "we're all responsible" means nobody is. Name the owner in the objective-setting process, not after the fact. If you can't name one person, the key result probably needs to be rewritten.
Step 7. Build the first check-in into the goal-setting session
Before the planning session ends, schedule the first progress check-in. Put it in the calendar. Assign who presents. Define what "on track" looks like in week three.
The reason most check-ins don't happen is that they're an afterthought - something to organise later, when everyone is already back in the work. Locking in the rhythm before the quarter starts is the single most effective way to make sure the objectives don't disappear into the doc they were written in.
OKR goal setting is a conversation, not a cascade
The teams that consistently hit their objectives at your stage aren't the ones with the most sophisticated frameworks - they're the ones that treated goal-setting as a two-way process, where context flows down and input flows up.
Goals set in isolation get worked around. Goals set together get worked toward.
That shift doesn't require a new methodology or a two-day offsite - it requires giving the people closest to the work a real seat at the table before the objectives are final.
When they help shape the goal, they stop waiting to be told how it's going and start caring whether it lands.
