Stretch Goals: When They Work and How to Set Them

The teams most likely to set a stretch goal are the ones least equipped to survive one. That isn’t a hot take; it’s the finding at the center of Prof. Sim Sitkin’s research at Duke: companies with recent wins and spare capacity mostly sit these out, while the team coming off a bad quarter reaches for a miracle number and calls it a reset.

Almost every guide on this topic tells you how to make the target inspiring. Inspiration isn’t the variable that decides the outcome. Two conditions and one uncomfortable question about consequences are, and you can check all three before the planning meeting starts.

TL;DR: A stretch goal is a target that appears unattainable given your team’s current skills, resources, and methods, which makes it different from a goal that’s merely hard. Most teams set a stretch goal for motivation, which is the wrong reason. Treat it as a resourcing decision instead: run the three-question test below, fund the experiments that will fail, and keep the goal out of anyone’s performance review.

Stretch Goals

What Are Stretch Goals?

A stretch goal is a target that appears unattainable given an organization’s current practices, skills, and knowledge.

Although the concept of stretch goals was first popularized by GE CEO Jack Welch, that definition comes from the research team of Sitkin et al. It is stricter than everyday usage. By that standard, a goal that is merely hard does not qualify.

A stretch goal has two properties at once: extreme difficulty and extreme novelty.

Novelty is the part most teams skip. If your team knows the path and simply has to work harder along it, you have an ambitious target instead. Prof. Sitkin frames the check as a question about your own certainty:

Does your organization have the skill, the experience, the resources to achieve a particular goal, or do you actually have absolutely no idea whether it’s possible to achieve it? If you have no idea whether it’s possible, that’s a stretch goal.

Sim Sitkin, Prof of Management, Duke University Fuqua School of Business

In practice, that test beats any percentage rule. Published advice often quotes a range, such as a target 50% to 70% above current performance. Those numbers rarely come with a source. Sitkin’s version is checkable in about ten seconds. If you can sketch a credible plan, it is not a stretch goal.

Vertical and horizontal stretch goals

Broadly, stretch goals are of two types, depending on whether they push harder on existing work or into unfamiliar work.

Vertical stretch goals raise the bar on something the team already does. A support team moving first-response time from 24 hours to under four hours is stretching vertically
Horizontal stretch goals push the team into territory it has never worked in. A paid-search team launching outbound sales is stretching horizontally, and usually rebuilding its marketing OKRs from scratch

In practice, the distinction changes what the goal costs you. Vertical goals mostly need capacity, because the team already knows the method. Horizontal goals need learning time, and learning time is the resource teams protect least. Set a horizontal stretch goal on a vertical timeline, and you will burn out a good team.

What Are Some Examples of Stretch Goals?

In practice, a real stretch goal names a team, a number, a deadline, and an unknown method. Generic examples like “increase revenue” fail because they specify no method problem. Here are four examples that pass, written the way you would put them in a planning doc.

For a support team

Vertical stretch goal: Cut median first-response time from 24 hours to under four hours by the end of Q3, with no headcount added.

The team has no idea how to do this without hiring, which is what makes it a stretch. Here, the plausible paths, such as triage automation, a macro library, and a self-serve help center, are untested.

For an engineering team

Horizontal stretch goal: Ship a public API within two quarters, on a product that has never had an external integration surface.

Nobody on the team has designed rate limiting, versioning, or developer docs. Even the software development KPIs you would normally track don’t exist yet. The uncertainty sits in the method, not the effort.

For a product team

Vertical stretch goal: Increase the 30-day user retention rate from 22% to 45% by the end of Q4, without changing the core product feature set.

The team can’t rely on building new capabilities, which forces them to fundamentally rethink onboarding, activation loops, and user messaging. The plausible levers, such as behavioral trigger emails, frictionless sign-up flows, and in-app walkthroughs, require rapid, unproven experimentation under tight time constraints.

For a marketing team

Horizontal stretch goal: Build and launch a fully functional localized self-serve campaign engine for three foreign markets within six months.

