OKRs for small teams: a simpler model that actually works

Objectives and Key Results were invented by Andy Grove at Intel in the 1970s and carried into Google in 1999 by the venture capitalist John Doerr, who later set the method out in his 2018 book Measure What Matters. Both were describing organisations of thousands. A five-person team that copies that machinery wholesale ends up with more ceremony than focus. The version that works at small scale is stripped almost bare: one objective, three key results, a weekly check-in.

What are OKRs, and where did they come from?

An OKR pairs a goal with the evidence you would accept that you have met it.

The objective is the goal, stated in plain, motivating language: "become the café's first-choice coffee supplier in the city". The key results are the numbers that prove it: sign 25 new accounts, hit a 40% repeat-order rate, keep delivery complaints under 2%. Grove's original insight, as Doerr tells it, was that a good OKR answers two questions — where do I want to go, and how will I know I'm getting there — and refuses to let a team confuse activity with progress.

That discipline is genuinely useful at any size. The problem is never the core idea; it is everything large companies bolt onto it to make it work across thousands of people, most of which a small team should quietly leave behind.

Why do OKRs usually fail in small teams?

Two ways, opposite in shape.

The first is over-adoption. A team of six reads a book written for Google and dutifully sets eight objectives with five key results each, schedules quarterly grading sessions, and tries to cascade goals it has no layers to cascade to. Within a month the OKRs are a resented spreadsheet nobody updates, and the team concludes "OKRs don't work for us" when what didn't work was the corporate exhaust they attached.

The second is set-and-forget. The team runs a tidy quarterly kickoff, writes good OKRs, and never opens them again until the end-of-quarter review, at which point they discover the objective quietly stopped influencing any real decision around week three. The OKRs were fine. The absence of a rhythm killed them.

Here is the position, and we will back it: for a small team, the weekly review matters more than the quality of the OKRs themselves. A mediocre objective looked at every week will pull a team further than a beautifully crafted one looked at twice a quarter, because the point of an OKR is to guide decisions, and a goal you never revisit guides nothing.

What does a simpler OKR model for a small team look like?

Take a five-person marketing team at a software company in Leeds, led by a head of marketing called Nadia. Last quarter they were busy and scattered — a bit of everything, no clear line. This quarter they run one OKR.

• Objective: "Make our webinars the reason mid-market buyers first hear of us."
• Key result 1: Run six webinars with an average of 80 live attendees.
• Key result 2: Generate 120 qualified leads attributed to webinars.
• Key result 3: Reach a 25% webinar-to-demo conversion rate.

That is the whole plan for the quarter. One objective the whole team can recite, three numbers that settle any argument about whether it is working. There is no cascade, because there is nobody to cascade to; there is no formal grading ceremony, because the three numbers already say where they landed. When a new request lands mid-quarter — a trade-show stand, a rebrand of the blog — the OKR is the filter: does this move one of the three key results, or is it a distraction dressed as an opportunity?

The rule of thumb is one objective per small team per quarter, and never more than a handful of key results. If you find yourself needing three objectives, you probably have three teams' worth of focus and not enough people to serve them.

How do you keep OKRs alive between quarters?

With a weekly check-in that takes minutes.

Once a week the team looks at the three key results, notes what moved, and names the one thing it will push on next week. That is it — not a status meeting, not a report, a short shared ritual that keeps the objective in the room. The teams that get value from OKRs are almost always the ones that review them weekly; the teams that don't are almost always the ones that set them and looked away.

This is where a structured group tool does more than a shared document. In Bitir, a small team runs its quarter as one private group with the objective and three key results pinned at the top, and a recurring weekly check-in that asks what moved this week. Each person can also hold an individual goal that ties into the team objective, visible to them and the lead — the same manager-led rhythm we describe in running accountability groups as a manager. The OKRs stay in front of the team all quarter instead of dying in a spreadsheet tab.

Related reading: how a Bristol firm replaced monthly 360s with weekly check-ins for new managers, and how a London startup ran its new-hire cohorts as one coached group.