This post covers Management by Objectives (MBO): its origins in Drucker’s work, its core mechanics, the conditions under which it works, and the reasons it often fails. The analysis draws on paired international and emerging-market cases, including Intel and Safaricom, to test the framework against practice.
Table of Contents
- MBO Is a Goal-Setting Discipline, Not a Performance Appraisal Form
- The Framework Has Four Working Parts That Must All Function
- Cascading Objectives Align the Firm, and Cascading Badly Breaks It
- MBO Fails for Predictable Reasons, Not Mysterious Ones
- Modern Practice Has Absorbed MBO into OKRs and Balanced Scorecards
- Judgement
- References
MBO Is a Goal-Setting Discipline, Not a Performance Appraisal Form
Management by Objectives is a system in which managers and subordinates jointly set specific, measurable objectives for a defined period, then review performance against those objectives. Peter Drucker introduced the concept in The Practice of Management (1954), arguing that managers should be judged by the results they produce, not by the activities they perform. The idea was radical at the time, and it remains the conceptual base of most modern goal-setting systems.
The point most firms miss is that MBO is a discipline, not a form. Drucker’s target was managerial behavior, not paperwork. George Odiorne, in Management by Objectives (1965), extended the framework into a full cycle of objective setting, action, review, and reward, which is where most of the implementation problems begin.
The core mechanics of MBO rest on three principles:
- Joint goal setting — manager and subordinate agree the objectives together, not by decree
- Measurable results — objectives are stated in terms that can be verified at review
- Periodic review — progress is checked at defined intervals, not only at year end
When these principles are honored, MBO produces clarity, alignment, and self-management. When they are skipped, the same framework produces an annual ritual that consumes time and changes nothing.
The Framework Has Four Working Parts That Must All Function
MBO is often described as a philosophy. In practice it is a four-part operating system, and each part must function for the whole to work. Richard Babcock, in Management by Objectives: A Handbook for Managers, set out the parts clearly, and the failures I see in firms map directly onto one of the four being weak.
Key point: if any one of the four parts is missing or performed superficially, MBO degrades into a documentation exercise, and the firm loses both the clarity and the motivation the system was supposed to produce.
The four working parts are:
- Objective setting — specific, measurable, time-bound goals agreed jointly
- Action planning — the resources, steps, and checkpoints required to reach each objective
- Progress review — structured checkpoints where progress is examined and adjustments are made
- Performance evaluation — a final assessment tied to rewards, development, and the next cycle
The framework is not complicated. What is hard is the discipline of holding all four parts in place across an entire hierarchy, and that is where most firms stall.
Cascading Objectives Align the Firm, and Cascading Badly Breaks It
MBO’s real power is vertical alignment. When senior objectives cascade down through each level, every manager can see how their goals connect to the firm’s strategy. When cascading is done poorly, the same mechanism produces goal congestion, contradiction, and employee cynicism.
Intel under Andy Grove is the clearest example of cascading done well. Grove adapted MBO into what he called Objectives and Key Results, with a small number of objectives per level, explicit measures, and a strict review rhythm. The framework traveled down the hierarchy without collapsing into dozens of goals per person.
Cascading succeeds when it respects three rules:
- Few objectives per level — three to five, not fifteen, so that priorities are real priorities
- One owner per objective — shared ownership at the working level produces shared inaction
- Explicit linkage — each objective states how it serves the level above it, or it is cut
The interpretive insight is that cascading is not the same as delegation downward. It is the deliberate translation of the firm’s strategy into goals that people at every level can actually execute.
MBO Fails for Predictable Reasons, Not Mysterious Ones
Most MBO failures are not failures of the concept. They are failures of implementation that repeat across firms and industries. Harry Levinson, writing in Harvard Business Review in 1970, warned that MBO could damage motivation when it became a control device rather than a developmental one. His warning still holds.
The four recurring failure modes I see are these: objectives set by decree rather than jointly, measurements that reward the wrong behavior, reviews that become confrontations, and rewards that ignore the results the system was supposed to produce. Any one of these is enough to kill the framework.
The recurring failure modes are:
- Top-down imposition — objectives dictated, so commitment never forms
- Metric displacement — people hit the number and miss the goal the number stood for
- Review as punishment — checkpoints become audits, and honesty disappears
- Decoupled rewards — performance reviews carry no consequence, so objectives lose credibility
- Over-documentation — the form becomes the work, and the management disappears
Each of these is preventable by design. The firm chooses whether to impose goals or agree them, whether to reward the metric or the outcome, and whether the review is a learning conversation or a tribunal.
Modern Practice Has Absorbed MBO into OKRs and Balanced Scorecards
MBO did not disappear. It was absorbed. OKRs, the Balanced Scorecard, and most modern performance systems are descendants of Drucker’s and Odiorne’s work, keeping the core of objective setting, alignment, and review, and adding tighter integration with strategy and capital allocation.
Robert Kaplan and David Norton, in The Balanced Scorecard (1996), extended MBO by requiring firms to measure across financial, customer, process, and learning dimensions. John Doerr, in Measure What Matters (2018), brought OKRs into mainstream management practice, separating ambitious objectives from measurable key results.
The lineage that matters for practitioners is this:
- Drucker (1954) — managers are judged by results, not activity
- Odiorne (1965) — a full MBO cycle of set, act, review, reward
- Kaplan and Norton (1996) — measurement across four perspectives, not only financial
- Doerr (2018) — objectives and key results, with ambition separated from measurement
The interpretive insight is that firms choosing between MBO and its successors are choosing between the same underlying discipline with different packaging. What matters is whether objective setting, alignment, and review actually function, not which label the firm uses.
Judgement
The case evidence from Intel and Safaricom establishes a proposition about MBO that most textbook treatments miss: the framework is not a form to be filled in, but a discipline to be operated, and the discipline is what determines whether it works. Intel’s adaptation of MBO into OKRs worked because Grove insisted on few objectives, clear ownership, and a real review rhythm. Firms that copy the form without the discipline get documentation without results.
My position is that MBO remains one of the most useful managerial frameworks available, and it remains one of the most frequently degraded. The core insight from Drucker — that managers should be judged by what they accomplish, not by what they do — is even more relevant today than it was in 1954. But the framework only delivers that insight if the four working parts are held in place and cascading is done with discipline.
The MBO lineage in OKRs and the Balanced Scorecard shows that the underlying discipline has survived every generation of management fashion. Firms adopting a modern system should recognize that they are adopting MBO under a new name, and should apply the same rigor that made MBO work in the firms that used it well.
My recommendations follow from that conclusion:
- Set objectives jointly, not by decree — commitment comes from participation, and imposed goals rarely survive their first review
- Limit objectives to three to five per level — a list of fifteen goals is a signal that the firm has not chosen its priorities
- Measure outcomes, not activity — the point of MBO is results, and any metric that rewards motion over progress undermines the framework
- Run real review cycles — structured checkpoints with honesty and adjustment, not annual ceremonies
- Tie rewards to results and development — if reviews carry no consequence, objectives lose credibility within one cycle
MBO is a discipline that translates strategy into daily work, and firms that treat it as a discipline, not a form, keep getting the results Drucker promised seventy years ago.
References
- The Practice of Management — Peter Drucker, HarperCollins
- Management by Objectives — George Odiorne
- Management by Whose Objectives? — Harry Levinson, Harvard Business Review
- The Balanced Scorecard — Kaplan and Norton, Harvard Business Review
- Measure What Matters — John Doerr
- Safaricom company profile and operations — Safaricom
Read Also on Kat-Syd Resources Hub
Management Principles Series: Planning, Organizing, Staffing, Directing & Controlling — Foundational management functions that govern how firms plan, organise, and control.
Functional Management — The Pillars — How core business functions including HR and operations are organised and measured.
Agency and Employment Law Series — The legal foundations of employment relationships and agency.
Written by Kateule Sydney — Researcher and Writer
© 2026 Kat-Syd Resources Hub. All rights reserved.
Kat-Syd Resources Hub — Educational case studies and analytical reference