Set the Floor and the Stretch for Quarterly Team Goals

We use two numbers and two different words for them. The floor is what we COMMIT to. The stretch is what we're chasing. If a number gets called a goal without one of those two labels attached, it goes back for a rewrite.

The rule that made the floor honest was this: the floor has to be a number the team would hit even if the quarter goes sideways. Somebody quits, a machine goes down, our biggest account pauses. If your floor assumes everything works, it isn't a floor, it's a forecast.

We size the floor off the last four quarters of actual results, not off what we wish. Then the stretch usually sits about 30% above it. Nobody gets punished for missing stretch. Missing the floor is a real conversation.

The phrasing we use out loud is "what breaks if we only hit the floor." If the answer is nothing breaks, the floor is too low and we raise it. If the answer is we can't make payroll, then the floor is actually the stretch and we've been lying to ourselves about the plan.

That one question has killed more bad quarterly goals for us than any framework I've read.

The floor is a number with a name attached to it. One quarter I had a vague priority to improve onboarding, so I rewrote it as: reduce onboarding time from 14 days to 7 days, owned by Sam, reviewed every Friday at 10 a.m. That is the minimum, not the dream. The stretch can sit above it in a separate line, but if a goal has no owner and no number, I do not count it as a goal yet. It got done in six weeks.

Twelve years setting quarterly goals for teams that were measured on hitting them. Under-committing is not a motivation problem. It is a rational response to being paid on the floor. If the number people are judged against is the number they must clear, they will name one they can clear, and no amount of ambitious framing changes that arithmetic.

Stop asking what the team can achieve. Ask what would count as a wasted quarter — that number they will tell you honestly.

The phrasing I use separates two sentences. The floor is written as a negative: "we have not wasted the quarter if X." The stretch is written as a bet: "if Y happens, we were right about Z." One is an obligation. The other is a hypothesis, and being wrong about a hypothesis is not failure.

It breaks the moment the stretch enters a performance review. Then both become floors, and you are back where you started.

The phrasing that's worked is calling the floor the number we would be uncomfortable explaining if we missed it, not the number we expect to hit. That framing forces the floor down to something genuinely defensible rather than a padded target dressed up as conservative, because nobody wants to set a floor they would have to justify failing.

The stretch gets described differently on purpose, as a specific outcome rather than a bigger number. Instead of a percentage increase, the stretch is named as the point where growth forces a real operational change, like needing to expand onboarding capacity. That framing makes the stretch feel like a real possibility worth planning for, not just the floor multiplied by an arbitrary factor.

The rule that keeps the two from blurring together is that the floor gets reported in every check-in regardless of where we land, but the stretch only gets mentioned again if we are actually within reach of it. Bringing up the stretch when it is clearly out of reach turns ambition into a running reminder of falling short, which erodes morale faster than just missing a single number would.

The rule is: “Number plus without.” “Floor” is “number plus without.” “At least X without Y” is “floor.” “Floor without a guardrail” is “pressure people into something else to break it.”

A floor and a “without”—a lesson we learned the hard way on the admissions side. We got the number one quarter. I was excited about it until I saw what they quietly dropped to make it happen: alumni calls, follow-ups to keep people connected to us after they leave us. No one stopped making alumni calls. It was just that they went last on the list every day for 11 weeks. A floor for the census commitment, no one alumni call that was missed, the same discipline that has every department head read their floor out loud in front of the other department heads, including clinical, medical, operations, and admissions. Two things. One sentence. One owner.

The floor is a sentence I can hold you to. Sandbagging survives a one-on-one with me, but sandbagging does not survive your peers hearing what you just promised.

This is a guess, and it’s just a bare number with no conditions. For the under-committing problem, I don’t argue numbers privately. I can hold you to a sentence.

Floor is "whatever survives my worst week in the last quarter." My average week doesn't matter. I take my worst week, multiply it across the quarter, and that number is my commitment. I've almost never under-committed because I was too pessimistic. It's mostly because teams quietly build their plan on their best week and call it normal.

