Management by Objectives
Management by Objectives (Peter Drucker, 1954) is the ancestor of the whole goal-setting shelf, and the OKR’s grandparent by direct descent: Drucker shaped Hewlett-Packard’s management system, Andy Grove rebuilt it at Intel as iMBO with objectives paired to measurable results, and Grove’s version is what John Doerr carried to Google.
Everything on this shelf is standing on Drucker's shoulders, including us.
What it teaches, and what we carry
The deepest idea is in Drucker's full phrase, the half history forgot: management by objectives and self-control. His argument was never "leaders set targets and inspect compliance"; it was that a person who understands the company's objectives can and should direct themselves, replacing supervision with self-managed commitment. That idea is alive and load-bearing in empowered OKR teams and aligned, not cascaded: teams that write their own goals against a shared strategy are practising Drucker as prescribed, seventy years on. He also gave the field its unit of management, the objective itself, and the insight that objectives exist to focus contribution, not to record activity, the earliest statement of what became outcome thinking.
What seventy years of running it taught everyone
MBO was the field's longest experiment, and its results shaped every successor. The annual cycle taught the value of a faster clock, which became the quarterly cadence with weekly check-ins. Cascade-by-decomposition taught that goals negotiated down an org chart lose the self-control that makes them work, which is why alignment replaced cascading. And wiring objectives directly to appraisal and pay taught the lesson Grove acted on at Intel and the research later confirmed: consequences change what people write. That learning, refined through our own bonus work, lives in OKRs and compensation.
The pattern to notice
None of these are failures of Drucker's idea; they are the field's collective results log, and each successor on the shelf, including the OKR, is a patch release. The concepts endured, the mechanics evolved. That is how healthy doctrine works. The lineage's proof case, Grove's Operation CRUSH, mobilised Intel through exactly this machinery.
One line to keep: the OKR is MBO with Drucker's forgotten half restored and a faster heartbeat.
Credited to Peter Drucker (The Practice of Management, 1954) and Andy Grove’s iMBO at Intel. Machinery connections are ZOKRI methodology.
What is the difference between MBO and OKRs? +
Direct descent with three patches: a quarterly clock instead of annual, alignment instead of cascade-by-decomposition, and consequences decoupled from goal scores. The OKR is MBO with Drucker’s forgotten half, self-control, restored.
We run MBO today. How hard is the move to OKRs? +
Easier than starting cold: the objective discipline exists, and what changes is the clock and the cascade. A ZOKRI implementation keeps what works and retrains the two habits that seventy years of results proved costly.
Drucker’s idea deserves modern machinery. We implement OKRs that restore the self-control MBO promised, through consulting, training and coaching that carry your managers with it.