OKRs for Small Businesses: Ready-Made Examples by Department and How Not to Give Up in Month Two
OKRs aren't just for big companies. Examples of objectives and key results for sales, customer service, operations and marketing at a small company, and the minimum routine to keep them from dying in a drawer.
The owner of an online store with twelve employees hears about OKRs, opens an article, and finds goals like "increase global market share." She closes the tab. The conclusion is reasonable: that was written for big companies. But the idea behind OKRs fits in a company of five people, as long as you throw out the bureaucracy and keep the essentials: an objective that inspires, a few numbers that tell you whether you got there, and a routine for looking at those numbers.
Below are ready-made examples by area and the minimum routine that avoids the most common fate of OKRs: excitement in January, forgotten by March.
OKRs in two lines
The objective is what you want to change, in one sentence anyone on the team understands. The key result is the number that proves the change: it goes from one value to another, by a date. If it can't be measured, it isn't a key result, it's a task.
For the full concept, see the OKR guide. Here the focus is practice in a small company.
Examples by area
The numbers below are illustrative: swap in your own reality. The yardstick is that the key result be hard enough to require effort and possible enough that nobody gives up in the first month.
Sales
Objective: make the sales forecast reliable.
| Key result | From | To |
|---|---|---|
| Proposals sent per week | 6 | 15 |
| Proposal close rate | 18% | 25% |
| Opportunities with a next step and date logged | 40% | 100% |
Customer service
Objective: customers get answered quickly and right the first time.
| Key result | From | To |
|---|---|---|
| Time to first response | 3 hours | 30 minutes |
| Tickets resolved on first contact | 45% | 70% |
| Average score on the satisfaction survey | 3.9 | 4.5 |
Operations
Objective: deliver on time without a rush at the end of the month.
| Key result | From | To |
|---|---|---|
| Orders delivered by the agreed date | 78% | 95% |
| Rework (items returned or redone) | 12 per month | 4 per month |
| Critical routines with an owner and checklist | 3 of 10 | 10 of 10 |
Marketing
Objective: have a channel that brings in customers without depending on referrals.
| Key result | From | To |
|---|---|---|
| Qualified leads from the website per month | 20 | 60 |
| Content pieces published per month | 2 | 8 |
| Leads that become a sales meeting | 10% | 20% |
Notice a pattern: each objective has two to four key results, and they mix volume, quality, and habit. Volume alone produces people chasing an empty number; habit alone produces a pretty report with no effect.
What separates a key result from a task
"Launch the new website" is a task: it happens or it doesn't. "Increase website leads from 20 to 60 per month" is a key result: it measures the effect. The task is the path; the key result is the destination. A good goal has both, and the link between them is what keeps the goal from becoming decoration. We wrote about this in OKRs linked to tasks.
How to write an objective that works
A good objective fits in one sentence, has no number, and makes you want to act. "Be the store that delivers fastest in the region" is an objective. "Increase satisfaction by 12%" is a key result in disguise. If the team reads the objective and doesn't know what would change on Monday, the sentence is too abstract; if they read it and think it's just another spreadsheet goal, it's too bureaucratic.
Three quick tests before closing the list:
- The hallway test. Ask someone on the team to repeat the objective without looking. If they can't, simplify.
- The deadline test. Can the key results be reached within a quarter? If the answer is "maybe in a year," break it at the halfway point.
- The control test. Does the team influence the number through what it does? "Market growth" doesn't depend on you; "proposals sent" does.
How to connect OKRs to everyday work
In a small company, the biggest risk is the OKR existing in one document while the routine goes on somewhere else. The fix is to put the two things in view together: the key result and the tasks that move it. If the result is "proposals sent per week: from 6 to 15," the tasks are things like building the proposal template, separating the contact list, and reserving two mornings a week just for proposals. Each task has an owner and a date, and the board shows whether it moved.
When the key result number goes up, the team knows what caused it. When it doesn't, the check-in conversation is about which task got stuck, not about who didn't try hard enough.
The minimum routine
OKRs don't die from being badly written. They die because nobody looks at them. Two meetings are enough.
Weekly check-in (10 to 15 minutes)
- Each owner updates the value of their key result before the meeting.
- In the meeting, only three questions: did the number move? What is blocking it? What will be done this week to move it?
- Log a short comment. In three months, that history tells the story of the quarter.
Quarterly review (1 hour)
- Look at what was achieved, what stopped halfway, and what didn't move.
- For each result not achieved, ask whether the goal was wrong or the effort didn't happen. Different answers call for different decisions.
- Define the objectives for the next quarter. Keep what worked, drop what no longer makes sense.
In Tasskee, a goal has key results, check-ins, and history, and progress is calculated from them. You can link each result to the tasks that move it.
Meet goals and OKRsMistakes that kill OKRs in the second month
- Too many objectives. A small company can handle two to four objectives per quarter. Six is a wish list.
- A result you can't measure. "Improve communication" doesn't turn into a number. Look for the observable signal: response time, complaints, rework.
- A goal nobody controls. Every key result has an owner by name. "The team" is not an owner.
- Tying bonuses to the number too early. In the first cycle, people pick easy goals to secure the prize. Use the first quarter to learn.
- Confusing 100% with success. Anyone who hits every goal every quarter is setting the bar too low.
- Skipping the check-in. The week when "nobody had time" is the beginning of the end. Ten minutes with the number on screen is enough.
What to do when the number doesn't move
By the third check-in, it's normal for a key result to still be stuck. Before concluding that the goal was too ambitious, go through four questions, in this order:
- Were the agreed tasks done? If not, the problem is execution, and the conversation is about time and priority.
- Were they done and the number didn't move? Then the hypothesis was wrong. Change the tactic, not the goal.
- Is the number measured reliably? Sometimes progress exists and the record doesn't keep up.
- Does the goal still make sense? If the context changed, like a big client leaving or a campaign being canceled, adjusting is maturity, not failure. Record the change and the reason.
This sequence prevents two opposite mistakes: blaming people for a bad hypothesis and stubbornly holding on to a goal that has lost its meaning.
How to start this quarter
- Pick one or two objectives, the ones that hurt the most today.
- Write two to three key results for each, with the current value and the desired value.
- Give each result an owner.
- Put the weekly check-in on the calendar, with a fixed date, before wrapping up the kickoff meeting.
- For each result, list the three or four tasks that move it the most and track them on the team's board.
If you want a starting point, the OKR template has the structure ready to fill in. The rest is week-to-week discipline: OKRs work for a small company precisely because it can get everyone in the same room for ten minutes.