What is Management by Objectives (MBO), and why did OKRs replace it?

If you’ve sat through an OKR training session, you’ve heard some version of this pitch: agree on an objective, attach a few measurable results, review them regularly.

It sounds current. It isn’t. In 1954, a management consultant named Peter Drucker wrote about a system where managers and employees sit down and agree on goals together, rather than goals simply being handed down.

He called it management by objectives, or MBO.

Seventy years on, most companies running OKRs are using a modernised version of Drucker’s original idea, whether they realise it or not. Knowing where MBO came from, and why it eventually fell out of favour, explains a lot about why OKRs are built the way they are today.

What is management by objectives (MBO)?

Management by objectives is a management approach where managers and employees jointly define objectives for a given period, agree on how progress will be measured, and then use those objectives to guide day-to-day work and evaluate performance at the end of the cycle. Drucker introduced the idea in The Practice of Management (1954), and it went on to become one of the most widely adopted management theories of the 20th century.

📖 Read more: The complete history of OKRs

The core premise was simple, and it was genuinely radical for the time: people work harder toward goals they helped set, not goals that were simply assigned to them. Before MBO, most performance management was based on subjective assessment of traits and effort. Drucker’s idea shifted the conversation to concrete, agreed outcomes.

How management by objectives works

The classic MBO cycle runs in five steps:

1. Set organisational objectives. Leadership defines the overall direction for the period, typically a year.
2. Cascade objectives down. Each manager translates the top-level objective into goals for their department or team.
3. Agree individual objectives collaboratively. The manager and employee negotiate what the individual will be responsible for. This joint agreement is the defining feature of MBO, and the part that separates it from goals being assigned top-down.
4. Monitor progress. Historically light-touch: often just a single check-in partway through the year, sometimes none at all.
5. Evaluate and reward. At the end of the period, actual results are compared against the agreed objectives, and the outcome is often tied directly to the performance review and compensation decision.

Why management by objectives fell out of favour

MBO worked well enough for decades, but three structural problems eventually caught up with it.

• The annual cycle is too slow. A goal set in January can be irrelevant by June if the market, the product, or the competitive landscape shifts, and MBO has no built-in mechanism to adjust mid-year.
• Tying objectives directly to pay encourages safe goals. When your bonus depends on hitting the number you agreed to, the rational move is to negotiate a number you’re confident you’ll hit, not the number that would actually move the business forward.
• Cascading is rigid. Objectives flow down through the org chart in one direction, which works reasonably well for stable, hierarchical businesses, but breaks down for the cross-functional, fast-changing priorities most companies deal with now.

None of this means Drucker was wrong. It means the operating environment changed faster than MBO’s mechanics could keep up with.

From MBO to OKRs: what Andy Grove changed

Andy Grove, running Intel through the 1970s and 80s, kept Drucker’s foundation (agreed objectives, measured against results) but rebuilt the mechanics around it. He called his version iMBOs. Cycles got shorter, moving from annual to quarterly. Each objective got a small set of measurable key results attached to it, rather than a single vague target. And critically, Grove pushed to keep goal-setting visible and separate from compensation decisions, specifically to stop people sandbagging their own targets.

John Doerr, who worked under Grove at Intel, carried the idea to Google in 1999 and gave it the name most people know today: OKRs, objectives and key results. The DNA is unmistakably Drucker’s. The engineering around ambition, cadence, and transparency is Grove’s. If you want the full breakdown of how objectives and key results fit together in practice, our OKR framework guide covers that in more depth.

Here’s what actually changed between the two:

Does MBO still have a place today?

Some functions still run something close to classic MBO, particularly where compensation is meant to track a specific number: sales quotas, executive bonus plans, some individual performance plans. That’s not necessarily wrong for those narrow, single-metric use cases. But as a company-wide way of setting and tracking strategy, MBO has mostly been replaced, because it never solved the cadence problem or the ambition problem. OKRs (or a similar framework) largely did.

Running goals the OKR way

If your company is still running an MBO-style process (annual goals, agreed once, reviewed once, tied to comp), the mechanics of switching to OKRs are well documented. The harder part is building the actual operating rhythm underneath it: who owns setting objectives each quarter, how often the business actually checks in on them, and what stops the whole thing sliding back into an annual box-ticking exercise by year two.

That operating rhythm is what StratOps is responsible for: the function that owns the cadence connecting strategy to execution, rather than leaving it to whoever remembers to chase people before the annual review. Tools like Tability give teams a single place to run that cadence, tracking objectives, key results, and check-ins, without recreating the manual reporting overhead that made MBO’s annual review cycle such a slog.

The bottom line: Drucker was right that people work harder toward goals they helped set. Grove and Doerr were right that those goals need to move faster than once a year, and need to be kept away from the pay conversation to stay honest. Get both of those right, and you’ve got something that looks a lot less like a 1954 performance review and a lot more like how good teams actually operate today.

Ready to move past the annual review cycle?

If you’re moving your team off an MBO-style annual process and want a proper OKR cadence instead, Tability is built for exactly this. Sign up free or book 30 minutes with us and we’ll help you figure out what that looks like for your team. Tability or not, the goal is the same: fewer goals set once a year and forgotten, more goals people actually work towards.