The team has only ever run centralized, agency-managed domestic campaigns. Nobody on the team has managed multi-region compliance, localized content pipelines, or automated cross-border ad spend allocation. The ambition lies in building entirely new organizational capacities rather than just scaling existing ad budgets. It’ll likely need a complete revamp of the team’s OKRs as well.

Stretch Goals vs. SMART Goals vs. OKRs

A stretch goal is a difficulty setting, while SMART goals and OKRs are formats. They are not competing systems, which is why the comparison confuses people.

You can write a stretch goal in SMART form. You can also carry one as an aspirational key result inside an OKR cycle. What changes is the expected completion rate, and what happens when you miss.

Dimension	Stretch goal	SMART goal	OKR
What it is	A difficulty level	A format for writing a goal	A framework for aligning goals
Path to achieve it	Unknown when set	Known and plannable	Known for committed, unknown for aspirational
Expected completion	Often missed by design	100%	100% committed, 60–70% aspirational
Best for	Innovation and method change	Predictable, ownable outcomes	Cross-team alignment and cadence
Main failure mode	Set without resources or slack	Attainability set too low	Treated as a review input
Can it hold a stretch goal?	n/a	Yes, with an ambitious target	Yes, as an aspirational key result

Google’s guidance on setting goals with OKRs is explicit about the scoring. It indicates that the sweet spot for OKRs is in the 60–70% range. An organization that scores lower is not achieving enough of what it could be. Scoring higher may mean the aspirational goals are not being set high enough.

In other words, a team that hits 100% every quarter has a calibration problem rather than a performance one.

Sales teams use a third vocabulary for the same idea. A commit is the number the rep will defend, a target is the quota, and a stretch is the upside case nobody plans headcount against. Functionally, those three match committed and aspirational OKRs exactly.

Why Do Most Stretch Goals Fail?

Most stretch goals fail because the teams setting them lack the two conditions that make them work: recent success and slack resources. This is the finding at the center of the stretch goal paradox that Sitkin et al wrote about.

The pattern is neat and awkward at the same time. Organizations positioned to benefit from stretch goals rarely bother, while the organizations least equipped reach for one as a rescue. Losses push decision makers toward risk-seeking, so a company coming off a bad year finds the go-for-broke option genuinely more attractive.

Prof. Chet Miller, a co-author of the Duke University study with Prof. Sitkin, explains why that leads to failure. As he stresses, stretch goals rarely end well, “unless an organization has had very strong recent success and has avoided advice to be very, very lean in operations.”

Note the second half of Miller’s condition. Being lean is usually treated as a virtue. For stretch goals, it is a disqualifier. Specifically, slack pays for the failed experiments, and a stretch goal is mostly failed experiments.

Most teams setting a stretch goal have neither. They have three competing priorities, a quarterly review looming, and a target that touches work nobody has run before.

Meanwhile, the baseline conditions for any goal are getting worse. Gallup’s Q2 2025 engagement data found that only 47% of US employees strongly agree they know what is expected of them at work. Adding an ambitious target to a team unclear about ordinary expectations doesn’t raise the ceiling. It blurs the floor.

Are stretch goals a blessing or a curse?

Research published in the Journal of Occupational and Organizational Psychology (Shi, 2025) reveals that stretch goals are more naturally perceived as hindrances than challenges, leading to employee withdrawal rather than growth.

The tipping point? Leader goal support. When managers actively provide resources, guidance, and psychological safety, employees see extreme goals as developmental challenges and proactively build skills. Without active leadership backing, stretch goals trigger stress and disengagement.

The takeaway: Never deploy a stretch goal in a vacuum. Extreme targets require high leadership support to motivate rather than demotivate.

When Is a Stretch Goal Worth the Risk?

Given all that, a stretch goal still earns its place in one situation: when you need a new method, not more output. An ambitious target gets hit by running the current plan harder. A stretch goal makes the current plan arithmetically impossible, which is the only reliable way to get a team to abandon one that still sort of works.

That is the whole case for them. Whether you can afford it comes down to the two conditions above.

The exception worth knowing about

Southwest Airlines is the counter-example everyone cites, and it genuinely does cut against the research. In spring 1972, the airline had $143 in its bank account, a $1.6 million net loss, and had just sold one of its four planes to cover wages. Ground operations VP Bill Franklin worked out that three planes could fly the schedule of four if crews turned each aircraft in ten minutes, against an industry norm closer to an hour. It worked, and it became the operating model.

