Rolling Out OKRs in Your First Two Quarters: A Playbook for 100 to 500 Staff
A week-by-week OKR plan for 100–500 staff: pilot teams, goal rules, software setup, check-in cadence, the first retrospective, and why pay should stay out of it for year one.
What Your First Two Quarters Have to Prove
At 100 to 500 people, the hard part of OKR implementation isn't the framework. It's getting a handful of teams to write honest goals, review them on a fixed schedule, and still be doing it in week ten, after the novelty has gone. Failed rollouts usually look alike. Leadership announces OKRs company-wide, everyone writes five objectives with four key results each, someone buys software before anyone agrees on the rules, and by the end of the quarter the goals are a stale page nobody opens.
A two-quarter plan avoids that by making the first quarter a pilot and the second a controlled expansion. You aren't trying to prove that OKRs transform the business by month six. You're trying to prove three narrower things: teams can write measurable goals without heavy coaching, a light check-in rhythm survives a busy month, and leaders use the goals to make trade-offs. Show those three and year two is worth funding. Fail, and you've lost two quarters and a small license fee, not a year of goodwill.
| Weeks | Focus | Main owner | Output |
|---|---|---|---|
| 1–3 | Sponsor, pilot team selection | CEO or COO plus HR | 3–5 pilot teams, named OKR champion per team |
| 2–4 | Goal-writing rules | HR / people ops | One-page rulebook |
| 3–5 | Software setup | HR ops plus IT | Configured tool or structured template |
| 5–13 | Pilot cycle and check-ins | Team leads | Weekly updates, mid-quarter review |
| 13–15 | Scoring and first retrospective | HR plus sponsor | Revised rules, expansion list |
| 15–26 | Expansion cycle | Department heads | 40–70% of staff on OKRs, year-two decision |
The first pilot cycle is deliberately short, about nine weeks. Treat it as a practice round and tell people so.
Weeks 1–3: Choosing a Sponsor and the Right Pilot Teams
Start with a single executive sponsor who will chair the quarterly review and publish their own objectives first. In most companies of this size that's the CEO or COO. HR can run the process, but if HR is also the sponsor, OKRs get read as an HR initiative, and line managers will treat them as paperwork.
Then pick three to five pilot teams covering roughly 30 to 80 people. Good pilot teams share a few traits:
- Measurable output. Sales, customer success, product, marketing and operations teams usually have numbers they already track. Legal or internal audit can come later.
- A manager who volunteered. A skeptical but willing lead is fine. One who was told to participate will sandbag.
- At least one cross-team dependency. Include two teams that rely on each other, say product and customer success, so you test how shared key results work.
- Different locations or time zones, if you have them. If you'll eventually run OKRs across offices in, say, Bangalore, Dubai and Lisbon, find out now whether your check-in cadence works asynchronously.
Avoid piloting with a team that's mid-reorganization, about to lose its manager, or already under a formal improvement plan. You'll learn about the team's problems, not about OKRs.
Each pilot team names an OKR champion, usually not the manager, who spends one to two hours a week keeping updates current and flagging stuck goals. By the end of week three, send a short internal note covering who's piloting, why, the dates, and a plain statement that pilot results won't feed into anyone's rating or bonus. Put that in writing now. The final section explains why.
Weeks 2–4: Writing the Goal Rules Before Anyone Writes a Goal
Your goal-setting process needs a rulebook that fits on one page. Teams skip anything longer. Draft it in week two, test it on one leadership objective in week three, and freeze it for the pilot in week four. These rules work well for a first cycle:
- Limits. Each team gets at most three objectives, each with two to four key results. Leadership sets three to five company objectives.
- Key results are outcomes, not tasks. "Reduce median first-response time from 9 hours to 4 hours" is a key result. "Launch new ticketing macros" is an initiative that supports it.
- Every key result has a baseline, a target and a data source. If nobody can say where the number comes from, rewrite it or drop it.
- Scoring is 0.0 to 1.0, and 0.6–0.7 is generally treated as a good result on stretch goals. Label each objective either "committed" (expected to hit 1.0) or "aspirational" (0.6–0.7 is success). Don't mix the two without labeling them.
- Alignment, not cascade. Team objectives should visibly support a company objective, but teams write their own. Don't copy leadership's key results down three levels.
- One owner per key result. Shared key results get a named lead owner and named contributors.
- No business-as-usual. Keeping payroll accurate is a health metric, not an OKR, unless it's currently broken.
Expect pushback on rule seven. Operations-heavy teams often feel invisible if their steady-state work isn't on the board. Give them a short "health metrics" section next to their OKRs so the work is seen without crowding the goals.
Run a 90-minute writing workshop with each pilot team in week four. Have the champion bring last quarter's real numbers so baselines are set in the room rather than guessed.
Weeks 3–5: OKR Software Setup Without Over-Engineering It
For a pilot of 30 to 80 people, a structured spreadsheet or shared document is a legitimate choice. Decide on software before the expansion starts, ideally by week 14, once you're confident you'll expand. If your HR platform already includes a goals module, turning it on costs little and saves a migration later.
| Option | Examples | Typical 2026 cost range | Best fit |
|---|---|---|---|
| Template in existing tools | Google Sheets, Excel, Notion, Confluence | No added cost | Pilot under ~60 people, uncertain commitment |
| Dedicated OKR tool | Perdoo, Weekdone, Mooncamp, Profit.co, Quantive | Roughly $5–14 per user per month | Companies wanting strong alignment views and integrations |
| Performance or engagement suite | Lattice, Leapsome, 15Five, Betterworks | Roughly $8–20+ per user per month, often bundled | Companies also buying reviews, 1:1s or surveys |
| HRIS goals module | HiBob, Personio, Workday, BambooHR add-ons | Often included or a modest add-on | Teams that value one system over OKR depth |
These are typical 2026 market ranges. Actual prices vary by contract length, seat count, region and bundle, so confirm with each vendor. Many quote annual-only contracts and minimum seat counts, which matter at the 100-person end.
Hypothetical example: say a 220-person services firm licenses a dedicated tool at $9 per user per month. Full rollout runs about $23,800 a year. Licensing only 60 pilot and expansion users for the first two quarters, if the vendor allows it, costs closer to $3,200.
Keep the configuration minimal:
- Load the org structure from your HRIS rather than by hand, so leavers and movers stay current.
- Turn on only company and team levels. Leave individual OKRs off for now.
- Connect one or two data sources, such as your CRM or support desk, for automatic key result updates. Skip the rest.
- Set check-in reminders to match the cadence in the next section.
- Check data residency and processing terms against the rules that apply to you, such as GDPR in Europe and the UK, India's DPDP Act, Brazil's LGPD or the UAE's PDPL, and ask IT to confirm single sign-on.
A red flag in vendor demos is heavy emphasis on linking individual goals to ratings, or manager dashboards that rank employees. That points to a performance-management product, which is probably what you don't want during a pilot.
Weeks 5–13: Setting an OKR Check-In Cadence That Survives Week Ten
Your check-in cadence matters more than any feature in the software. Make it too heavy and teams quietly stop. Make it too light and goals drift until the end-of-quarter scramble. This rhythm works for most pilot teams:
- Weekly, 10–15 minutes, inside an existing team meeting. Each key result owner updates progress and a confidence score (on track, at risk, off track) in the tool before the meeting. Spend the time only on at-risk items.
- Every two weeks, 30 minutes, champions with HR. Collect friction: confusing rules, broken integrations, key results nobody can measure.
- Monthly, 45–60 minutes, sponsor with pilot leads. Review cross-team dependencies and decide what to deprioritize. This is where OKRs start changing decisions.
- Week 9, mid-quarter health check. Teams may rewrite a key result once if the baseline was wrong or the business changed. Log the change and the reason.
Distributed teams should default to written asynchronous updates, with the live meeting reserved for discussion. A team split between Manila and Mexico City has no comfortable shared hour, and forcing one is how check-ins die.
Watch the update rate from week five. If fewer than roughly 70% of key results get a weekly update for two weeks running, intervene. Usually the cause is too many key results, a missing data source, or a manager who isn't asking. Fix the cause rather than sending more reminders.
In weeks 12 and 13, each team scores its key results, writes two or three sentences on what drove the score, and drafts next-quarter objectives. Scoring should take an hour per team, not a week.
Weeks 13–26: Running the First Retrospective and Expanding
Hold the first retrospective in week 13 or 14. Give it 90 minutes with the sponsor, HR, pilot managers and champions. Look at process, not team performance. Work through these questions in order:
- Which key results changed a decision or a priority? Ask for specific examples.
- Which ones were vanity metrics or disguised task lists?
- Did the cadence hold? Where did it break, and in which week?
- Were scores honest? A pilot where every team scores 0.9 or above usually set targets too low.
- What did the software help with, and what did people work around?
- Which rules need changing before expansion?
Expect to revise two or three rules. Common changes are tightening the key result limit, adding a shared-objective template for cross-team work, and clarifying how health metrics are reported.
For the second quarter, expand to 40% to 70% of the company, not everyone. Bring in whole departments so managers can align their teams with each other, and have each pilot champion coach one new team. Hold back groups where outputs are hard to measure or where change fatigue is already high. Shorten training to a 45-minute session using your own pilot OKRs as examples, which are far more convincing than textbook ones.
Run the same cadence through weeks 15 to 26 and hold a second retrospective in week 26. That meeting ends with a yes-or-no decision on company-wide rollout in year two, based on the three tests from the start: measurable goals without heavy coaching, a cadence that held, and leaders using OKRs to make trade-offs.
When to Keep OKRs Separate From Pay and Performance Ratings
Our position: for at least the first year, keep OKR scores out of compensation, bonuses and formal performance ratings. This isn't a soft preference. Once a 0.7 score can cost someone part of a bonus, people stop writing stretch goals and start writing goals they know they'll hit. You lose the honest signal that makes OKRs useful, and the program becomes a second, worse appraisal system.
Separating them doesn't mean performance reviews ignore goals. Managers can and should discuss how someone contributed to key results, how they handled a goal missed for reasons outside their control, and what they learned. What you avoid is a formula that converts OKR scores into ratings or pay.
There are narrow cases where tighter links make sense:
- Sales quotas and commission plans already tie pay to numbers. Keep those in the compensation plan and treat sales OKRs as separate improvement goals, such as shortening the sales cycle, rather than restating quota.
- Committed operational targets in a mature program, after two or more years, may feed into a company-level bonus pool. They shouldn't feed into individual scores.
Check local rules before any link to pay or individual monitoring. In countries with works councils or employee representation, such as Germany, the Netherlands and France, introducing a system that tracks individual performance can trigger consultation or co-determination requirements. Bonus plan terms in many jurisdictions are contractual, and changing the basis for variable pay may need employee consent or notice. Have employment counsel in each relevant country review the plan before connecting OKRs to pay.
A simple decision rule: if a team would write a less ambitious goal because of how it affects pay, the link is costing you more than it's worth. Put the separation statement in your week-three announcement and repeat it at the first retrospective.
Common questions
How long does OKR implementation take for a company of 100 to 500 people?
Plan on two quarters to reach a solid foundation: one pilot quarter with three to five teams, then an expansion quarter covering roughly 40% to 70% of staff. Company-wide adoption that runs without heavy HR involvement often takes three to four quarters. Moving faster tends to produce goals that are written once and never reviewed.
Do we need dedicated OKR software from day one?
No. For a pilot under about 60 people, a well-structured spreadsheet or shared document works if every key result has an owner, a baseline, a target and a data source. Buy software once you've decided to expand, or turn on the goals module in your existing HR platform if it has one.
What does OKR software typically cost?
As a typical 2026 market range, dedicated OKR tools run roughly $5–14 per user per month, and broader performance suites roughly $8–20 or more, often bundled with reviews and surveys. Prices vary by region, contract length and seat count, and many vendors require annual contracts or minimum seats. Confirm current pricing directly with vendors.
Should individual employees have their own OKRs?
Not in the first two quarters. Company and team OKRs give you alignment without multiplying admin work or creating pressure to link goals to individual ratings. Some companies add individual OKRs later for senior roles or individual contributors with clear outputs, but many never need them.
How often should teams check in on OKRs?
A short weekly update of 10–15 minutes inside an existing team meeting, a monthly leadership review, and one mid-quarter health check work for most teams. Distributed teams should default to written asynchronous updates. If weekly update rates stay low for two weeks, simplify the goals rather than adding reminders.
Can we tie OKR scores to bonuses?
You can, but during the first year it usually backfires because people stop setting ambitious goals. Keep OKRs separate from pay and formal ratings, and let managers discuss goal contributions qualitatively in reviews. Before creating any link, check local employment law, works council requirements and bonus plan terms with an employment lawyer in each country where you operate.
Written by the Group Fund Tech editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.