Push back = protect data quality, scope, or timeline. Stay respectful.
Soft push-back script
1. Acknowledge the goal 2. Explain the risk or cost 3. Offer alternatives 4. Ask for priority call if needed
STAR outline
Situation: Stakeholder asked to "just hardcode" a fix in the dashboard SQL for a bad source field.
Action: I explained hardcoded fixes drift and hide source bugs. I offered: (A) fix upstream mapping today, (B) temporary case statement with a ticket and expiry date. We chose B with a 1-week expiry and an upstream ticket.
Result: Dashboard recovered; source fix landed; temporary logic removed.
Fresher tip
In group projects: push back on skipping tests before a demo. Frame it as reducing demo risk.
Interview tip: Push back on risk, not on the person.