By Sitkin’s criteria, Southwest should not have attempted that. No recent win, no slack, going for broke because there was nothing left to protect.

Two things made it survivable anyway. The goal targeted one repeatable operation that the airline already performed dozens of times a day, so every attempt returned data within hours instead of quarters. And nobody’s job depended on hitting ten minutes: the alternative was no company at all, which is the purest possible version of detaching a goal from performance review.

Southwest is the exception that shows you what the conditions actually need to look like, not proof that desperation works.

The Three-Question Test for Stretch Goals

Before setting a stretch goal, answer three questions.

Have we won recently?
Do we have slack?
Is missing it free of consequences?

Fail the first, and you have a threat. Fail the second, and you have a wish. Fail the third, and you have a quota in a stretch goal’s clothing.

The first two come from Sitkin. The third is the one almost nobody writes about, and it is where most stretch goals go wrong.

Maurice Schweitzer, Lisa Ordóñez, and Bambi Douma ran an experiment on goals and honesty for the Academy of Management Journal. They found that people with unmet goals were more likely to behave unethically than people simply asked to do their best. The effect was strongest when people fell just short of reaching their goals.

This isn’t an argument against stretch goals. It is an argument that our focus shouldn’t be on the size of the number, but the consequence attached to it.

Fortunately, the practical fix is boring and effective. Separate the stretch goal from anyone’s compensation, rating, or promotion case.

Sandbagging sits on Google’s own list of goal-setting pitfalls, next to failing to communicate that a goal is a stretch at all. Specifically, when people are graded on a target they cannot reliably hit, they stop proposing ambitious numbers. That is a rational response. It also costs you the exact behavior the stretch goal was meant to buy.

Run the test as three sentences you have to finish out loud:

Recent performance: “In the last two quarters this team delivered ___.” If the honest answer is a miss or a reorg, stop here
Slack: “The specific time, budget, or headcount we are protecting for this is ___.” If you cannot name it, you have a wish
Consequence: “If we miss this, what happens to the owner’s review is ___.” If the answer is worse than nothing, you have a quota

How to Set a Stretch Goal in Five Steps

Set a stretch goal by choosing one target, naming the unknown, funding the slack, declaring the goal type publicly, and reviewing it on a fixed cadence. The steps below are tool-agnostic. They work in a spreadsheet, a planning doc, or a work platform, and the sequence matters more than the software.

Step 1: Pick one goal, and write down what you are giving up

First, limit the team to one stretch goal per cycle, or two at the very most. Ambition divided across five targets is a scheduling conflict.

Remember that a stretch goal consumes the slack that ordinary work depends on. So the honest version of this step is a subtraction. Name the project that will now ship late, or the initiative you’ll put off for later. If nothing on the list moves, the slack is imaginary, and the goal will be absorbed as unpaid overtime.

Step 2: Name the unknown out loud

Next, write one sentence describing what the team does not know how to do. “We do not know how to cut response time by 80% without hiring” is a stretch goal. “We need to work harder on response times” is a performance conversation.

Importantly, that sentence does real work later, because it defines what a productive failure looks like. It also tells you which KPIs are worth watching while the experiment runs. A team that ends the quarter at 55% but has answered the unknown has delivered the valuable part.

Step 3: Fund the experiments before you announce the number

Decide what share of the team’s time is protected for experiments that will fail, then write it into the plan. 10-20% of a cycle is a reasonable starting point.

For instance, announcing a stretch goal and then filling the calendar with committed delivery work is the most common version of this failure. Teams read it accurately as a signal that the goal is decorative.

Step 4: Label the goal type in writing

State in the goal’s own description that it is a stretch goal, that 60–70% counts as success, and that it does not feed performance reviews.

Most OKR templates now include a field for goal type, and it is worth using.

Step 5: Review on a cadence, and grade before the deadline

Check progress at fixed intervals, monthly at a minimum. Do the final grading a week or two before the cycle closes.

