Every mid-size and enterprise HR team eventually has the same conversation. Leadership wants clearer goals. Managers want a template. Someone brings up OKRs. Someone else brings up MBOs. A newer manager asks whether the 30-60-90 day plan they used at their last company counts. Three frameworks get mixed up in one meeting, and the team walks away without a decision.
This guide is a reference for HR leaders, people managers, and operations owners who need to tell those three frameworks apart, understand what each is actually built to do, and pick the right one (or combination) for their organization. It covers the mechanics of OKRs, the origins and current use of Management by Objectives, and the specific role a 30-60-90 day plan plays in onboarding. It ends with templates you can copy, a comparison table, and a short section on where hiring intersects with goal-setting when a plan calls for scaling headcount fast.
Table of contents
- What is an OKR?
- The anatomy of an OKR
- The OKR cycle
- What is Management by Objectives (MBO)?
- What is a 30-60-90 day plan?
- OKRs vs MBOs vs 30-60-90: a comparison
- Templates you can copy
- How to choose the right framework
- Where goal-setting meets hiring
- Related resources
- FAQ
What is an OKR?
An OKR is a goal-setting framework built around one ambitious Objective and a small set of measurable Key Results. The Objective describes what you want to accomplish in qualitative, direction-setting language. The Key Results describe how you will know you got there, in numbers. Together they answer two questions a well-run team should always be able to answer: what are we trying to do, and how will we measure whether we did it.
The OKR framework was developed by Andy Grove at Intel in the 1970s as an evolution of Peter Drucker's Management by Objectives, and later brought to Google in 1999 by John Doerr, who had learned it working under Grove. Google's early adoption is the reason OKRs became the default goal-setting language in tech, and the framework is now used well beyond software: the Wikipedia entry on Objectives and key results tracks adopters across manufacturing, non-profits, and public sector organizations.
Two features distinguish OKRs from most alternatives. First, they are usually transparent across the organization: your OKRs are visible to your peers, your peers' OKRs are visible to you, and everyone can trace their team's goals up to a company-level Objective. Second, they are decoupled from compensation. Because ambitious OKRs are designed to be hard (a 70 percent score is considered a good result at Google), tying them to a bonus creates pressure to sandbag them, which defeats the purpose.
The anatomy of an OKR
Every OKR has two required parts and one optional part.
- Objective. A short, qualitative statement of what you want to achieve, written in language a person outside the team would understand. Good Objectives are ambitious enough that hitting 100 percent would feel like a genuine accomplishment. "Make onboarding a competitive advantage" is an Objective; "Improve onboarding NPS by 5 points" is not.
- Key Results. 3 to 5 measurable outcomes that, taken together, prove the Objective was met. Each Key Result is a number with a target, not a task. "Ship the new onboarding portal" is a task, not a Key Result. "Reach a 4.5 out of 5 new-hire onboarding satisfaction score by week 6" is a Key Result.
- Initiatives (optional). The concrete projects and tasks the team believes will move the Key Results. Initiatives are the "how"; they belong in a roadmap, not in the OKR itself.
The clearest way to test whether a candidate Key Result is written well is to ask: can it be graded 0.0 to 1.0 at the end of the quarter without anyone arguing about what the score means? If yes, it is a Key Result. If no, it is either a task or a wish.
| Component | What it answers | Example |
|---|---|---|
| Objective | What are we trying to accomplish? | Make our hiring funnel predictable enough to plan around. |
| Key Result 1 | How will we know? | Reduce time-to-hire from 42 days to 25 days. |
| Key Result 2 | How will we know? | Screen 100 percent of applicants within 48 hours of application. |
| Key Result 3 | How will we know? | Hold interviewer feedback SLA under 24 hours for 90 percent of loops. |
The OKR cycle
The OKR cadence is usually quarterly at the team level and annual at the company level, though smaller teams sometimes run monthly cycles and enterprises sometimes overlay both. The cycle is what turns OKRs from a document into a practice.
- Draft. Two to three weeks before the quarter starts, teams draft OKRs that ladder up to company-level Objectives. Drafting is a two-way conversation, not a top-down assignment.
- Align. Leadership reviews team OKRs for coverage (does every company Objective have owning teams) and for conflicts (are two teams counting the same Key Result). Misalignment gets resolved before the quarter starts, not during it.
- Publish. Final OKRs go into a shared tool or wiki. Everyone can see everyone else's.
- Check in. Weekly or biweekly, teams grade progress on each Key Result and flag risk. This is where the framework earns its keep, because it forces early conversations about what is off track.
- Grade. At quarter end, each Key Result gets a 0.0 to 1.0 score. Google's convention treats 0.6 to 0.7 as a good result for a genuinely ambitious OKR. A team hitting 1.0 on every OKR usually means the OKRs were not ambitious enough.
- Reflect and reset. Before the next cycle starts, teams do a short retrospective on what was learned, then draft the next round.
The Google re:Work guide on setting goals with OKRs documents the cadence Google itself uses, and remains one of the most useful primary sources on running OKRs in practice.
What is Management by Objectives (MBO)?
Management by Objectives is the older cousin of OKRs. Peter Drucker introduced the concept in his 1954 book *The Practice of Management*, and it became the dominant enterprise performance management approach through the 1960s and 1970s. Under MBO, a manager and employee jointly set specific, measurable annual objectives that align with department and company goals, review progress at set intervals, and evaluate performance against those objectives at year-end.
Three things distinguish MBO from OKRs.
- Annual cadence. MBOs are typically set at the start of the fiscal year and reviewed formally at mid-year and year-end. OKRs are usually quarterly.
- Tied to compensation. MBO results feed directly into performance ratings and, in most implementations, bonus decisions. This creates strong incentives to set achievable objectives.
- Cascaded top-down. Company objectives cascade to department, then team, then individual. The employee's role is to negotiate within a defined slot, not to propose their own top-level Objective.
MBO is not obsolete. It is still the working model at many enterprises, particularly in regulated industries, government, and traditional manufacturing, where annual planning cycles match the pace of the business. The tension MBO creates (predictability of achievable annual targets versus flexibility to respond to change) is exactly why tech companies gravitated toward OKRs. See our overview of structured versus situational interviews for a related pattern: the same tradeoff between consistency and adaptability shows up in how organizations evaluate people, not just how they set goals.
What is a 30-60-90 day plan?
A 30-60-90 day plan is a structured document for the first three months in a new role. It breaks that period into three phases with different centers of gravity:
- Days 0 to 30 — Learn. Understand the team, the product, the customers, the systems, the stakeholders, and the priorities. Outputs are notes, not deliverables. Success is measured by the quality of questions the person is asking by day 30.
- Days 31 to 60 — Contribute. Take ownership of small, well-scoped pieces of work. Build first-hand credibility with peers and stakeholders. Start reshaping tools and processes where the diagnosis from the learn phase pointed to gaps.
- Days 61 to 90 — Own. Own a meaningful slice of the role's remit end to end, with the manager's involvement dropping to review and unblock. By day 90, the new hire's calendar should look like a settled member of the team, not a new joiner.
30-60-90 day plans are most commonly written by the new hire in the first two weeks, in partnership with their manager. Some organizations expect candidates to present a draft during the final interview, particularly for leadership roles. That practice pre-dates AI and is largely a signal exercise: a good 30-60-90 tells you as much about how the candidate thinks about ramp as it does about what they plan to do.
A 30-60-90 is not a replacement for OKRs or MBOs. It is an onboarding scaffold that sits underneath whichever goal framework the company runs. Once a new hire is past day 90, they roll onto the same OKR or MBO cycle as everyone else.
OKRs vs MBOs vs 30-60-90: a comparison
The three frameworks answer different questions and work at different time horizons. The comparison below is a fast reference; the sections above have the detail.
| Dimension | OKRs | MBOs | 30-60-90 |
|---|---|---|---|
| Primary purpose | Drive ambitious change | Evaluate annual performance | Ramp a new hire |
| Time horizon | Quarterly (with annual overlay) | Annual | First 90 days |
| Direction | Mixed, transparent across org | Top-down cascade | New hire drafts, manager reviews |
| Linked to compensation | Deliberately not | Yes, in most implementations | No, it is an onboarding tool |
| Success rate expected | 60 to 70 percent (ambitious) | 90 to 100 percent (committed) | Qualitative milestones |
| Best fit | Fast-changing tech and product teams | Regulated or slower-cadence industries | Any org onboarding leaders or specialists |
Templates you can copy
Below are minimum-viable templates for each framework. They are meant to be filled in and iterated, not treated as final artifacts.
OKR template
``` Team / owner: Quarter:
Objective: (One qualitative, ambitious sentence.)
Key Result 1: Metric | Baseline | Target | Owner
Key Result 2: Metric | Baseline | Target | Owner
Key Result 3: Metric | Baseline | Target | Owner
Initiatives (optional, not scored):
- Initiative 1 — link to project
- Initiative 2 — link to project
Check-in cadence: Grading day:
```
MBO template
``` Employee: Manager: Review year:
Company objectives this ladders up to: 1. 2.
Individual objectives (3 to 5, agreed with manager):
- Objective — Success measure — Weight (%)
- Objective — Success measure — Weight (%)
- Objective — Success measure — Weight (%)
Mid-year review notes: Year-end rating: Comp / bonus recommendation:
```
30-60-90 day plan template
``` New hire: Role: Manager: Start date:
Days 0-30 — Learn
- Meet: 10 people across (team / stakeholders / customers)
- Understand: (systems, product, customer segment, KPIs)
- Deliverable: written diagnosis of the top 3 things I see, by day 30
Days 31-60 — Contribute
- Take ownership of: (small, well-scoped work)
- Ship: (concrete first deliverable)
- Relationships: (stakeholder confidence signals)
Days 61-90 — Own
- Own end to end: (meaningful slice of the role)
- Redesign or improve: (one process I have earned the right to change)
- 90-day review: agenda + expected outcomes
```
How to choose the right framework
For most modern organizations the question is not OKRs versus MBOs versus 30-60-90 in a winner-take-all sense. It is which combination fits the pace of the business and the maturity of its planning muscle.
- Fast-changing tech company. OKRs quarterly for the whole org. 30-60-90 for every new hire above IC2 or equivalent. Skip MBOs; they will feel bureaucratic and slow.
- Traditional enterprise with an annual planning cycle. MBOs at the individual level for performance and comp. Optionally OKRs at the team level for strategic initiatives that need faster iteration than the annual cycle allows. 30-60-90 for leadership hires.
- Fast-growing startup. OKRs quarterly, but keep them small (one Objective and 3 Key Results per team). Skip MBOs entirely until scale forces a formal performance system. 30-60-90 becomes essential once the team is past 30 people.
- Regulated industry. MBOs stay dominant because auditability and predictability matter more than agility. Layer OKRs onto specific transformation programs, not the whole business.
The failure mode across all four scenarios is the same: adopting a framework as a mandate without changing the underlying leadership behavior. Managers who do not run weekly check-ins will not suddenly do so because OKRs exist. Executives who set vague strategic priorities will produce vague OKRs. The framework is not the goal-setting practice, it is the container.
Where goal-setting meets hiring
Almost every serious annual or quarterly plan contains a hiring goal. "Hire 40 engineers this quarter" or "grow the sales team from 25 to 60 by year-end" shows up as a Key Result on some team's OKR page in most growing organizations. On paper it is one line. In practice it is where planning most often collides with reality.
The bottleneck is Round 1 screening. Screening consumes roughly 80 percent of time-to-hire in most enterprise recruiting functions, and it does not scale linearly with recruiter headcount. When a hiring OKR calls for 4x the interview throughput of last quarter, the screening layer decides whether the goal actually lands.
This is where Fabric fits into a goal-setting conversation. Fabric is an agentic AI platform for end-to-end hiring: once a hiring plan approves a requisition, Fabric handles sourcing, outreach, screening, scheduling, and AI-led Round 1 interviews. It connects to LinkedIn Jobs, an existing ATS, or accepts uploaded profiles, and covers the funnel from candidate discovery through Round 1. Round 1 interviews are tailored by role, with pair programming for engineering, case studies and guesstimates for product and consulting hires, and cold call and cold email simulations for sales and customer success. Cheating detection is built as a core part of the product, not an add-on, which matters in bulk hiring and campus hiring scenarios where interview integrity is the top risk. Fabric is focused on Round 1, for roles where evaluation is objective. For subjective roles such as design or content writing, a human interview is still better.
Practically, this turns "hire 40 engineers this quarter" from an aspirational Key Result into an executable pipeline: recruiters can absorb the volume without a proportional headcount increase, and the throughput number becomes something a workforce plan can rely on.
Related resources
If this piece covered how the three goal-setting frameworks relate to each other, these go deeper on the parts of the operating system they touch:
- Workforce planning: a complete guide
- Capacity planning and workforce analytics
- What are competencies? A working definition
- Learning and development strategy
- BARS: behaviorally anchored rating scales explained
- The 9-box grid and succession planning
- Attrition vs retention rate
- Structured vs situational interviews
FAQ
What is an OKR vs KPI?
An OKR is a goal-setting framework: an ambitious Objective paired with 3 to 5 measurable Key Results that show whether you got there. A KPI is a single ongoing metric a team tracks to monitor process health. OKRs drive change; KPIs monitor the status quo.
What are the 5 elements of OKR?
Most practitioners describe OKRs with five elements: a clear Objective, 3 to 5 Key Results, a defined time horizon (usually a quarter), a scoring or grading cadence, and public visibility across the organization.
What is an example of an OKR?
Objective: make the hiring funnel predictable enough to plan around. Key Results: reduce time-to-hire from 42 to 25 days, screen 100 percent of applicants within 48 hours, and hold interviewer feedback SLA under 24 hours for 90 percent of loops.
What is the difference between OKRs and MBOs?
MBOs (from Peter Drucker in 1954) set annual objectives cascaded top-down and are usually tied to compensation. OKRs (from Andy Grove at Intel, popularized by Google) are quarterly, transparent across the company, and deliberately decoupled from compensation to encourage ambition.
What is management by objectives?
Management by objectives (MBO) is a performance management approach where a manager and employee jointly set specific, measurable annual objectives that align with company goals, review progress at set intervals, and evaluate performance against those objectives at year-end.
What is a 30-60-90 day plan?
A 30-60-90 day plan is a structured document a new hire (or their manager) creates for the first three months in a role, breaking that period into learning-focused (0 to 30), contribution-focused (31 to 60), and ownership-focused (61 to 90) phases with defined goals for each.
Which framework is best for a startup?
Most startups get more out of OKRs than MBOs, because OKRs are quarterly and public, which suits a small team changing direction often. A 30-60-90 plan is not a replacement for either; it is an onboarding tool that sits underneath whichever goal framework the company uses.