Running Effective Quarterly Reviews
How to conduct quarterly check-ins that help your team reflect on progress, celebrate wins, and plan ahead.
A practical step-by-step guide to writing objectives and key results that actually align with your company's direction
Author
Written by the lindenquill Editorial Team, focused on practical, honest guidance for implementing OKR frameworks and quarterly reviews.
OKRs aren't just another management trend. They're a straightforward way to align your entire team around what matters most. Instead of scattered priorities and vague goals, you've got clear direction everyone understands.
The beauty of OKRs is their simplicity. An Objective is what you want to achieve. Key Results measure whether you actually got there. That's it. No complex formulas or corporate jargon needed. We're talking about focusing your team on real outcomes, not just staying busy.
If your team's been operating without a framework like this, you'll notice an immediate difference. People understand what success looks like. Meetings become more productive because everyone's working toward the same targets. And you can actually see progress.
Before you write a single OKR, know where your company's headed. Your mission isn't about this quarter or this year—it's the bigger picture. That's your north star.
Let's say you're running a SaaS platform for project management. Your mission might be: "Help teams collaborate without friction." Every OKR you set should point back to that. If an objective doesn't support your mission, it doesn't belong on your list.
Spend 30 minutes with your leadership team and write down your core mission. Don't overthink it. Two or three sentences is plenty. You'll use this to filter your OKRs all year long.
An Objective is qualitative. It's directional. It answers: "What do we want to achieve this quarter?" It's ambitious but achievable, inspiring but grounded in reality.
Here's the thing—don't confuse objectives with tasks. "Ship the new dashboard" is a task. "Make our product faster for power users" is an objective. One's a to-do. The other's a direction.
You're aiming for 3-5 objectives per team. Too many and you're scattered. Too few and you're not pushing hard enough. Each objective should be something your team can rally around.
Good Objective: "Become the easiest project tool for remote teams to adopt"
Not an Objective: "Update our onboarding flow" (that's the tactic, not the goal)
Key Results are quantitative. They're how you measure if you hit your objective. Without them, you've just got nice intentions. With them, you've got accountability.
For the objective "Become the easiest project tool for remote teams to adopt," your Key Results might be:
Reduce time-to-first-project from 8 minutes to 3 minutes
Increase user activation rate from 32% to 50%
Hit a Net Promoter Score of 60+ from customer interviews
See the difference? These are measurable. Concrete. You'll know at the end of the quarter if you made it or not. No guessing. No hand-waving.
Aim for 3-4 Key Results per Objective. They should stretch your team a bit—maybe 70% confidence you'll hit them all is the sweet spot. Too easy and they're not motivating. Too hard and morale tanks.
Company-level OKRs set the direction. But your teams need their own OKRs that support the bigger picture. This is where alignment happens. Each team's OKRs should connect back to at least one company objective.
If your company's objective is "Reduce churn by improving customer success," your support team's OKR might be "Reduce average resolution time from 6 hours to 2 hours." See how it flows? The company wants less churn. The support team contributes to that by getting faster at solving problems.
This doesn't mean every team touches every objective. It means when you're setting team-level OKRs, you're asking: "How does this support our company's direction?" If the answer's "it doesn't really," you've probably got a team-specific goal that shouldn't be an OKR.
Spend a full day on this if you can. Get teams together. Map out the connections. It's time well spent.
Building your first OKR framework doesn't require a massive project or months of planning. You need clarity on your mission, 3-5 ambitious-but-achievable objectives per team, and measurable key results that actually tell you if you won. That's the whole thing.
The real work isn't in writing them down—it's in using them. Review your OKRs weekly. Talk about progress in your team meetings. Adjust if circumstances change. And when the quarter ends, reflect on what worked and what didn't. That reflection is how you get better at this.
Your first quarter with OKRs might feel clunky. That's normal. By quarter three, your team will wonder how you ever managed without them. You'll have clarity. Alignment. Real accountability. And you'll actually know what you accomplished.
This guide is educational material designed to help you understand OKR frameworks and best practices. Every company's situation is unique—your industry, stage, culture, and team size all matter. Use these principles as a foundation, then adapt them to what works for your specific context. If you're implementing OKRs for the first time, consider working with your leadership team or a consultant familiar with your business to ensure alignment with your strategy.