Pushback and feedback are often used loosely as synonyms, but they are not the same thing. Feedback is general input or comments. Pushback specifically means resistance or objections.
The test: general input, or active resistance?
The question is whether the stakeholder is giving broad input or resisting the plan. Flattening active resistance into "feedback" can hide the fact that a subset of stakeholders is actively opposed to a change, understating a risk decision-makers need to see clearly.
"In a survey summary, users made general feature suggestions and a smaller group actively opposed a pricing change: 'We received pushback on the pricing change, along with general feedback on the product' correctly separates the two."
That sentence does real work: it tells the reader that one part of the response was resistance, and the rest was ordinary suggestion.
"Writing 'we received a lot of feedback about the pricing change' would flatten the active opposition into generic input, hiding the real resistance from decision-makers."
The word "feedback" here understates what actually happened. A reader skimming that sentence has no way to know that part of that "feedback" was people actively opposing the change.
The common mistake: flattening resistance into feedback
The mistake is flattening active resistance into generic "feedback" in a survey or stakeholder summary -- that can hide the fact that a subset of stakeholders is actively opposed to a change. This tends to happen for a understandable reason: "feedback" sounds softer and less alarming than "pushback," so it's tempting to reach for it even when it isn't accurate.
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 →But a summary's job is to give decision-makers an accurate read on where the resistance actually is, and that job fails if real opposition gets folded into a generic bucket alongside minor suggestions. When a survey or stakeholder response includes genuine objections, name them as pushback specifically, and keep the rest as feedback.
Feedback is the wider category, not a competing word
It helps to think of feedback and pushback as concentric, not opposed: pushback is a specific kind of feedback, the kind that actively resists rather than merely comments. Every instance of pushback is technically feedback, but not every instance of feedback is pushback -- most feedback is suggestions, praise, requests for clarification, or general reactions that never rise to active resistance.
That relationship is why "feedback" so easily becomes the default umbrella term, especially in a summary written quickly: it's always technically accurate, even when it understates what happened. The discipline this creates is to actively look for the subset of responses that cross the line into resistance, and pull them out with the more specific word, rather than letting the broader, safer term absorb everything.
This matters most in exactly the situations where a summary gets skimmed rather than read closely -- a leadership deck, a quarterly review, an executive digest. In those contexts, a reader who sees "feedback" is unlikely to dig further; a reader who sees "pushback" is far more likely to ask a follow-up question, which is usually the point of flagging it in the first place.
Practice scenarios
Practice using push back in situations like:
- writing a survey summary that separates general suggestions from active opposition
- catching when 'feedback' has softened a report to hide real resistance
- reporting a stakeholder response accurately to a decision-maker
Useful practice phrases:
- "We received pushback on..., along with general feedback on..."
- "That's not just feedback -- it's pushback on..."
- "A subset of respondents actively opposed..."