A safe target buys a safe plan, and rarely a remarkable result

Most people set objectives they are fairly sure they will hit. It feels responsible. The plan is clear, the numbers are believable, and in December there is a tick against each one.

The cost is harder to see. A target you are sure to hit tells the plan it can be cautious, and it usually is.

Why the safe target feels right

Committed objectives have their place. If you know you can hit the number, you can build a plan backwards from it with confidence. Every checkpoint is credible. When something slips you notice, because the margin was never large.

That can also be a problem. When the target sits comfortably inside what you can already do, the work expands to fit it. There is no reason to find a faster route, so nobody looks for one. The plan is padded at the start, the effort is paced to the deadline, and the deadline is met. Nothing went wrong, and nothing remarkable happened either.

It gets worse when the target is also the grade. If missing counts as failing, the sensible move is to set a number you cannot miss. Teams do this when objectives feed straight into performance reviews, and individuals do it to themselves. Nobody calls it sandbagging. It feels like realism.

What a bigger target does to the work

I've seen a team of three take on a quarter of objectives that would have been a fair target for nine months. On the scorecard, they missed. The work needed a few more weeks.

But almost all of the progress happened inside that quarter. The size of the goal forced a focus nothing else would have. The external blockers that eventually slowed them were found in the first weeks rather than the last, because there was no slack to hide them in. I have run teams twice that size that delivered much less against targets they comfortably hit.

The same thing happened with my own running this year. I set out to get my 10k under 50 minutes. I never got near it. Injuries interrupted the year and I didn't get below 55. In reality, I was never going to get to 50. Somewhere along the way my 5k dropped under 24 minutes, which I would not have aimed at if the goal had been comfortable.

When I realised 50 was out of reach, it felt like failing. Stepping back, it was the most I have improved in a year. Both were true, but the progress was the thing worth knowing.

The target and the grade are different jobs

Earlier pieces on this blog argue that a plan should be specific enough to fail. A goal you expect to miss seems to contradict that. It doesn't, once you separate the two jobs a target does.

It sets the ambition of the plan, and it is usually also used as the verdict. A stretch objective keeps the first job and drops the second. You still build the plan backwards from the big number, and its checkpoints still tell you when it is off course. What changes is what missing means. Getting seventy percent of the way to a target that would be remarkable if hit is good performance, and should be read that way.

A committed objective keeps both jobs, and it should, because the line itself is real. Someone else depends on it. A regulator has a date. A colleague is building on your work. You need a certain amount saved before the holiday. In those cases the point is not missing, and caution is the right instinct. In my experience these are fewer than they look.

Where stretch goes wrong

There are two failure modes, and I have hit both.

The first is setting the bar so high that it stops being a target and becomes a reason not to try. A stretch objective should still be achievable, just impressive if achieved. When I have set goals beyond that, they demotivated me. If something can't be done, it's hard to see why you'd bother starting.

The second is confusion about which kind of objective it is. If you treat a target as a stretch and someone else treats it as committed, every miss looks like unreliability. In a business that matters. A missed stretch that someone built a revenue forecast on is not a stretch any more. It is a hole in the numbers. Everyone relying on an objective has to know which kind it is before the quarter starts, not after.

Label it before you set the number

The practical change is small. Before setting a target, decide which job it is doing. If something outside you depends on the line, it is committed: set it where you will reliably hit it and hold yourself to it. Otherwise it is a stretch: set it where hitting it would be impressive, plan backwards from it anyway, and read seventy percent as a good outcome.

Both kinds have their place. The problem is a target made safe to protect the grade, when nothing actually depends on it.