Objectives and measurable key results for eight teams, written for companies of 30 to 200 people. Copy one, swap in your own numbers, and check it every week.
One short line a team can remember. It should matter this quarter and be a stretch, not a to-do.
Each key result is an outcome you can check: from where you are today to where you want to be.
Three to five key results per objective, each with an owner, updated weekly so problems show up early.
Company-wide OKRs set the direction for the quarter. Keep them to three or four, owned by the leadership team, so every team can see what theirs should support.
Set goals and key results in Beam, align them to company objectives, and see each week which ones are on track.
Sales OKRs should move the numbers that predict revenue, not count activity. Track calls and emails as KPIs if you need them; put the outcomes in your OKRs.
Marketing OKRs work best when they end in pipeline or revenue. Reach and engagement are useful, but only as steps toward a number sales also cares about.
Customer success OKRs should show up in retention and expansion. Activity like calls and QBRs belongs in your plan; the OKR is what those activities change.
Operations OKRs make the rest of the company faster. Measure the time, cost and errors your teams feel, not the projects that should fix them.
Engineering OKRs should describe what users and the business feel: speed, reliability and quality. Methods like Scrum or code review are how you get there, not the result.
Product OKRs should measure the change in customer behavior a feature is meant to cause. Launching the feature is the plan; adoption and results are the key results.
People OKRs should change how it feels to work here, measured in retention, engagement and hiring outcomes, not the number of programs launched.
Want the full method? Read the free OKR guide.
Most teams do best with one to three objectives a quarter, each with three to five key results. If everything is a priority, nothing is.
A key result is a measurable outcome, like “cut churn from 3% to 2%”. A task is something you do to get there, like “launch a win-back email”. Keep tasks in your plan and outcomes in your OKRs.
Usually not. Tying OKRs to pay encourages safe targets. Many teams score ambitious OKRs and treat 0.7 as a good result, then reward behavior and outcomes separately.
Weekly. A short check-in on each key result, with a status of on track, at risk or behind, is enough to spot problems while there’s still time to act.
Use them as a starting point. Replace the numbers with your own baseline and a target that stretches your team, and drop anything that isn’t a priority this quarter.