Grade early, and the score stops being a verdict and becomes a planning input, which is really the only thing a stretch-goal grade is good for. Pairing the goal with one leading and one lagging measure keeps reviews short.

To learn more about the best goal-setting strategies, watch this video.

What to Do Instead When You Fail the Test

If your team fails the test, pursue a series of small wins rather than one large target. This is not a consolation prize. It is what Sitkin calls a strategy of small losses: a team needs evidence that it can win before it can absorb a goal it might miss.

So break the ambition into targets the team can plausibly hit in two to four weeks. Make each one visible when it lands, ideally on a KPI dashboard that the team can see.

For example, a support team that cannot credibly promise four-hour response times can still promise a triage rota this month, a macro library next month, and a measured 30% reduction the month after. The destination is the same. The difference is that each step returns information and a win rather than a running deficit.

Two other options are worth mentioning.

The first is the practical version of pairing a broad goal with measurable objectives beneath it. You can keep the ambitious number as a direction while committing only to the near-term step.

Conversely, you can spend the quarter buying the slack instead of spending it. Kill two low-value projects, then set the stretch goal next cycle when question two has a real answer. Waiting one quarter is cheap. Setting a stretch goal on an exhausted team is not.

Five Mistakes That Stop Teams From Hitting a Stretch Goal

In general, most stretch goals fail in one of five recognizable ways. Each one below has a symptom you can spot from the outside and a fix you can apply this week.

Attaching the goal to the review cycle. You can spot this when the numbers people propose get less ambitious every quarter, and the team starts negotiating the target instead of the method.

The fix: Hold to the no-consequences promise the first time someone misses. That is the only moment the team finds out whether it was real.

Setting one after a bad quarter. Leadership announces a bold target within weeks of a miss, a layoff, or a reorg, and frames it as a reset.

The fix: Run a small-wins cycle first, and set a stretch goal next cycle.

Confusing hard with unknown. The clearest sign of this is that the plan for the stretch goal is the current plan with longer hours.

The fix: Apply Sitkin’s certainty question. If you can write the steps, set an ambitious ordinary goal, and skip the theater.

Running four stretch goals at once. Does every function have an aspirational target, with the shared engineering or design capacity they all depend on booked three times over?

The fix: Allow one per team per cycle, then resolve the shared-capacity conflict before anyone announces anything.

Never declaring the outcome. You’ll see this when the goal quietly disappears from the doc at quarter end, and nobody says whether it was hit.

The fix: Close every stretch goal explicitly and record what the team learned about the unknown from step 2. An undeclared miss teaches the team that the goal was never real, which costs more than the miss itself.

How to Track Stretch Goals in ClickUp

Company OKRs and Goals Template by ClickUp — Set and track stretch goals in ClickUp

ClickUp keeps the goal and the work in the same place, which removes the gap between “we set an ambitious target” and “nobody looked at it for six weeks.” The judgment calls stay with you, as they should.

Five features that map to the steps above

Custom Fields carry the measurable part. Add a Number or Currency field to any task acting as your stretch goal and update it as results come in. A Dropdown field handles the status label from step 4 (stretch, committed, aspirational), so the ambition level shows up on the task instead of living in a manager’s memory
Subtasks and Checklists update progress from finished work. Break the goal into subtasks representing each milestone or deliverable in ClickUp Tasks. Progress rolls up automatically as subtasks close, so tracking is not a number someone has to remember to type on Friday. Note the success threshold in the description, so it travels with the work
Filtered Views keep the cycle honest. Build a Board or List View filtered by a “Goal Type” label field and grouped by quarter or sprint. One glance shows every stretch goal’s status across the team, which catches the four-stretch-goals-at-once mistake early
Real-time dashboards expose staleness. A Status widget or Custom Field Calculation card in ClickUp Dashboards shows how targets are moving (or not). Add a “Last Updated” filter, and anything untouched for five weeks surfaces immediately, because silence is the real status report for a stretch goal
ClickUp Brain catches what Dashboards wait for you to notice. Set up a Super Agent in ClickUp to review stretch goal tasks on a weekly cadence and flag anything with no subtask movement, missing owners, or stalled progress. It posts a summary in Chat or as a task comment, so the “untouched for five weeks” problem gets caught at week one, not week five. For lighter-touch tracking, Brain’s AI Standup pulls progress across your goal tasks into a single update without anyone filling in a form

