Quarterly goals for a ten-person company
Quarterly goals have a bad reputation in small companies, and the reputation is deserved. Most of the time the exercise goes like this: an afternoon spent writing them, a document everybody agrees with, and then eleven weeks of silence, followed by a slightly embarrassed review in which nobody can remember what was agreed.
The failure is almost never the goals themselves. Read them back at the end of the quarter and they are usually fine. The failure is that between the afternoon and the review, nobody looked.
The usual failure is the not looking, not the setting
It is worth being precise about why the looking stops, because the reason is not laziness.
Goals get written in a format that is good for writing them and bad for reading them. Long documents with context, reasoning, and carefully worded metrics. That format is right for the afternoon when you are deciding. It is wrong for a Tuesday in week six, when the question a person actually has is much smaller: is the thing I am about to spend today on one of the things we said mattered?
Answering that question should take five seconds. If it takes opening a document and reading two pages, it will not happen, and after three weeks of not happening the goals are functionally gone.
The second reason is location. The goals live somewhere the daily work does not. Every time you want to check them you leave what you are doing, go somewhere else, and come back. That trip is small, and it is enough. Anything that costs a context switch to consult gets consulted at review time and never in between.
Why one owner and daily visibility is enough
Small companies sometimes try to fix this with process: goal owners, weekly check-ins, a scoring ritual. At ten people that is more machinery than the problem needs, and the machinery itself becomes the thing that gets dropped.
There are only two requirements, and they are modest.
The first is that somebody owns the wording. Goals that anybody can edit drift, because every person who touches them adjusts them slightly towards what they are already doing. By the end of the quarter you have a set of goals that describes what happened, which is not a goal, it is a diary. One person, usually a founder or whoever runs the company day to day, keeps the text and changes it deliberately.
The second is that everybody can see them without going anywhere. Not a review, not a notification, not a summary posted on Monday. Just present, in the place where people already are, so that the five-second question has a five-second answer.
That is the whole mechanism. One owner for the words, everybody able to see them without effort. Everything else people build around quarterly goals is a substitute for one of those two things being missing.
The smallest thing that connects today to the quarter
Visibility on its own does not change what anybody does. The connection has to be made at the level of a single day, and there is a version of it that takes almost no time.
Once a day, when you decide what you are actually going to work on, look at the goals and ask one question of your list: which of these is not attached to anything we said mattered?
You will usually find two or three. That is normal and not a crime — some of what anyone does is maintenance, support, and the thing that broke this morning. The value is not in eliminating them. It is in knowing the proportion. A week where nine of your ten items are unattached is information you want in week three rather than week twelve.
The second version of the question is the one that actually moves things: for each goal, what is the next concrete thing, and does it appear anywhere on anybody’s list? A goal with nothing in front of it is not being worked on, regardless of how much anybody agrees with it. That is the single most useful check you can run, and it takes about a minute.
Neither version requires tagging your work, scoring anything, or maintaining a mapping between two systems. Reading down one list with the goals in view is enough at this size.
The mid-quarter look
Around week six, take twenty minutes. Not a meeting with the whole company unless the whole company wants one.
Three things to establish.
Which goals are on track, meaning there has been visible movement in the last two weeks. Note that this is a question about movement, not about percentage complete, because at week six percentage complete is mostly guesswork.
Which goals have had no movement at all. This is the important category and it splits in two. Either the goal still matters and nobody has started, which is a scheduling problem and can be fixed this week. Or the goal stopped mattering four weeks ago and nobody said so.
That second case deserves a direct answer rather than a quiet death. Changing a goal mid-quarter is allowed. A small company learns things in six weeks that genuinely invalidate what it decided in January, and pretending otherwise just teaches everybody that the goals are theatre. Change the text, say plainly that it changed and why, and carry on. What is not allowed is leaving a goal in place that everybody privately knows is dead, because that is what makes the next quarter’s goals unbelievable.
The third thing: is there a goal that has quietly become the only one anybody is working on? That is sometimes correct and sometimes a sign that three of the four were never realistic together.
Do not build a process around the goals
The temptation after reading something like this is to add structure: a weekly goals section in the team update, a scoring scale, a template, an owner per goal, a review cadence.
Resist most of it. Every piece of structure you add has to be maintained by somebody, and at ten people that somebody is a person whose main job is something else. The structure decays first, and when it decays it takes the goals with it, because now the goals are associated with a ritual that stopped happening.
What survives a busy quarter is short and local: goals that are visible where people already work, one person who keeps the words honest, a daily glance that costs seconds, and one twenty-minute look halfway through. That is not a process. It is four habits, and habits at this size are more durable than anything with a template.
The test is simple. If your company had a genuinely terrible month — a key person out, a customer problem that ate three weeks — would this still be happening in week ten? Anything that would not survive that month is not worth building.
Where Opitor fits
Opitor is an AI-native operating system for small companies, where every person gets their own AI chief of staff. Quarterly goals (OKR) are part of the product and are managed by administrators, so the wording has an owner and everybody else can see the goals without going anywhere. Each person’s own todos and deadlines live in the same place, which is what makes the daily glance cheap enough to actually happen, and their chief of staff follows those todos up and drafts for them without ever sending in their name. Opitor is free to start, with no paid plans yet. The questions and answers page covers what is included, and what is an AI chief of staff explains the rest.