A floor is one number and a stretch is a range of numbers. If a department head hands me a range for the floor, they haven't actually decided yet, and we keep talking until one number comes out of their mouth. Stretches can breathe, but floors can't.

I learned that the hard way. Our admissions team beat their floor early. I raised the floor on them at week six because it looked easy. Once they hit the new number, I still consider it one of the worst calls I have made. Then, when the next quarter rolled around, every floor they brought me was padded. You move a floor mid-quarter once and you've taught your people that honesty gets punished. Now the floor is locked the day the quarter opens, no matter what happens.

Being in long-term recovery myself taught me the whole distinction. There is a difference between making a promise you can keep and a promise you can't keep.

I'm Max Shak, Founder and CEO of NerDAI.com. When I set quarterly goals, I've learned that the biggest mistake is treating the target as a single number. A number without context can encourage a team to either play it too safe or chase an unrealistic outcome.

I like to separate the goal into a floor and a stretch. The floor is the minimum result we should be able to achieve if we execute the plan we agreed to. It should require real effort, but it shouldn't depend on everything going perfectly. The stretch is what becomes possible if execution is strong and we capitalize on opportunities along the way.

The phrasing I use is simple: "This is the commitment; everything above it is upside."

That distinction matters because I want people to know exactly what they are accountable for without creating a ceiling around their ambition. If the team thinks the stretch number is the minimum, they may become discouraged when circumstances change. If they think the floor is the goal, they may stop pushing once they reach it.

I've also found that a good minimum success line needs to be tied to controllable actions, not just outcomes. For example, instead of saying, "We need $500,000 in new revenue," I'd look at the pipeline, customer conversations, proposals, conversion assumptions, and other leading indicators that make the revenue target credible.

The quarterly review then becomes more useful. We can ask, "Did we meet the commitment? If not, why? If we did, what allowed us to outperform it?"

For me, the floor creates accountability while the stretch creates ambition. The key is making sure the team understands that one is a promise and the other is an opportunity.

I learned this the hard way when we missed our Q3 revenue target at my fulfillment company because I'd set a goal of "grow 30% this quarter" without defining what the actual floor was. My team celebrated hitting 18% growth while I was quietly panicking about cash flow. That's when I started using what I call the "two-number rule" for every quarterly goal.

Here's how it works: Every goal gets a floor number and a ceiling number, and I explicitly tell the team which one determines their bonus. The floor is the minimum we need to hit for the business to stay healthy or for the project to be worth continuing. The ceiling is the ambitious outcome that would genuinely move the needle. When I sold my company for eight figures, we'd been using this system for two years and it completely changed how teams operated.

