How to Write OKRs: A Practical Guide for Small Business
How to write OKRs for small business: 7-step process, the OKR formula, good vs bad examples across functions, common mistakes, and the cycle that works.
How to Write OKRs
A practical guide for small business owners
The first time I tried to write OKRs at a company I was running, I produced a 4-page document with 8 objectives, 32 key results, and a kickoff meeting that left the team confused and exhausted. By week three, nobody could remember what was in the document. By month two, we had quietly stopped mentioning OKRs in any conversation. The framework was not the problem; my application of it was. I had treated OKRs as a corporate planning artifact rather than as a focusing tool, and the team correctly read it as bureaucracy and ignored it.
Most articles on writing OKRs are written for enterprise companies with formal goal-setting processes, dedicated OKR champions, and goal-tracking software. The advice often does not translate down to a 12-person company where the founder is also the OKR champion, the people manager, and frequently the person executing the work. Generic OKR frameworks work poorly at small business scale because they were designed for problems small businesses do not have.
This guide is different. It is written for small business owners and operators running 5-50 person companies who want to use OKRs as a focusing tool, not as a planning ritual. You will get the OKR formula, the 7-step writing process, good versus bad examples for every common business function, the quarterly cycle structure that actually works, and the common mistakes that turn OKRs into corporate theater. I built FirstHR for this audience because most performance management content assumes a level of organizational sophistication small businesses neither have nor need.
What OKRs Actually Are
The simple working description: an OKR is the answer to two questions paired together. The objective answers "what meaningful outcome do you want to achieve in the next 90 days?" The key results answer "how will you know you achieved it?" Both questions are required; either alone produces something less useful than OKRs.
Three things are true about every OKR that drives results. First, the objective is qualitative and meaningful. It describes a future state worth working toward, not a project you plan to ship. Second, the key results are quantitative and specific. Each one names a metric, a target, and a date. Vague key results produce vague behavior; specific key results produce specific behavior. Third, the cadence is consistent. Weekly check-ins translate the quarterly OKRs into weekly behavior. Without the cadence, OKRs become forgotten planning artifacts within 6 weeks.
Most failures in OKR writing happen because at least one of those three is missing. The objectives are activities ("launch the new website") instead of outcomes ("convert more visitors into customers"). The key results are vague ("improve customer satisfaction") instead of measurable ("increase NPS from 32 to 45"). Or the cadence never starts. Each missing piece reduces the framework's effectiveness by 30-50%; missing all three produces what most teams call "OKRs that did not work."
Why OKRs Look Different at Small Business Scale
Most OKR guides are written for enterprise companies with hundreds of employees, formal goal-setting cycles, and dedicated People Operations functions. The advice does not translate cleanly to a 12-person company where the founder writes the company OKRs in 90 minutes on a Sunday afternoon and the entire team reviews them in a single Tuesday meeting. Small businesses need a different application of the framework.
Three implications for SMB OKRs. First, the formality should match the scale. A 12-person company does not need OKR-tracking software, formal calibration meetings, or quarterly OKR ceremonies. A shared document and a 15-minute weekly check-in is enough. The framework is doing the work; the rituals around it are mostly enterprise overhead. Strip the rituals; keep the framework.
Second, the founder is the most important OKR participant. In a 12-person company, the founder writes the company OKRs and is also doing meaningful work toward them. This is an advantage that enterprise CEOs do not have. Use it: company OKRs at SMB scale should be specific, ambitious, and personally relevant to the founder. Generic enterprise-style OKRs at small scale produce no engagement.
Third, the cycle length should match business reality. Quarterly cycles work for most small businesses, but some early-stage startups run 6-week cycles for faster iteration, while some stable mid-market companies use semi-annual cycles. Pick the cycle that matches how fast your strategy actually changes; trying to force a 90-day cycle on a business with 30-day strategic shifts produces OKRs that are obsolete by week 6. SHRM's performance management toolkit covers the broader principles of structured goal-setting that apply at any scale.
The OKR Formula
Every OKR follows the same structural formula: one qualitative objective paired with 3-5 quantitative key results. The formula is deliberately rigid because the rigidity prevents the most common failure modes (vague objectives, immeasurable key results, scope creep into 10+ key results).
The formula is simpler than it looks. Most OKR failures are not failures of the formula; they are failures of the writer to commit to either the qualitative or the quantitative discipline. Vague objectives that try to be measurable become weak objectives. Quantitative key results that try to be inspirational become weak key results. Keep the parts separate; let each do its job.
For the broader context on OKRs and where they fit alongside other performance management tools, the OKR guide covers the full framework foundation including history, theory, and how OKRs interact with other goal-setting systems.
For the comparison with KPIs (which are often confused with OKRs but serve different purposes), the OKR vs KPI guide covers when to use each framework and how they complement each other in a complete performance system.
A 7-Step Process for Writing OKRs
The process below produces OKRs that drive behavior change. The total time investment is 90-120 minutes for company-level OKRs, plus 60-90 minutes per team. Skipping steps produces lower-quality OKRs regardless of how good the framework is.
Two failure modes to avoid during the process. First, do not skip Step 1 (company-level objective). Most OKR failures happen because teams write team-level OKRs without a clear company-level anchor; the result is a collection of disconnected priorities pulling in different directions. Second, do not skip Step 7 (weekly cadence). The cadence is the engine that turns quarterly OKRs into weekly behavior. Without it, even perfect OKRs become forgotten documents.
Writing Objectives That Drive Behavior
Objectives are the qualitative side of the OKR. Most failures in objective writing come from either making them too vague (impossible to know if achieved) or too specific (a project plan disguised as an objective). The right level is meaningful outcome stated in plain language.
| Vague objective (avoid) | Specific outcome (use) |
|---|---|
| Increase revenue | Establish predictable revenue growth in our mid-market segment |
| Improve product | Make the onboarding experience the strongest reason customers stay past month 2 |
| Better customer success | Eliminate the predictable churn pattern at month 6 |
| More efficient operations | Cut the time engineers spend on production incidents in half |
| Strengthen the team | Build a senior engineering team that can ship without founder direction |
| Improve marketing | Build a repeatable inbound channel that scales with content investment |
Three rules for writing objectives. First, the objective is an outcome, not an activity. "Launch the new pricing page" is an activity (you can launch a bad page); "Convert more visitors into paying customers" is an outcome (the new page is one of many ways to achieve it). Second, the objective should sound like a meaningful business priority, not a corporate slogan. "Be the best" is a slogan; "Establish predictable revenue growth in mid-market" is a priority. Third, the objective should be ambitious enough that achieving it would meaningfully change the business state.
Writing Key Results That Are Measurable
Key results are the quantitative side of the OKR. Each one has three required elements: a metric, a target, and a date. Without all three, a key result is incomplete and produces no measurable accountability.
| Vague key result (avoid) | Specific key result (use) |
|---|---|
| Sell more | Close 20 new mid-market deals worth at least $25K ARR by end of Q3 |
| Build features faster | Reduce average time-to-first-value from 14 days to 4 days by Q3 |
| Improve SEO | Increase organic search traffic from 8K to 25K monthly visits by end of Q3 |
| Better retention | Reduce gross monthly churn from 3.2% to 2.0% by end of Q3 |
| Fewer bugs | Reduce production incidents from average 4 per week to 1 per week by Q3 |
| Hire faster | Reduce time-to-fill from 47 days to 30 days for engineering roles by Q3 |
| Improve culture | Reach NPS score of 60+ on quarterly team survey (currently 38) |
Three rules for writing key results. First, every key result requires a number. If you cannot put a specific target on it, you do not yet have a measurable key result. Second, every key result requires a date. Quarterly targets are the default; some key results can have intermediate dates. Third, the key results together should prove the objective. Test: if you achieve all the key results, would the objective be accomplished? If yes, the key results are well-aligned. If you could achieve all the key results without accomplishing the objective, you have the wrong key results.
OPM's performance management framework offers a useful federal-government reference for how structured measurement fits into broader performance practices. The federal context is more formal than most small businesses need, but the measurement discipline applies at any scale.
Good vs Bad OKR Examples Across Functions
The examples below cover the most common OKR contexts at small business scale. Each shows a vague (avoid) version and a specific (use) version. The pattern across all of them: the bad version is a generic statement; the good version is a specific commitment.
| Context | Bad (avoid) | Good (use) |
|---|---|---|
| Sales objective | Increase revenue | Establish predictable revenue growth in our mid-market segment |
| Sales key result | Sell more | Close 20 new mid-market deals worth at least $25K ARR by end of Q3 |
| Product objective | Improve the product | Make the onboarding experience the strongest reason customers stay past month 2 |
| Product key result | Build features faster | Reduce average time-to-first-value from 14 days to 4 days by Q3 |
| Marketing objective | Get more leads | Build a repeatable inbound channel that scales with content investment |
| Marketing key result | Improve SEO | Increase organic search traffic from 8K to 25K monthly visits by end of Q3 |
| Customer success objective | Keep customers happy | Eliminate the predictable churn pattern at month 6 |
| Customer success key result | Better retention | Reduce gross monthly churn from 3.2% to 2.0% by end of Q3 |
| Engineering objective | Ship more code | Cut the time engineers spend on production incidents in half |
| Engineering key result | Fewer bugs | Reduce production incidents from average 4 per week to 1 per week by Q3 |
The pattern: bad examples could apply to almost any company in that function; good examples could only apply to a specific company in a specific quarter facing specific challenges. The specificity is the point. OKRs that all sound the same across companies and quarters do not drive any behavior change because they make no real commitment.
Complete Company-Level OKR Examples
The examples below show complete company-level OKRs (objective + 3-5 key results) for different small business contexts. Names and specifics are illustrative; the structure and specificity discipline are what matter.
Three patterns across these examples worth noticing. First, every objective is anchored in a specific business situation, not a generic aspiration. Second, every key result includes specific numbers (current state, target, date) so the team can track progress weekly. Third, the key results together would clearly demonstrate the objective is achieved if all hit; they do not just measure activity but measure the underlying business change.
OKR Examples by Team Function
Below are examples of team-level OKRs across the most common small business functions. Each team OKR should align with a company-level priority, but team teams own their specific objective and key results.
| Function | Sample objective | Sample key result |
|---|---|---|
| Sales | Establish predictable revenue growth in mid-market | Close 20 deals worth $25K+ ARR each by end of Q3 |
| Marketing | Build a repeatable inbound channel | Generate 200 qualified leads/month from content by end of Q3 |
| Product | Make onboarding the strongest reason to stay | Reduce time-to-first-value from 14 to 4 days |
| Engineering | Cut incident response burden in half | Reduce production incidents from 4/week to 1/week |
| Customer Success | Eliminate predictable churn at month 6 | Reduce gross monthly churn from 3.2% to 2.0% |
| People/HR | Build hiring capability that scales | Reduce time-to-fill from 47 to 30 days for engineering roles |
| Finance | Build cash predictability | Achieve 90-day cash flow forecast accuracy of 95%+ |
| Operations | Eliminate the delivery bottleneck | Reduce order-to-shipment time from 9 to 4 days |
The pattern: each team OKR is specific to that function's contribution to the company priority. Sales drives revenue; Customer Success eliminates churn; Engineering reduces incidents. These are not arbitrary metrics; each one represents a meaningful business outcome that the team can directly affect through their work.
For the broader practice of measuring performance across the company alongside OKRs, the KPI guide covers the ongoing metrics that complement quarterly OKRs. SHRM's research on organizational development covers how goal-setting fits into broader people development practices.
The OKR Cycle Structure
OKRs work as a cycle, not as a one-time exercise. The cycle is what produces compounding learning over quarters; without it, OKRs are just quarterly planning theater. Below is the standard 13-week quarterly cycle structure that works at small business scale.
| When | What happens | Time investment |
|---|---|---|
| Week 0 (before cycle starts) | Founder writes draft company OKRs; shares with leadership for input | 60-90 min |
| Week 1 | Company OKRs finalized and shared. Teams draft team OKRs aligned with company priorities | 60-90 min per team |
| Week 2 | Team OKRs reviewed with founder; final adjustments. Weekly check-ins scheduled in calendar | 30 min per team |
| Weeks 3-12 | Weekly 15-minute team check-ins on key results progress. Adjust if reality has changed | 15 min/team/week |
| Week 6 (mid-cycle) | Mid-cycle review: which OKRs are on track, which need to change, what blockers exist | 30-45 min per team |
| Week 12 (cycle end) | Cycle review: what did we accomplish, what did we learn, what changes for next cycle | 60-90 min |
| Week 13 (between cycles) | Buffer week. Reset, plan next cycle, do not stack cycles back-to-back | Optional buffer |
Three rules for the cycle. First, the cadence is non-negotiable. Weekly check-ins, mid-cycle review, end-of-cycle review. Without these, OKRs decay within 6 weeks. Second, the buffer week between cycles matters; teams that immediately stack the next cycle on top of the previous one without reset never have time to learn from what worked. Third, the cycle review is the highest-leverage meeting in the entire OKR system. Skipping it once costs most of the value; skipping it routinely produces teams that have done OKRs for years without getting better at them.
The Weekly Check-In That Makes OKRs Work
Weekly check-ins are the engine that turns quarterly OKRs into weekly behavior. Most OKR failures are not failures of writing; they are failures of cadence. Teams that write good OKRs but skip weekly check-ins produce nothing; teams that write average OKRs but maintain the cadence produce real results.
| Element of weekly check-in | What happens | Time |
|---|---|---|
| Confidence score | Each owner rates confidence in hitting each key result on 1-10 scale | 2-3 min |
| Status update | Brief update on what moved this week toward each key result | 5-7 min |
| Blocker surfacing | What is blocking progress; who can help unblock it | 3-5 min |
| Key result adjustments | If reality has changed, surface needed adjustments (rare; mostly stay course) | As needed |
| Next week priorities | What each owner will focus on this week to move the key results | 3-5 min |
The total weekly check-in is 15-20 minutes for the team. Most teams overengineer it: 60-minute meetings, slide decks, formal reviews. The purpose is to maintain attention on the OKRs and surface blockers, not to produce documentation. Keep it short; do it every week. Gallup research on managers consistently finds that weekly cadence with employees is one of the strongest predictors of engagement; OKR check-ins are one of the highest-leverage applications of that cadence.
When OKRs Actually Work (and When They Do Not)
OKRs are not the right tool for every business situation. Honest assessment of when OKRs work and when they do not is more useful than universal endorsement.
The pattern: OKRs work as a focusing tool when the team is large enough to need coordination, the strategy is stable enough to plan around, and the founder is committed to maintaining the practice. OKRs do not work well in pre-product chaos, in companies where the founder cannot commit to the cadence, or in teams smaller than about 5 people. Small business owners considering OKRs should honestly assess whether their situation matches the "works well" column before adopting them.
For the broader context on whether OKRs make sense for your specific business situation, the OKR guide covers the full framework foundation including more detailed assessment of fit.
Common Mistakes in Writing OKRs
The mistakes below appear consistently across small businesses writing OKRs for the first time. All are avoidable once you understand the patterns.
The pattern across these mistakes: treating OKRs as a planning artifact rather than as an active operating practice. Plans get written and filed. Practices get revisited weekly. The fix for most OKR failures is not better writing; it is more honest treatment of what makes OKRs actually work as a weekly framework. Work Institute research on retention consistently finds that lack of clear direction is among the top reasons employees leave; well-run OKRs are one of the most concrete tools for providing that direction.
Writing OKRs for the First Time
The first OKR cycle is always rougher than later cycles. The team is learning the framework; the founder is learning to write meaningful objectives; the cadence has not been established. Below is the practical advice for first-time OKR writers.
| First-time pitfall | How to avoid it |
|---|---|
| Trying to make OKRs perfect on the first cycle | Aim for 'good enough.' First-cycle OKRs will be imperfect. The cycle review at the end is where you learn what to do better next time |
| Writing too many OKRs because everything feels important | Force yourself to 3 objectives maximum at company level for the first cycle. Discipline at the start prevents bloat later |
| Imposing OKRs top-down because the team has not done them before | Have the team draft their own first OKRs even if the writing is rough. Ownership matters more than perfection on the first cycle |
| Overcomplicating the tracking | First cycle: shared doc, weekly 15-minute check-in, end-of-cycle review. Skip OKR software, formal calibration, written-up cycle reviews |
| Skipping the cycle review when the cycle ends because results were mediocre | The mediocre cycle is exactly when the review matters most. The learning compounds across cycles only if you actually conduct it |
| Tying compensation to first-cycle achievement | First cycles are calibration runs. Tie compensation to OKRs only after 2-3 cycles of practice, and even then, indirectly |
The single most useful advice for first-time OKR writers: aim for "good enough first cycle" rather than "perfect first cycle." The cycle review at the end is where the learning happens; what you wrote in the first cycle matters less than what you learn from how it went. Most teams that succeed with OKRs went through 2-3 mediocre cycles before producing genuinely useful ones. Plan for the learning curve.
Tools and Templates for OKRs
The tooling for OKRs at small business scale should be lightweight. Most teams over-engineer the tooling and under-engineer the practice. Below is the practical breakdown of options.
| Tool | Best for | Tradeoffs |
|---|---|---|
| Shared text document | Most small business teams (under 25 people) | Simple, flexible, accessible. Requires manual updating but the simplicity is the point |
| Spreadsheet | Teams that want structured tracking by row | Good for tracking key result progress numerically; less good for qualitative narrative |
| Internal wiki page | Teams already using a wiki or knowledge base | Better structure than docs; integrates with other team docs |
| Dedicated OKR software | Larger SMBs with formal goal-setting culture | Built-in workflow and reminders; adds cost and complexity often unjustified at small scale |
| Project management tool integration | Teams already using project management for daily work | Connects OKRs to specific work; can dilute strategic focus into operational tasks |
For most small businesses, a shared document with company OKRs at the top, team OKRs below, and weekly check-in notes appended produces all the tracking the team needs. The tooling does not produce focus; the framework and cadence do. Resist the temptation to invest in OKR software before the practice is established; software amplifies what is working but does not fix what is broken.
How FirstHR Fits
The honest disclosure: FirstHR is not a dedicated OKR or goal-tracking platform. We do not have built-in OKR templates, key result tracking workflows, or quarterly cycle automation. The platform handles onboarding, employee profiles, document management, org charts, and the operational HR foundations that most small businesses need. OKRs, when you adopt them, will live in your shared docs or eventually in dedicated OKR software once you have grown into needing that.
That said, OKRs work better when the underlying people operations are working. A team running OKRs on top of broken onboarding will spend most of the OKR cycle compensating for unclear role expectations the new hires never had. A team running OKRs on top of consistent onboarding, clear documented roles, and structured employee profiles will produce OKR cycles that drive real progress. FirstHR exists to handle the operational HR foundation at flat-fee pricing ($98/month for up to 10 employees, $198/month for up to 50), so that owners can focus on the higher-impact work of writing meaningful OKRs and running the cycles that turn them into outcomes.
For the foundation that determines whether the team can actually execute on OKRs, the onboarding best practices guide covers what makes new hires ready for goal-driven work.
For the broader management foundation that OKRs sit on top of, the people management guide covers running a small team without enterprise overhead.
Frequently Asked Questions
How do you write OKRs?
The seven-step process: start with the company-level objective, write the objective as an outcome (not an activity), draft 3-5 key results that prove the objective, make every key result quantitative with specific numbers, aim for 70% achievement (not 100%), get team input before finalizing, and schedule weekly check-ins from day one. Each OKR has one objective (qualitative, what you want) and 3-5 key results (quantitative, how you will know). The whole framework only works with weekly cadence; OKRs written and reviewed quarterly produce nothing.
What is the OKR formula?
Objectives are written as outcomes: 'I will [achieve this meaningful outcome].' Key results are written as measurements: 'As measured by [metric] reaching [target] by [date].' The objective answers what you want to achieve; the key results answer how you will know you achieved it. Both parts are required. An objective without key results is a wish; key results without an objective are disconnected metrics. The full formula: 'I will achieve [meaningful outcome] as measured by 3-5 specific quantitative milestones each with a deadline.'
How do you write a good OKR?
Three things separate good OKRs from forgettable ones. First, the objective is an outcome, not an activity. 'Launch the new pricing page' is an activity; 'Convert more website visitors into paying customers' is an outcome that any pricing page change should serve. Second, every key result is quantitative with a specific target and date. Vague phrases like 'improve customer satisfaction' fail; 'increase NPS from 32 to 45 by end of Q3' lands. Third, the targets are aggressive enough to require real effort but not so aggressive that the team gives up. The sweet spot is 60-70% achievement.
How many OKRs should a company have?
At small business scale (5-50 people): 3-5 company-level objectives, with 3-5 key results each, per quarter. That is 9-25 key results total at the company level, which is enough focus to be meaningful and not so many that the team cannot remember them. Larger numbers signal that the company has not made hard prioritization choices. If you have 8 company-level objectives, you have priorities, not OKRs. The point of OKRs is to commit to the most important work and let the rest be regular operations.
What is the difference between objectives and key results?
An objective is qualitative: it describes what success looks like in human terms ('Establish predictable revenue growth in our mid-market segment'). A key result is quantitative: it is a specific metric with a target and date ('Close 20 mid-market deals worth $25K+ ARR by end of Q3'). Objectives capture meaning; key results capture measurement. Each OKR has exactly one objective and 3-5 key results. The objective gives the team purpose; the key results give them the testable evidence of whether they accomplished the purpose.
Should small businesses use OKRs?
Most should, with calibration to small business reality. OKRs work well when the team has 5+ people, the company has 1-2 quarters of stable strategic priorities, and the founder commits to weekly check-in cadence. OKRs do not work when the company has fewer than 5 people (overhead exceeds benefit), strategic priorities change every 3-4 weeks (use shorter cycles or different framework), or the team is in pure survival mode. The 12-person remote company with quarterly stability gets the most value; the 3-person pre-product team usually gets less.
How often should you write OKRs?
Quarterly cycles work for most small businesses. The 90-day horizon is long enough to ship meaningful work and short enough to maintain focus. Annual OKRs become irrelevant within a few months as reality changes; monthly OKRs become operational task lists without the strategic distance OKRs require. The standard cycle: 1 week to plan, 12 weeks to execute, 1 week to review and reset. Some teams run 6-week cycles for faster iteration, especially in early-stage startups; others use semi-annual for more stable mid-market companies. Quarterly is the safe default.
Should OKRs be tied to compensation?
No, not directly. When OKRs determine bonuses or raises, two predictable things happen. First, people sandbag targets to ensure they hit them, defeating the stretch-goal purpose. Second, people optimize for key result numbers without delivering the underlying objective. The cleaner approach: separate OKRs from compensation entirely. Tie compensation to performance review judgment, informed by OKR achievement among other factors, but not directly determined by it. This produces more honest goal-setting and more accurate compensation decisions.
How aggressive should OKR targets be?
Aggressive enough to require real effort, not so aggressive that the team gives up. The classic sweet spot is 60-70% achievement: targets that are uncomfortable to set, possible to hit if everything goes well, and informative if missed. Most first-time OKR writers fail in one of two directions: they play it safe (100% achievement, but the targets are boring) or aim for the moon (20% achievement, but the team is demoralized). Calibrate by reviewing past quarter results and adjusting the next round up or down based on what you learned.
Who should write OKRs at a small business?
The founder writes the company-level OKRs (3-5 objectives, 3-5 key results each). Each functional team writes its own team OKRs aligned with the company priorities. Individual contributors generally do not need formal OKRs at small business scale; their work is captured in team OKRs and weekly 1:1s. The exception: senior individual contributors whose work spans multiple functions may benefit from individual OKRs. Top-down imposed OKRs produce no ownership; collaboratively written OKRs (founder calibrates, teams own) produce real engagement.
What are good OKR examples for small business?
Strong examples include: 'Establish product-market fit signals strong enough to support Series A' with key results around ARR, retention, and customer endorsements. 'Move from project-based revenue to recurring contracts' with key results around retainer conversions and MRR growth. 'Build a brand customers actively recommend' with key results around NPS, referrals, and repeat purchase rate. The pattern: objectives are meaningful outcomes specific to your business situation, and key results are 3-5 measurable signals that prove the outcome was achieved. Avoid generic objectives like 'Increase revenue' or 'Improve customer satisfaction.'
What is the difference between OKRs and KPIs?
OKRs are time-bound goals (typically quarterly) with specific targets you are trying to achieve. KPIs are ongoing metrics you continuously track to monitor business health. An OKR might be: 'Reduce churn from 3% to 2% by Q3.' A KPI is: 'Monthly churn rate (currently 3%).' Both matter; they serve different purposes. OKRs drive change; KPIs monitor stability. A small business uses both: KPIs for the operational dashboard, OKRs for the strategic priorities of the current quarter. The two systems complement each other rather than replacing each other.