An Objective Is a Stairway, Not a Wish With a Deadline
Written in January, read in December, dead in between. An objective is a lifecycle, not a sentence: hand over the choosing, calibrate the bar per person, build a stairway of small wins, and kill the dead ones in month two.
I have watched managers keep a corpse on the board for two quarters out of pure inertia. Then dock the owner for not delivering it.
Most objectives are written once and read once. Written in January, in a planning document. Read in December, in a review document. In between they do nothing.
Strange fate for the one tool whose entire job is to say what matters this quarter.
The tool is not the problem. Rodgers and Hunter ran a meta-analysis of 70 MBO programs (Journal of Applied Psychology, 1991). 68 of 70 showed productivity gains. With committed top management, the average gain was 56%. Without it: 6%. Same tool, roughly a 9x swing, decided by whether management actually engages.
Objectives rot when they arrive as something done to the person instead of built with them.
Fixing that takes a lifecycle, not a better sentence: choose it together, size it to the person, cut it into steps. Then walk it monthly, and the moment it dies, kill it.
The half everyone amputated
Peter Drucker named the idea in 1954, in The Practice of Management. Everyone remembers the name: Management by Objectives. Almost nobody reads the full chapter title: "Management by Objectives and Self-Control".
The forgotten half is the entire point.
Drucker's words: self-control means stronger motivation, "a desire to do the best rather than just enough to get by."
The compliance ritual isn't a corruption of MBO. It's MBO with the self-control half amputated. Goals cascade down, ownership never arrives, and the paperwork walks around wearing the name.
And no, the villain isn't the acronym everyone reaches for either. SMART has its own sins; I take those apart separately. The rot here sits upstream of any acronym.
Make it theirs, or don't bother
An assigned objective and a chosen one can read identically on the page. They behave like different species.
The assigned one buys compliance: the minimum that reports green. The chosen one buys someone who wants the outcome, because it's their outcome. The difference is who did the choosing.
So I don't show up to objective-setting with finished objectives. I show up with problems and directions.
"We're getting killed on on-call. I want that fixed this quarter."
Then the engineer writes what "fixed" means. They're the one who will live inside that definition for three months.
Compare the two versions.
"Improve code quality by 20%", handed down from above: a sentence nobody owns and nobody can picture.
"Stop getting paged twice a night by the ingestion pipeline": a thing a tired human will actually chase.
That gap is the most replicated finding in goal-setting research. Specific, difficult goals beat vague exhortations, with effect sizes of .42 to .80 across meta-analyses (Locke and Latham, 2002).
The mechanism is simple. A vague goal means whatever each head decides it means. "Code quality" means fourteen things to fourteen people. "Paged twice a night" means one thing to everyone, especially at 3am.
The research is narrower than my claim, so the honesty clause matters. An assigned goal with a real "why" performs about as well as a chosen one. The same goal delivered as a bare "do this" performs measurably worse (Latham, Erez and Locke, 1988).
The lever is commitment plus a reason, not choosing itself.
My experience says handing over the choosing is the cheapest way to guarantee the "why" lands. The person wrote it. Nobody fails to understand their own sentence.
The craft is to hand over the choosing without handing over the direction. Most managers run it exactly backwards. They dictate the objective down to the letter. Then they wonder why they have to nag to get it done.
Not the same bar for everyone
You want one standard and zero favoritism. You also cannot set the same bar for the engineer who has done this five times and the one who has never done it and knows it.
The veteran needs a stretch big enough to miss, or they coast and quietly resent you for wasting their year. The newcomer needs a target they can reach, or they drown, and read the drowning as proof they don't belong.
Identical objectives feel fair and are the least fair thing you can do.
The research backs the asymmetry. Commitment moderates goal performance most strongly exactly when goals are difficult (Klein et al., 1999). The veteran's stretch goal needs the ownership work more, not less.
So calibrate on purpose, and say out loud that you're doing it. Calibration looks exactly like favoritism to anyone you haven't explained it to. That is the whole reason you explain it.
It's like having kids. Same values for everyone. You still don't pretend the eight-year-old and the fifteen-year-old carry the same load. Treating them identically isn't fairness. It's laziness, and calling it fairness doesn't change which one it is.
Build the stairway
Most objectives name the destination and skip the steps. That's why December feels like one terrifying cliff.
Break the objective into a short list you can cross off. A small win every couple of weeks.
Amabile and Kramer read close to 12,000 diary entries from 238 knowledge workers across 7 companies. Nothing moved motivation and inner work life more than making progress in meaningful work ("The Power of Small Wins", HBR, 2011).
People climb toward the next checkbox long after they've stopped feeling anything about the abstract goal at the top. A stairway manufactures the strongest day-to-day motivator on record. A cliff gets you three months of dread and one bad meeting in December.
The stairway is how an objective survives the middle of the quarter, where motivation goes to die.
Walk it monthly
An objective you check twice a year is wall art.
Block real time, monthly at least. Walk the stairway. Find the step that quietly stalled before the stall becomes a postmortem. Same discipline as the one meeting you never cancel: cheap insurance, paid on schedule.
Most managers will nod along to this part. The next part is the one they skip.
Kill it in month two
Sometimes the monthly walk finds an objective that reality has overtaken. The project got cancelled. The priority moved. The problem it solved stopped mattering.
Kill it.
Out loud, on the spot, with no ceremony. Do not let it limp to December so everyone can solemnly mark it "not achieved" in a review that helps no one.
I call this the month-two kill: retiring an objective the moment it stops being true, months before the review cycle grants permission.
A dead objective left on the books is worse than no objective at all. Every day it sits there, it teaches the team that the whole exercise is fiction.
It also re-amputates Drucker's forgotten half. Nobody self-directs toward a target everyone can see is dead. One visible corpse poisons every live objective next to it.
The nerve to kill an objective in month two is rarer than the discipline to write a good one in January. It matters more. It is the single act that proves to your team the objectives are real.
The lesson is plain. An objective is not the sentence. It is the lifecycle: choose it together, size it to the person, cut it into steps, walk it monthly, and kill it when it dies.
That is why I don't show up to objective-setting with finished objectives. I show up with problems and directions.