Does a small startup need OKRs?


Usually not the full version. Before product-market fit, plans change too often for quarterly goals per team to stay useful, but the meetings around them keep going. A small team needs some parts of the system, and this article covers which ones.
It usually starts with good intentions. A founder reads about goal-setting frameworks, or the company hires someone who ran planning at a much larger organisation. Soon every team has quarterly goals, there's a weekly check-in per team, a monthly review, a leadership sync and a planning day at the end of the quarter.
Two quarters later, the goals are out of date by week four. Some meetings exist to report progress on goals nobody looks at. People update the status the night before the review. Nobody decided to work this way; the system grew faster than the company did.
Christina Wodtke, who wrote Radical Focus about working with objectives and key results, says the most common mistake is setting too many per quarter [4]. Her advice is to set one objective for the company, unless you have several separate business lines [3]. A large company running several products needs several. A team of fifteen doesn’t.
She’s also clear about timing. If a startup can’t stay on course for longer than a week, which is normal before it has found product-market fit, “you probably aren’t ready for OKRs”. And she separates goals from work: a key result describes what happened because of the work. In her words, “Save the tasks for the weekly priority list.” If every routine project gets written into the quarterly goals, the goals stop telling the team what to focus on.
If every routine project gets written into the quarterly goals, the goals stop telling the team what to focus on.
Most recurring meetings were added to fix a real problem. A handover kept failing, so there’s a sync. Two teams kept clashing, so there’s a weekly alignment. Once the problem is fixed, nobody cancels the meeting.
Constance Noonan Hadley, who studies meetings at Boston University, found that rethinking meetings fixes more than you’d expect [2]. In one company that followed the plan she and her colleagues designed, people reported a 42% rise in collaboration, and satisfaction with work-life balance went from 62% to more than 90%.
Once the problem is fixed, nobody cancels the meeting.
The third thing that keeps growing is the backlog: every idea, request and “we should” anyone has written down, groomed and re-prioritised every few weeks.
Ryan Singer, in his book Shape Up, argues against keeping one at all: “Backlogs are a big weight we don’t need to carry.” [1] The list grows to hundreds of items that everyone knows will never get done, and its length makes the team feel behind even when it isn’t. His point is that important ideas come back on their own. If nobody mentions an item for months, it probably wasn’t important.
In a small team, these few things cover most of what planning is for:
One company goal per quarter. One per business line if you really have more than one.
A weekly priority list per team. This is where the tasks go.
One weekly meeting where decisions get made. The agenda is the list of open decisions. Updates can be read beforehand.
A short review at the end of each cycle. What worked, what didn't, what to change in the next one.
And these can usually go:
Team goals that repeat the company goal in different words.
Status meetings that read out what's already written down. Read it before the meeting, or skip the meeting.
Grooming old backlog items. Archive anything nobody has mentioned in a few months.
Goals in performance reviews. Wodtke warns that if you want people to aim high, you can’t punish them for missing ambitious goals [4].
For each recurring meeting, report and planning ritual, ask one question: what decision did this change in the last month? If nobody can name one, pause it for four weeks and see who misses it. Most of the time, nobody does. If someone does, you'll find out what it was really for, and you can keep just that part.
Sources
Singer, R., Shape Up (n.d.). Bets, Not Backlogs
Thurston, A., Boston University (2018). The Curse of Meetings
Wodtke, C., Eleganthack (n.d.). One Objective to Rule Them All
Wodtke, C. (n.d.). OKR Mistakes (and how to fix them)

Edita Dermontaité
Hands-on CPO and product leader who still builds (with AI)
I’ve often been the first: the first product hire at Leadcamp and Bizzy, where I led product as CPO for five years, and the first user researcher at Lighthouse, where I spent two years building the research function.
For the past year I’ve worked as a fractional CPO and hands-on product leader, helping B2B SaaS teams between traction and scale connect what engineering builds to what brings in revenue.
I started out as a graphic designer, so I still design and test things myself, these days mostly with AI: in Claude and Lovable, or straight in code with Cursor.
Book a free 30-minute call, or a coffee in Ghent. We’ll look at what’s slowing your product down and what to do about it. I work with teams fractionally or hands-on as an embedded product leader, 2–5 days a week, depending on your needs and my availability.
Product leadership for B2B SaaS between traction and scale, from a hands-on CPO and product leader who still builds (with AI). I take product decisions off the founder’s shoulders and get product, engineering and sales moving in one direction: revenue.

New North BV
BE 1025.547.940
9050 Ghent
Belgium