Push back is the workplace move of resisting, questioning, or renegotiating something so it doesn't move forward unexamined -- without necessarily rejecting it outright or ending the conversation. It's how you flag a weak assumption, an unrealistic deadline, or a pricing concern while staying open to discussion.
The core pattern: push back on
The everyday form is push back on + idea / request / assumption / timeline / price. The preposition matters: "on" keeps the resistance conversational and targeted at the point, not the person.
"I want to push back on the assumption that Q3 demand will match Q2 -- we don't have the data yet."
"Before we commit, I'd push back on the two-week timeline. Engineering needs closer to four."
When the resistance is broader or more public -- pressure, criticism, an allegation, a proposed rule -- "against" is the more natural preposition:
"The legal team plans to push back against the proposed regulation before it reaches a vote."
The noun form, pushback, describes the resistance itself and is normally uncountable:
"We should expect some pushback from Finance on the revised budget."
Want to learn "Push Back" in depth?
Lyra Practice teaches advanced non-native professionals the nuance of high-value expressions like this one, then has you practice using them in realistic work scenarios.
Start learning for free →A second, unrelated pattern: scheduling
Push back also means to move something later -- a meeting, a launch, a deadline. This sense takes no preposition; the object goes directly between "push" and "back":
"We've had to push the launch back to early Q3."
This is the single most confusable part of the expression, because the scheduling sense and the resistance sense look almost identical on the page. Keep the direction straight: push back always means later, never earlier.
Common mistakes
Confusing the two senses. "I pushed back the plan" is ambiguous or simply wrong -- if you mean resistance, you need "push back on the plan"; if you mean rescheduling, you need a date or timeframe attached ("push the plan back to Friday").
Dropping or misusing the preposition. Skipping "on" in the resistance sense ("I pushed back the assumption") reads as a scheduling statement by mistake. Adding "on" to the scheduling sense ("push back on the meeting to Friday") is equally wrong -- the scheduling pattern never takes a preposition before its object.
A third habit worth watching: treating pushback as automatically hostile. It isn't. "We welcome pushback on this proposal before it goes to the board" uses the same noun to invite scrutiny, not describe conflict -- the word is neutral until the tone around it says otherwise.
Practice scenarios
Practice using push back in situations like:
- challenging a weak assumption in a recommendation before it goes to leadership
- resisting an unrealistic deadline or scope change with a concrete constraint
- reporting expected stakeholder resistance neutrally in a status update
- moving a launch or review later and communicating the new date clearly
Useful practice phrases:
- "I want to push back on [assumption/timeline], because [constraint]."
- "We should expect some pushback from [team] on [issue]."
- "We've had to push [meeting/launch] back to [date]."
Get the preposition and the direction right, and push back does exactly what it should -- it opens a conversation instead of closing one.
The word carries no built-in hostility. What makes it sound tactful or abrasive is everything around it: the evidence you bring, and whether you're aiming at the plan or the person.
Lyra Practice helps advanced non-native English professionals learn the nuance of high-value workplace expressions and practice using them in realistic scenarios, so their English sounds natural, precise, and senior at work. Try Lyra Practice.