OKRs get talked about a lot and used well rarely. Most teams either ignore them or turn them into a quarterly ritual that no one looks at again until the next planning session. OKRs — Objectives and Key Results — are a simple way to name what matters this quarter (the Objective) and define how you'll know you got there (the Key Results), so a team's effort points in one direction instead of scattering. Done well, they bring focus. Done badly, they become a to-do list in disguise. Here's the practitioner's read on writing and running them for a revenue team.
What are objectives and key results, really?
An Objective is the meaningful, qualitative goal you're chasing; Key Results are the few measurable outcomes that prove you reached it. The Objective answers "what are we trying to achieve and why does it matter?" — it's meant to be ambitious and memorable, not a number. The Key Results answer "how will we know we got there?" — and they have to be measurable, so there's no arguing at quarter-end about whether you succeeded. The most important distinction is this: Key Results measure outcomes, not activity. "Send 500 emails" is a task. "Increase qualified pipeline created by the SDR team" is an outcome. Worked example: an Objective like "Make our outbound motion reliably produce pipeline" might carry Key Results such as a target for qualified meetings booked, a target for opportunities created, and a target for the conversion rate from meeting to opportunity. The Objective inspires; the Key Results keep you honest.
How do you write OKRs that actually work?
Keep them few, make every Key Result a measurable outcome, and make sure each one rolls up to something the business actually cares about. A few rules keep teams out of trouble:
- Limit the count. A small handful of Objectives, each with two to four Key Results. More than that and focus dissolves — which defeats the entire point.
- Measure outcomes, not tasks. If a Key Result is just a thing you'll do, rewrite it as the result that thing is supposed to produce.
- Make them honestly ambitious. A good Objective should feel like a stretch. If you're confident you'll hit every Key Result easily, you set the bar too low.
- Connect to the bigger picture. A team's OKRs should visibly support the company's. If nobody can explain how a Key Result helps the wider goal, question whether it belongs.
Worked example (illustrative): a revenue team rewrites "run a webinar series" — a task — into the outcome it was meant to drive: a target for influenced pipeline from those events. Now success is defined by what the work produced, not by whether the work happened.
How do you actually run OKRs through the quarter?
Set them once, then check in often — a short weekly or biweekly review where you score progress and decide what to do about it. This is where most teams fail. They write beautiful OKRs in week one and never look at them again, which turns the whole exercise into theater. The running of OKRs is more important than the writing. Each check-in, ask three things: where does each Key Result stand, what's blocking the ones that are behind, and what will we change this week as a result. Keep the cadence light and honest — a Key Result that's clearly off track should trigger a conversation, not a cover-up. At quarter-end, score them, talk about what you learned, and feed that into the next set. The score is a learning tool, not a performance review weapon — the moment people fear the number, they sandbag the goals, and the system rots.
The IV-Lead take
The hard part of OKRs was never the framework — it's the discipline to revisit them weekly and the honesty to write outcomes instead of tasks. We see two failure modes constantly. The first is the disguised to-do list, where "Key Results" are just activities the team was going to do anyway, dressed up to look strategic. The second is the set-and-forget, where great OKRs are written and then abandoned until the next planning offsite. Both waste the team's time. For a revenue team specifically, the magic is in the connection to the pipeline: when every Key Result ties to a number that actually moves revenue, OKRs stop being a planning ceremony and become the thing that keeps everyone pulling the same way. Write fewer, make them outcomes, and review them like they matter — because if you don't review them, they don't.
Want your revenue OKRs tied to numbers your CRM can actually track? Book a 30-minute portal audit — we'll show you which outcomes you can measure today and which need cleaner data first. For the bigger picture, see how we approach revenue operations.
Frequently asked questions
What's the difference between an objective and a key result?
The Objective is the qualitative, inspiring goal — what you're trying to achieve and why. Key Results are the few measurable outcomes that prove you reached it. The Objective motivates; the Key Results keep score.
How many OKRs should a team have?
Few. A small handful of Objectives, each with two to four Key Results. The whole value of OKRs is focus, and too many of them destroys exactly that.
Should OKRs measure tasks or outcomes?
Outcomes. "Send 500 emails" is a task; "increase qualified pipeline" is an outcome. If a Key Result is just an activity, rewrite it as the result that activity is meant to produce.
How often should we review OKRs?
Weekly or biweekly. Writing OKRs once and ignoring them until the next quarter is the most common reason they fail. The running of them matters more than the writing.
