Setting goals with OKRs for a small team: a simple quarterly method
A plain guide to OKRs for small teams: how many objectives to set, how to write key results that measure outcomes, a first-quarter checklist, weekly check-ins, honest scoring and the mistakes that make OKRs fail.

Small teams rarely fail for lack of ideas. They fail because everything feels equally urgent, so effort gets spread thin and nobody can say at the end of the quarter whether it was a good one. OKRs, short for objectives and key results, are a lightweight way to fix that: pick a few things that matter, say how you will know you got there, and check in often enough to change course.
This guide shows how to use OKRs in a team of three to thirty people without turning them into a bureaucracy. It covers what to write, how many to set, how to run weekly check-ins, how to score honestly and the mistakes that make OKRs fail. You can run the whole system on a shared document and a calendar reminder.
What OKRs are, and what they are not
The basic idea
The US Chamber of Commerce describes OKRs as a collaborative goal-setting method with two parts: a motivating objective and a set of measurable key results. It credits Andrew Grove of Intel with developing the method and venture capitalist John Doerr with introducing it to Google. The simple formula is "I will (objective) as measured by (key results)".
- Objective: a short, ambitious statement of what you want to achieve.
- Key results: two to five measurable outcomes that show whether you got there.
- Initiatives: the projects and tasks you choose to move the key results.
What OKRs are not
OKRs do not replace the numbers you already track to run the business. The Chamber notes that KPIs monitor ongoing operations, while OKRs push for bigger changes. Google's guide to setting goals with OKRs adds that OKRs are not performance evaluations and not a to-do list: they define the impact a team wants, and the team decides how to achieve it. Keep them separate from pay and appraisals, or people will set safe goals.
Step 1: Choose very few priorities
Start by brainstorming what matters most in the next quarter, then cut hard. The Chamber suggests about three priorities and no more than five. Google recommends three to five objectives and warns that more can overextend a team. For a small team, the lower end is wiser. If everything is a priority, nothing is.
A useful filter: "If we achieved only these, would the quarter be a success?" If the answer is no, you have the wrong list. If the answer is yes but the list has nine items, you have too many.
Step 2: Write objectives people can feel
A good objective is specific enough that anyone can tell whether it was achieved, and inspiring enough to be worth the effort. Google advises using endpoints and new achievements rather than maintenance language such as "keep hiring".
| Weak objective | Stronger objective | |---|---| | Improve marketing | Become the first choice for local home-renovation enquiries | | Keep customers happy | Make onboarding so smooth that new clients go live in a week | | Grow revenue | Win three recurring clients that pay us every month |
Step 3: Write key results that measure outcomes
Key results describe results, not activity. The Chamber points out that words like "review", "meet" or "analyze" usually signal a task rather than a result. Aim for three or so per objective, with a number, a baseline and a target, and with evidence that is easy to find.
| Objective | Key result (outcome) | Not a key result (activity) | |---|---|---| | Win three recurring clients | Sign three clients on monthly retainers by 31 March | Send 100 outreach emails | | Fast, smooth onboarding | Average time from signature to first delivery falls from 14 days to 7 | Write an onboarding document | | First choice for local enquiries | Enquiry form submissions rise from 20 to 40 a month | Redesign the website |
Activities still matter. They go underneath as initiatives: the projects and tasks you pick to move the numbers. If a key result needs several of them, treat the key result as the goal and the tasks as your plan.
Include a stretch
Both sources want OKRs to be ambitious. The Chamber suggests at least one stretch goal per cycle. Goals that are too easy fail to motivate, and goals that are too hard can lead to burnout, so say plainly which key results are stretch and which are commitments, especially when another team depends on you.
Step 4: Share, check in and score
Make them visible
Post OKRs where everyone can see them. Google advises making them public so everyone knows the organisation's priorities, and each team's goals should connect to at least one company goal. In a small team, one page for the whole business plus a short list for each person or squad is plenty.
Weekly check-ins
The Chamber describes regular check-ins, typically weekly, and Google recommends mid-quarter check-ins with a final one before grading. Keep them to fifteen minutes. For each key result, give a confidence rating, say what is blocking progress and decide one next action. If a key result is clearly out of reach, say so and adjust. Treating OKRs as fixed when conditions change is a common mistake.
Score honestly at the end of the quarter
Google grades each key result from 0.0 to 1.0 and averages them for the objective. Its target sweet spot is roughly 0.6 to 0.7: consistently scoring 1.0 suggests goals were not ambitious enough, and low scores are useful data for next quarter. Hold a short retrospective: what worked, what did not, what to carry over and what to drop.
A first-quarter checklist
- Agree the quarter's dates and who owns the process.
- List candidate priorities and cut to three.
- Write one objective for each in plain language.
- Add two to three measurable key results per objective, with a baseline.
- Mark any stretch key results.
- Share the page with the whole team and collect edits for a week.
- Set a recurring fifteen-minute weekly check-in.
- Hold a mid-quarter review and adjust.
- Score, review and write next quarter's OKRs.
Common mistakes
- Too many OKRs. Three objectives that get done beat nine that get discussed.
- Writing tasks as key results. If it can be ticked off without changing anything, it is an activity.
- Setting and forgetting. OKRs only work if you look at them every week.
- Tying them to bonuses or appraisals. People then sandbag, which Google lists among the common errors.
- Using OKRs for routine operations. Keep everyday numbers as KPIs.
- Overbuilding. The Chamber notes a small company with a few onsite staff may need only a simple template or spreadsheet, not dedicated software.
This is general business guidance, not professional advice for your situation.
How WorkBOS can help
OKRs do not require a special tool, and WorkBOS does not need one either. In WorkBOS you can write the objective in a shared document, make each initiative a project or task with an owner and due date, use team and workload views to see who is stretched, and keep the weekly check-in on the calendar. Roles and permissions let you decide who edits the page. See the docs, the Academy and the pricing page, which includes a free plan.
To connect goals to people, read one-on-one meetings that work and team accountability without micromanaging. If you are new to leading a team, start with becoming a first-time manager.
Frequently asked questions
Q: How many OKRs should a small team set? A: About three objectives with two to five key results each. Google suggests three to five objectives as a ceiling, but smaller teams do better near the bottom of that range.
Q: How are OKRs different from KPIs? A: KPIs track ongoing health, such as monthly revenue or response time. OKRs target a change you want to make this quarter. A KPI can become a key result when you want to move it.
Q: What score counts as success? A: Google treats roughly 0.6 to 0.7 as the sweet spot for ambitious goals. Reliably hitting 1.0 usually means the goals were too easy.
Q: How often should we review OKRs? A: Check in weekly or every two weeks, review properly mid-quarter, and score at the end of the quarter.
Q: Should OKRs be linked to bonuses? A: Google says OKRs are not performance evaluations. Linking them to pay tends to push people toward safe targets, so keep the two separate.
Sources are linked in the text above: US Chamber of Commerce, Google re:Work.
Run it all from one place
Projects, clients, finance, people and AI employees in one system. Start free, no card needed.
Start free →