Sandbagging

One-liner: Deliberately holding back real output or ability, so a later, unremarkable effort looks like a leap forward and no one raises the bar on you.

Also known as / related terms: Underperforming on purpose, lowballing, holding back capacity, pipeline sandbagging, effort management, strategic underperformance.

What it is: Sandbagging is the deliberate suppression of one’s true output, speed, or ability so that expectations stay low, comparisons stay favorable, or a later result looks more impressive than it really is. It has a well documented professional lineage outside of office slang: in sales, “sandbagging the pipeline” refers to reps intentionally under-forecasting or delaying deal closures to guarantee they beat quota later or smooth commission timing, a practice sales operations and forecasting literature treats as a known distortion of pipeline data. In project management and construction, sandbagging describes padding schedule or cost estimates, or concealing true capacity, so that hitting the padded number later reads as strong performance. Applied to a coworker or team, the same mechanism becomes a workplace pattern: doing the job at a deliberately slow rate, downplaying results, or hiding true capacity to manage what others expect from you next cycle, avoid a permanently raised bar, or protect a future point of comparison.

What it looks like (workplace): A team member who is fully capable of finishing a project in two weeks quietly stretches it to four, consistently, so that the two-week pace never becomes the new normal others are measured against; or someone underreports how much of a shared workload they actually handled so a modest effort next quarter reads as a dramatic improvement.

Why they do it: To control future expectations and comparisons, to avoid being permanently anchored to a high bar, and to bank a strategic reserve that can be revealed later for maximum credit or leverage.

How to protect yourself:

• Track your own team’s actual output over time rather than relying on any one person’s self-reported pace or numbers.
• If you suspect it in performance reviews or PIPs, ask for concrete, time-stamped work product, not just self-reported status updates.
• Separate “this person is slow” from “this person is controlling the narrative”: the tell is a sudden, unexplained jump in output right after a review, layoff round, or renegotiation.
• If you manage sales or delivery teams, cross-check self-reported forecasts or estimates against historical actuals rather than taking any single quarter’s number at face value.

Cross-links: Weaponized Incompetence, Knowledge Hiding / Information Hoarding, Perception Management / Rewriting the Story.

Sources:

• Corporate Finance Institute: Sandbagging, defines sandbagging as intentionally lowering estimates or projections to produce better than expected results, in management, sales, and startup contexts.
• Sandler: Sales Sandbagging Explained, documents sandbagging as a recognized, named distortion of sales pipeline forecasting.
• Perficient: Sandbagging and Lowballing in Project Estimating, documents the practice of intentionally padding project estimates in project management.

Label note: Mixed. Sandbagging has genuine, decades-old grounding in sales forecasting and project estimating literature as a named, studied distortion. Its application to everyday office politics, an employee deliberately underperforming to manage a coworker’s or manager’s expectations, is a more informal extension of that same mechanism, documented mainly in workplace forums and management blogs rather than peer-reviewed research.