The Stretch Goal Trap: Why Pushing Harder Doesn’t Always Deliver More

More than ever, I notice leaders and managers announcing huge stretch goals that seem unlikely to be achieved. Elon Musk is a past master at this, frequently setting his teams massive targets that are missed — and yet, even when missed, the performance is often impressive.

It brings to mind a classic framework: Management by Objectives (MBO), popularised by Peter Drucker in his 1954 book The Practice of Management. Yet one question continues to challenge its practitioners: can objectives be pushed too far?

The short answer is yes — stretch goals can work, but only up to a very specific point.

At its best, MBO operates on a simple but powerful insight: moderately challenging goals work best. The framework is built on the idea that objectives should be realistic yet demanding. If targets are too easy, people tend to coast and little improvement occurs. Conversely, if objectives are too difficult — overly stretched — employees disengage, game the system, or burn out.

This dynamic is well supported by Goal Setting Theory, which shows that performance improves as goals become more difficult, but only up to an optimal level. Beyond that tipping point, performance begins to decline.

The real trouble begins when objectives are pushed beyond this optimal zone. When goals become extreme, several problems tend to emerge. Motivation drops because people stop believing success is possible. Teams may resort to shortcuts, manipulating metrics simply to “hit the number”. A narrow focus takes hold, where important but unmeasured work is ignored. Over time, sustained stretch goals exhaust teams, leading to burnout.

Because MBO relies fundamentally on commitment, extreme stretch undermines the very foundation of the system.

That said, highly ambitious targets are not always a mistake. They can be effective under specific conditions: when framed as aspirational rather than tightly linked to evaluation or pay; when psychological safety exists so that failure is not harshly punished; when resources and support are realistically available; and when stretch goals are combined with baseline, must-achieve objectives.

This begins to resemble more modern frameworks such as Objectives and Key Results (OKRs), where achieving around 70% of a stretch goal may still be considered success.

The practical takeaway is clear. Traditional MBO works best with challenging but achievable objectives. If you want to include stretch goals, separate them from strict performance evaluation.

A balanced approach is often most effective: maintain core objectives that are realistic and must be achieved, while introducing stretch objectives that drive innovation.

Comparing MBO with OKRs

To fully understand the role of stretch, it helps to compare MBO directly with OKRs. The two frameworks are closely related, yet behave quite differently in practice — particularly in terms of ambition, measurement, and culture.

The core difference lies in philosophy. MBO, rooted in Drucker’s work, focuses on achieving agreed, realistic goals tied to performance evaluation. OKRs, developed by Andy Grove and later championed by John Doerr, focus on driving ambitious outcomes, even if they are not fully achieved.

Side by side, the contrasts are clear. In terms of goal-setting style, MBO emphasises specific, achievable goals, where success usually means hitting 100%. OKRs, by contrast, are deliberately ambitious; achieving roughly 60–70% of key results is often considered strong performance. This again reflects Goal Setting Theory, with OKRs pushing towards the upper edge of difficulty.

Structurally, MBO objectives are often broader and sometimes less rigorously quantified. OKRs are highly structured: the objective is a qualitative goal — such as improving customer experience — while key results are quantitative metrics, such as reducing response time from 24 hours to 6 hours.

The link to performance and pay marks another key difference. MBO is closely tied to appraisals, bonuses, and promotion decisions. OKRs are typically decoupled from compensation, which encourages risk-taking and honesty.

Time horizons also differ. MBO often operates on annual or semi-annual cycles, whereas OKRs are usually quarterly, with frequent check-ins and adjustments. Transparency is another distinguishing factor: MBO goals may remain private or team-level, while OKRs are typically highly transparent, allowing everyone to see each other’s objectives.

Culturally, MBO drives accountability and clarity but can become bureaucratic over time. OKRs promote alignment, focus, and ambition, encouraging experimentation, though they can feel intense if overused.

The issue of stretch is where the two frameworks truly diverge. MBO works best with moderate, achievable goals; overstretching tends to break the system, leading to disengagement or metric manipulation. OKRs, however, are explicitly designed for stretch goals, where partial success is both expected and accepted.

Consider a simple example. An MBO goal might be: “Increase sales by 10% this year,” with the expectation that it will be achieved. An OKR might instead define the objective as “Dominate our market segment”, with key results including increasing sales by 25%, acquiring three major enterprise clients, and reaching 90% brand awareness. Achieving 70% of this could still be viewed as success.

So when should each be used? MBO is best suited to situations requiring predictability, clear accountability, and a strong link to performance management. OKRs are better suited to organisations seeking innovation, growth, cross-team alignment, and a culture that tolerates ambitious failure.

In reality, most organisations blend the two. MBO-style goals are often used for core operations — keeping the business running — while OKR-style stretch goals are applied to growth and innovation. This hybrid approach may offer the best of both worlds.