Real example from ShipDaddy: Q1 goal was onboard new 3PLs to the platform. Floor was 150 new providers (the minimum to maintain our growth trajectory and justify the sales team's salaries). Ceiling was 300 (which would let us expand into two new verticals). I told the team bonuses kicked in at 150, with accelerators above 200. We hit 220. Nobody celebrated at 150 and called it done.

The phrasing I use in kickoff meetings is this: "The floor is what keeps us in the game. The ceiling is what wins the game. Your bonus starts at the floor, but your equity value grows at the ceiling." That last part matters because it separates short-term thinking from long-term ambition.

The mistake most founders make is setting only stretch goals and then retroactively celebrating when teams hit 60% of them. That's just lying to yourself about performance. Define your floor based on what the business actually needs to survive and grow, not on what feels motivating. Then set a ceiling that would genuinely surprise you. The gap between those two numbers is where real performance lives.

A clear minimum success line is the Trust Threshold—the baseline of delivery where failure represents a breach in operational discipline rather than just a missed target. In large-scale engineering, this floor is defined by outcomes where failure would damage reputation, client trust, or financial stability. To separate this floor from ambition, use a framework of Commitments versus Aspirations. The Commitment is the non-negotiable floor, consisting of deliverables backed by rigorous resource allocation and risk assessment. The Aspiration represents the stretch—high-value, higher-risk objectives pursued only once core commitments are secured.

The operational rule is that the floor must represent 80% of the team's capacity, ensuring you are not under-committing while leaving 20% for aggressive innovation. I tell my leads that the Commitment is what we owe the organization today, while the Aspiration is what we owe our growth tomorrow. This phrasing removes the ambiguity that leads to burnout. If a team hits 100% of their Commitment, they have succeeded; anything achieved in the Aspiration category is a performance multiplier rather than a baseline expectation. This prevents sandbagging because stretch goals are celebrated as strategic wins rather than expected outcomes. By treating the floor as a non-negotiable operational promise and the stretch as a strategic investment, you maintain a culture where predictability and ambition coexist. This distinction is critical for distributed teams where clear, binary success metrics are the only way to maintain alignment across geographies and functional units.

The framework I use to separate the floor from the stretch starts with a single question for every quarterly goal before it is finalized: what version of this outcome would disappoint us but not surprise us?

That question does something most goal-setting frameworks miss. It forces the team to honestly confront the low end of the range rather than anchoring exclusively on the aspirational number. When people can articulate what a disappointing but defensible result looks like, they implicitly reveal the floor. And when the floor is explicit rather than assumed, the gap between floor and stretch becomes a real and navigable distance rather than an undefined space where ambiguity lives.

To make this concrete in team settings, I use the must and the want. Every quarterly goal gets stated twice. The must is the minimum outcome that represents genuine progress and meets the commitment we made to the business. The want is what we are actually aiming for, the number that would make us genuinely proud and that requires real stretch to hit. Both numbers are visible to the whole team from day one.

The rule that keeps this honest is that the must has to be something the team would be willing to defend publicly if asked. If the floor is so low that nobody would feel comfortable saying it out loud, it is not a real floor. It is an escape hatch. And if the stretch is so high that nobody actually believes it is possible, it is not ambition. It is theater.

The practical result of naming both is that the team stops unconsciously negotiating with itself about what it's really committing to. The floor is not the target. It is the line that tells everyone when the quarter has succeeded at minimum. Everything above it is where the ambition lives.

So the floor and the stretch live in one sentence here, joined by the words “if the quarter goes well.” 12 pieces published, then 20 if the quarter goes well. The floor is the number I would put in front of the whole company without explaining anything around it. 60 of us work across 3 time zones, which means a goal gets read at 4 in the morning by somebody with nobody to ask. A team that hits the stretch 2 quarters running has a floor that is too low, so we raise the floor and say that out loud.

You can tell within a week whether a team believes the floor, because the arguments all happen over the floor and never over the stretch. The way we write the stretch has not moved in 6 quarters. Only the floors have.

When I set a quarterly team goal, I define the minimum success line as the result we can commit to delivering with our current people, capacity, and resources—not the number we hope everything goes perfectly enough to reach. I use a simple rule: "The floor is the commitment; the stretch is the opportunity." In our plating business, I've seen ambitious production targets become counterproductive when the team quietly treats the stretch number as the real expectation. For example, when we've planned around a demanding delivery period, separating the must-hit output from the additional capacity we wanted to unlock kept everyone focused without lowering the bar. The floor should still require disciplined execution, while the stretch should require something extra—better efficiency, fewer delays, or an improvement in the process. That distinction gives the team a clear definition of success while still giving ambitious people something meaningful to chase.

I would define the minimum success line as the outcome the team can commit to with current capacity while maintaining safety, workmanship and customer promises. If reaching the target requires favourable weather, perfect attendance or rushed quality checks, it is not a credible floor.

The phrasing I recommend is: “The floor protects our commitments; the stretch improves how we deliver them.” For an outdoor construction team, the floor might cover completed, quality-checked work, while the stretch could reward fewer return visits, stronger preparation or smoother handovers. This separates dependable performance from ambition and prevents the higher target from quietly becoming permission to cut corners.

I use a rule called funded confidence. The floor is the result we can defend after accounting for current capacity, known constraints, and work already in motion. It should feel demanding because missing it requires a real explanation. It should not depend on a perfect quarter, a surprise hire, or three assumptions landing at once.

The stretch is the outcome unlocked by choices the team can still make. We phrase it as, "We will deliver X, and we can reach Y if we complete A, B, and C by these dates." That wording matters because it keeps Y from becoming a hidden expectation. Teams under-commit when leaders treat forecasts as promises. They overreach when aspirations lack conditions. Separating the two turns ambition into a visible operating plan rather than a motivational poster.

Floor: every active patient has a dated next visit inside the usual 6 to 8 week window. Stretch: we also clear the open-lab list before Friday.

The floor is the calendar. The stretch is the inbox of results. If the floor fails, the quarter failed, no matter how ambitious the stretch looked on a whiteboard. Ambition is allowed only after the dated visits exist. I write both lines in the same note so nobody confuses a busy week with a successful one.

When I set a quarterly team goal, I define the minimum success line by documenting the acceptance criteria and the team's decision authority up front. My rule of thumb is to delegate tasks, not uncertainty: everyone must know what outcome satisfies the minimum and which decisions require escalation. I use a single phrasing on the goal: "Minimum: accepted outcome with no further approvals required; Stretch: additional value-added work pursued if capacity allows." That phrasing keeps the team focused on delivering the essential outcome while making clear what extra ambition looks like.

I'm Charles Liu, CEO and Marketing Director of Cubic Promote. For us, the minimum success line is very clear because our finance team sets a sales quota for each team member. That quota is the floor everyone is expected to reach for the quarter.

We then raise the target gradually, usually a step higher each quarter, so the team is always working towards better performance rather than simply repeating the same result. The distinction we use is simple: the quota is the minimum, while anything above it is the stretch. Also, we have a team quota to reach, which encourages everyone to do more. That way, everyone knows exactly what success looks like, but there is still room for stronger performers to push further.

I prefer gradual increases rather than setting an unrealistic jump all at once. It keeps expectations clear, gives the team something achievable to work towards and still encourages continuous improvement.

Charles Liu
CEO and Marketing Director
Cubic Promote

A quarterly goal needs a clear floor, not only an ambitious ceiling. I write the minimum that still counts as done, in one sentence, before the stretch language goes on the slide.

That floor stops under-committing dressed up as realism, and it stops a heroic target that nobody believed. The team can still chase the stretch. The review starts with whether the floor landed.

I run people internally at Cintra and the HR outsourcing work. Vague goals create quiet overtime. A named minimum keeps the conversation honest when capacity is tight.

My recommendation is to write two promises: "We commit to this outcome with the resources we control; we will pursue this additional outcome if the named assumptions hold." Give both a number, an owner and a date, and apply the same quality guardrails to each.

The floor should represent worthwhile improvement over the baseline. It should not be a list of activities that can all be completed while the customer sees no benefit. For a hypothetical appointment-access team starting at 17% no-shows, a floor might be 14% and a stretch 11%, with no increase in unresolved patient callbacks. Those are illustrative targets, not QuickIntell commitments.

Our published anonymized orthopedic case reports no-shows moving from 17% to 9% after a combined scheduling, authorization and documentation deployment. That company-reported result illustrates why the outcome matters more than the number of reminders sent; it is not a benchmark every team should promise.

My rule: the floor earns confidence, the stretch tests a hypothesis, and neither permits a quality shortcut. Review the assumptions weekly instead of quietly moving the success line.

Rahul Agrawal, Founder & CEO, QuickIntell

Define the floor as the smallest result that makes the quarter's investment worthwhile, with the quality conditions included. The stretch is additional value the team will pursue after that commitment is protected. A low number chosen because it is easy to hit is not a useful floor.

The phrasing I recommend is: "We commit to X by this date, while meeting Y quality standard and staying within Z constraint. We will pursue the stretch if these assumptions hold." That forces the conversation to include capacity, dependencies and what the business actually needs.

For a hypothetical marketing quarter, the floor might be an agreed number of qualified opportunities at a defined maximum acquisition cost, with a named person responsible for validating qualification. The stretch could be additional qualified opportunities from a new channel. Publishing more content would be a supporting activity, not an alternative way to claim that the commercial goal was met. The actual numbers should come from the baseline, available resources and the business requirement.

To prevent under-committing, ask two questions before approving the floor: would achieving it justify the resources, and what evidence says the team can deliver it? To protect ambition, make the stretch explicit and state which experiment or additional capacity could make it possible.

Review the assumptions during the quarter. If a dependency fails, record the change and its effect instead of silently lowering the target. At the end, report the commitment and the stretch separately. Reaching the floor should mean the agreed result was delivered; missing the stretch should still produce a clear lesson about the experiment.

Heath Squier, Founder, EVKII

I write two numbers on every quarterly goal, and I make the team say both out loud in the kickoff. The floor is the number I'd be embarrassed to miss, meaning if we hit it, I still don't get to celebrate. The stretch is the number that would require something to go unusually right. Everything in between is normal performance.

The phrasing I use is simple: “We commit to X. We're chasing Y.”

Commitment is a promise other people can plan around, so nobody downstream gets burned. Chasing is what we're spending our energy on, and missing it costs nothing except the upside.

To keep the floor honest, I set it at the level we'd hit if we did nothing new this quarter. A floor built on last quarter's habits is a number the team already knows how to reach. If someone proposes a floor that requires new work to achieve, I treat it as a stretch wearing a disguise.

Then I only score the commit number in reviews. The stretch gets talked about weekly, gets the credit when it lands, and never shows up as a failure.

The floor is what the shelf and the inbox will still do if the quarter goes sideways. The stretch is optional work that cannot steal time from restock or replies.

For this shop, the floor sounds like this: keep 28 products in stock across The Doux, SheaMoisture, Oyin Handmade and Kitsch, and answer tickets weekdays 9 to 5 within one working day. Stretch might be a new journal piece. In The UK Wash-Day Report 2026, https://zenvy-beauty.com/blogs/news/uk-wash-day-report-2026, wash days sat 4.8 days apart. The rule I use is one sentence. If missing the stretch would still leave the next wash-day bottle on the shelf, it was stretch. If missing it would leave a hole a customer can see, it was never stretch.

I use a proximity test for quarterly floors. Could the team explain the minimum commitment to the person most affected by a missed deadline or confusing decision? If the language becomes evasive, the floor is probably a metric rather than a responsibility. The right floor names the practical benefit people should reliably receive.

The stretch should describe an additional benefit, not a substitute for the basic obligation. My rule is, "Floor is the promise we can defend face to face, stretch is the improvement earned through better execution." This framing builds clarity into reviews and discourages success theater.

A useful quarterly floor is not a target chosen in isolation. It is the last point in a chain of dependencies. Demand, staffing, supplier reliability, website accuracy, fulfillment capacity, and post-purchase support all determine whether a number is genuinely deliverable. Most under-commitment happens when teams ignore the weakest link and select a goal based on the strongest department's potential.

I frame it this way: “The floor survives normal friction, while the stretch assumes several important things go right.” Normal friction includes routine delays, imperfect conversion, and ordinary rework. That language makes the distinction concrete. It also keeps leaders from labeling a favorable scenario as a commitment simply because the math looks attractive in a planning sheet.

When I set a quarterly goal, I try to make the minimum something the team can recognize in their actual day-to-day work. I don't think the floor should be an ambitious growth number if hitting it means people are rushing work or creating more review problems later.

For me, the minimum would usually be that the work we have committed to clients is delivered on time, review points are dealt with properly, and there is clear ownership when something is still outstanding. If we can do that consistently, then we have a stable base to improve from.

The stretch part does not always have to mean doing more work. At CYLL, one thing I value is seeing junior team members gradually understand more of the whole engagement and become less dependent on step-by-step direction. So a good quarterly stretch might be that someone who previously handled only one part of an engagement can take ownership of a larger section and bring the judgment points to me for review.

I think that is also a healthier way to judge progress. If the team is meeting client commitments and, at the same time, people are becoming more capable of handling the work themselves, then I would consider that a good quarter. If we hit a bigger number but everyone needs more chasing and more late review, I probably would not.