“Push back” is how disagreement is submitted for approval. The word does something “no” cannot: it frames objection as a contribution to the process rather than a challenge to it. Pushing back is collaborative. It has a spirit of engagement. The idea being pushed back on is still alive; it is merely under review.
In a meeting, push back arrives as a question. “Have we fully thought through the implications?” is a well-formed push back. So is “I want to make sure we’re aligned on the risks.” Neither is a rejection. Both are. The distinction matters to the room because the room contains people who approved the idea, and push back is designed to give everyone somewhere to stand while the idea quietly fails to move forward.
The more senior the push back, the less it needs to explain itself. A junior professional who pushes back provides a counterargument, supporting data, and an alternative. A senior one says, “I’m not sure I’m comfortable with this,” and that is sufficient. Discomfort at sufficient seniority functions as a veto. It is a more efficient mechanism than the veto because it leaves no record of having been used.
Push back that succeeds is called due diligence. Push back that fails is called resistance to change. The difference is determined afterward.
