All posts
Nov 18, 2026·10 min read

Management by objectives (MBO): how it works and how it compares to OKR

How MBO works and differs from OKR, with a practical example and a setup for tracking goals in Vaiz.

Mike Burton
Mike Burton — Founder of Vaiz
Vaiz board and objective card illustrating management by objectives, with targets to reduce review time and limit rework.

“Improve client delivery” sounds like a reasonable goal until the team has to measure it. One manager expects faster reviews. Another cares about missed deadlines. Employees need to know which result they are responsible for before their performance is evaluated.

What is management by objectives?

Management by objectives (MBO) is a management approach in which managers and employees jointly agree on objectives and evaluate results against them. They define what success means, with individual and team objectives contributing to the organization’s broader priorities.

Peter Drucker introduced MBO in his 1954 book, The Practice of Management. The approach gives employees room to decide how to achieve the agreed result.

A creative team lead, for example, might agree to reduce internal review time while maintaining quality. The manager and lead would need to establish a baseline, a target, and a deadline, then define acceptable quality. They would also need to discuss reviewer availability and which decisions the lead can make.

How MBO works

MBO connects company priorities to results that teams and individuals can influence. A practical MBO cycle has five stages:

  1. Define the organizational priority.
  2. Agree on team and individual objectives, with success measures and deadlines.
  3. Develop an action plan and confirm the resources needed.
  4. Review progress and adjust actions or objectives when assumptions change.
  5. Evaluate results and use the findings to set the next cycle’s objectives.

Cascade goals through meaningful contributions

Cascading goals means translating a company objective into contributions at different levels.

Consider a hypothetical agency that wants to increase the share of client projects delivered on time from 78% to 90%. Internal creative reviews are one source of delay.

The creative team could agree to reduce median review time from five business days to two. Within that team, a reviewer could take responsibility for reducing overdue assigned reviews from 30% to 10%.

The reviewer can influence one cause of delay, although the company’s overall delivery rate also depends on other teams. Check that connection before approving the goals: faster creative reviews will have limited impact if most delays happen during client approval or development.

A goal setting template can help teams record the outcome, owner, timeframe, and success measure before choosing a more specialized format.

Agree on objectives with the people doing the work

Participative goal-setting gives employees a role in defining the objective and the plan for achieving it. Feedback allows them to adjust their approach as work progresses. OpenStax’s explanation of MBO treats this participation as a core part of the method.

For the creative team, the discussion might reveal that reviewers receive incomplete briefs or that nobody covers approvals when the creative director is away. A shorter review target needs a plan that addresses those constraints.

Before work begins, agree on:

  • The baseline, target, and deadline.
  • How the metric is calculated and where the data comes from.
  • The resources and decisions the owner can control.
  • The actions required from other people.
  • When progress will be reviewed and what would justify changing the goal.

Use an action plan to turn the objective into tasks with owners and deadlines.

To reduce internal creative review time, the team might introduce a brief checklist and set up a backup reviewer rota. Completing those tasks shows that the plan has been carried out. Review-time data shows whether it has worked.

A KPI dashboard can help the team compare current results with agreed targets during each review. Discuss the figures alongside changes in workload and unresolved dependencies.

MBO vs OKR

Management by objectives (MBO) is a management approach built around jointly agreed goals and performance reviews. OKR, short for objectives and key results, is a goal-setting framework that pairs each objective with measurable key results.

Teams can use OKRs within an MBO process. Review frequency, transparency, and the use of goal achievement in compensation decisions depend on implementation.

How the approaches compare

These are common practices. Each organization still needs to decide how it will share goals, review progress, and evaluate performance.

Dimension
MBO
OKR
Goal structure
An agreed objective with success criteria and a deadline
An objective supported by explicit, measurable key results
Goal-setting process
Managers and employees agree on expected contributions
Company direction combines with proposals from teams and individuals
Accountability
Often emphasizes responsibilities attached to a role; can also apply to teams
Often emphasizes shared team or organizational outcomes; individual OKRs are also possible
Planning cycle
Matches the agreed business or performance period, with interim reviews
Commonly uses quarterly cycles within a longer-term direction
Expectations
Agreed targets generally describe commitments to achieve
Goals may be committed or aspirational
Performance evaluation
Achievement can inform individual appraisal
OKR progress can inform discussion, but does not provide a complete employee evaluation
Visibility
Depends on the organization’s approach to sharing objectives
Usually emphasizes visibility across teams

Google’s guide to setting goals with OKRs describes shared visibility, contributions from different organizational levels, and regular reviews. Organizations can adopt these practices within an MBO process too.

MBO vs OKR example: the same goal in two formats

Consider a hypothetical creative team whose internal reviews currently take a median of five business days. The goal is to reduce that time without increasing rework.

An MBO agreement could read:

By the end of the quarter, reduce median internal creative review time from five business days to two, while keeping the share of approved deliverables reopened for internal quality issues at or below 10%. The creative lead owns the result.

The manager and creative lead would also agree on resources, review dates, and the action plan.

In OKR format, the same commitment could become:

Objective: Make internal creative reviews fast and dependable.

