peopleanalyst

Tools · General business

Mbo Designer

Cascading objectives that stay participative — designed against MBO's own pathologies.

The method

Management by Objectives (Drucker), designed against the Deming critique

The January cascade goes out, and by February every plant manager holds a quota sheet nobody discussed with them. By June they are optimizing exactly what the sheet counts and nothing it does not, and the objectives no longer describe the business — which changed in March.

The method Drucker proposed in 1954 was not the one most companies run. His phrase was management by objectives and self-control, and the second half was the point: a manager who participates in setting her objectives can manage herself against them, which is the only kind of control that scales. The cascade-as-dictation version keeps the paperwork and discards the mechanism — and it is that version W. Edwards Deming attacked when he told managers to eliminate management by objectives outright. His objection stands: a numerical goal without a method changes the reporting, not the work, and invites tunnel vision and gaming.

Bradley Hall's The New Human Capital Strategy argues the missing ingredient is discipline rather than enthusiasm. Executives agree people matter, then delegate the machinery to program-of-the-month HR. Hall's prescription — invoking Deming's manufacturing revolution as the model — is to manage human capital with the rigor applied to financial capital: define what success looks like for each role, measure it year over year, and run it as one integrated system. An objective cascade is one of the few structures that can hold that discipline, but only if every objective carries observable evidence of attainment rather than a sentiment.

Rumelt supplies the strategy-side test. His proximate objectives are targets close enough to be unambiguous and achievable, chosen because they resolve a diagnosed challenge — and his broader warning applies directly to MBO: a cascade of goals with no diagnosis behind it is bad strategy in management clothing. Every objective in the system should be able to name what it serves.

This service designs the cascade the way the critics demand it: participative setting mechanics so it does not decay into quota-assignment, a review rhythm that can revise objectives mid-cycle, each failure mode shipped with its guard, and a pay-linkage note that is honest about the gaming every linkage invites.

The books behind this tool

How it works

Designs a Management-by-Objectives system for an executive audience, grounded in the strategy corpus: a three-level objective cascade (organization → unit → individual, every objective naming what it serves, with observable evidence of attainment), the participative setting mechanics that keep it from becoming quota-assignment, and a review rhythm that can revise objectives mid-cycle. Treats the Deming critique as in-scope: failure modes (tunnel vision, sandbagging, cascade drift) each ship with their guard, and the pay-linkage note is honest about the gaming risk every linkage creates. Performix-surface tool; the SMART goal definer is the single-goal cross-reference.

You bring

{ organization, objectives, example_unit? }

You get

{ cascade[] (level · objectives: serves · evidence_of_attainment), setting_process[], review_rhythm[], pay_link_note, failure_modes[], grounded_in, provenance }

Use it for

Run it on your data

Call it on your own inputs — over the API, or hand it to your AI agent via MCP. Discovery is open; running it is metered.

REST  POST /api/bicycle/mbo-designer
MCP   design_mbo_system

← All tools