Track work against goals automatically with AI Standup in ClickUp — *Configure AI StandUp to pull progress across your goal tasks on a set cadence*

To get started with minimal lift, try ClickUp’s OKR Framework Template. It’ll help you set SMART goals, track progress in real time, and identify blockers in time to find solutions.

Help your team focus on priority goals and measure progress systematically with ClickUp’s OKR Framework Template

Where ClickUp fits, and where it doesn’t

ClickUp is built around execution, so it fits best when the goal and the work feeding it live in the same place. Teams running formal quarterly scoring cycles across dozens of departments will want a dedicated OKR platform such as Microsoft Viva Goals or Weekdone for the scoring and alignment-tree layer, then connect it back to where the work happens.

For a single ambitious target reviewed once a quarter, a spreadsheet is faster to set up, though the number is only ever as current as the last person who remembered to type it.

This walk-through shows you how to manage OKRs in ClickUp.

Stretch goals need visibility to work

When QubicaAMF, the world’s largest bowling equipment provider, set out to scale project delivery across 90 countries, their progress was buried in siloed emails and spreadsheets. No one could see whether ambitious targets were on track. After centralizing all project tracking in ClickUp, with custom Dashboards giving each salesperson and coordinator real-time visibility into pipeline progression, revenue impact, and delivery milestones, the results spoke for themselves: a 35% increase in on-time delivery and 60% boost in cross-team collaboration.

As Process Manager Charles Frey says,

I don’t think I’ve ever seen any platform provide this level of visibility!

Charles Frey, Process Manager, QubicaAMF

The takeaway? Stretch goals only stretch if your team can actually see how far they’ve come.

Set Fewer Stretch Goals, and Fund the Ones You Set

The research on stretch goals is more settled than the advice around them suggests. They work for teams with recent wins and spare capacity, and backfire on teams without both.

Adding a bigger number to a stretched team doesn’t create capability. It creates a gap that someone will eventually be tempted to close on paper.

Therefore, run the three questions before the planning meeting rather than after it. If you pass, set one goal, protect the time, label it clearly, and leave it out of the review. If you fail, spend a quarter stacking small wins and ask again.

Get started with ClickUp for free if you want the goal and the work that feeds it in the same place.

Frequently Asked Questions About Stretch Goals

What percentage above current performance makes a goal a stretch goal?

There is no evidence-based percentage, and the commonly quoted “50% to 70% above target” rarely comes with a source. Difficulty is relative to method, not magnitude: a 20% lift can be a stretch goal if nobody knows the path, while a 60% lift is ordinary work if the plan already exists. Use certainty instead of arithmetic. Google’s OKR guidance covers the other number that matters, scoring 60% to 70% on an aspirational goal as success.

Where did stretch goals come from?

The practice is generally traced to Jack Welch at General Electric in the 1990s, alongside Motorola’s Six Sigma quality push, and both are documented in Sitkin, Miller, and See’s 2017 HBR article. Welch used stretch targets to break incremental planning habits at a company already performing well, which is the condition the research supports. Most later adoption dropped that context and kept the ambition.

Are stretch goals the same as BHAGs?

No. A BHAG, or Big Hairy Audacious Goal, is a 10-to-30-year organizational vision from Jim Collins and Jerry Porras in Building Your Company’s Vision. A stretch goal operates on a quarter or a year and attaches to a specific team and metric. BHAGs set direction for a company; stretch goals set difficulty for a cycle. A BHAG can generate stretch goals underneath it, but the two are not interchangeable.

Who should set a stretch goal, leadership or the team?

The team that owns the work should propose the number, and leadership should fund it. Targets handed down without the owner’s input get managed as quotas, no matter what the description says. In Measure What Matters, John Doerr argues roughly half of goals should originate bottom-up rather than cascade from executives, specifically so owners have a stake in the target they’re chasing. If the team cannot say no to the number, it is not a stretch goal.

Everything you need to stay organized and get work done.

Contact Sales

Stretch Goals: What They Are, When They Work, and How to Set Them