Key results:

  • Reduce median internal creative review time from five business days to two by quarter end.
  • Keep the share of approved deliverables reopened for internal quality issues at or below 10% throughout the quarter.

The creative lead remains the owner, and the second result protects quality while the team improves speed.

Both versions use the same evidence. The OKR format separates the objective from its measures, which can make several contributing results easier to discuss together. MBO can accommodate those measures too; it does not require a single number per objective.

Introducing a brief checklist and arranging reviewer coverage remain actions under either approach. They should not replace the outcome measures.

Ambition and performance evaluation need separate decisions

With OKRs, the expected level of achievement depends on whether the goal is committed or aspirational.

Google’s OKR playbook distinguishes committed goals, which teams expect to achieve fully, from aspirational goals, where the path or resources may be uncertain. Partial achievement can represent meaningful progress on an aspirational goal. It does not automatically fulfill a commitment.

At the start of the cycle, the creative team should decide whether two-day reviews are a firm commitment or an experiment in what better coordination could achieve.

Compensation needs its own discussion. When a numerical score directly determines pay, employees have a reason to negotiate easier targets or protect their results at another team’s expense. What Matters recommends keeping compensation decisions separate from OKR scores. Goal progress can still provide context for a broader performance review.

Which should your team choose?

Use MBO when the main problem is agreeing on what a person or team is responsible for delivering. It gives managers and employees a structure for discussing expectations, the support required, and the eventual results.

Use OKR when a shared priority needs several measurable outcomes and contributions from multiple teams. The format can make those relationships easier to communicate and review.

If you combine the approaches, keep one record of each objective and make the evaluation rules explicit. Separate MBO and OKR documents for the same commitment can leave people working toward different targets or deadlines.

For help writing objectives, choosing key results, and running the review cycle, see our full guide to OKRs.

Benefits and limitations

Where MBO helps

Clear objectives give employees a way to check whether their priorities match their manager’s expectations. They also give managers a more specific basis for feedback.

Involving employees in the decision can expose constraints early. Someone doing the work may know that a target depends on an unavailable specialist or an unreliable data source.

Agreed outcomes can also give employees more autonomy. When the expected result is clear, managers can discuss progress without prescribing every step.

A 1991 meta-analysis by Robert Rodgers and John Hunter found generally positive productivity results and identified top-management commitment as an important factor. Those historical findings do not establish a predictable improvement for every team adopting MBO today.

Where MBO can fail

Measurable targets can narrow attention. In the creative review example, speed alone could encourage rushed approvals. The quality threshold reduces that risk, but the team still needs to investigate why work is being reopened.

Other limitations include:

  • Objectives becoming outdated after a change in customer needs or available resources.
  • Individual targets encouraging teams to transfer work or delays to someone else.
  • Employees being judged on results they cannot reasonably influence.
  • Too much time spent updating objectives across teams and management levels.
  • Work such as mentoring or prevention receiving little attention because it is harder to measure.

The research paper Goals Gone Wild examines risks of excessive goal setting, including narrow attention and distorted behavior. Poorly designed OKRs carry these risks too.

Qualitative evidence belongs in reviews alongside the numbers. A team can hit its target while damaging customer relationships or leaving colleagues with unsustainable workloads.

Is MBO still relevant today?

MBO remains useful when people need clear performance commitments and have enough influence over the result to be accountable for it.

For a team improving a known process, such as internal reviews, the baseline and expected outcome may be clear enough to support a meaningful agreement. Frequent check-ins can keep that agreement useful even when the planning period lasts several months.

Work involving substantial uncertainty needs different expectations. A product team investigating an unfamiliar customer problem may not yet know which commercial target is realistic. Its first objective could be to gather enough evidence to choose a product direction. Delivery or adoption targets can follow once the team understands the problem.

Before adopting MBO, check whether employees can question proposed targets and whether managers can provide the resources those targets require. Agree on how to revise objectives when their assumptions no longer hold. Record the revised target and the reason for the change.

Putting MBO into practice with Vaiz

Vaiz’s ready-made OKR template provides a board for connecting initiatives to objectives. You can use it to organize the work supporting goals agreed through an MBO process.

Start with one objective:

  1. Record the agreement in a document, including the owner, timeframe, and success measures. For the creative review example, include the five-day baseline, the two-day target, and the quality threshold. Specify when the review clock starts and stops.
  2. Turn the action plan into tasks with assignees and due dates. Create tasks for the brief checklist and reviewer rota, then use the template’s Objective field to assign each initiative to the relevant goal.
  3. Record the latest measurements in the objective document, with the measurement date and a link to the underlying evidence.
  4. Review the board and the recorded metrics together. Discuss unfinished work and dependencies, then check whether review time is improving without an increase in rework.
  5. Update the plan when priorities change. Move deprioritized initiatives to the template’s Parked lane and use WIP limits to constrain active work. Record any agreed changes to the objective in its document.

If the checklist and rota are complete but review time remains at five days, investigate the delay before declaring success. The next action might be to examine how long work waits for specialist feedback.

Conclusion

Start with one objective the team can influence. Agree on the evidence of success and schedule a review early enough to change the plan. In Vaiz, keep the supporting tasks assigned to that objective and review their progress alongside the results.