A PM wanted us to add analytics dashboards directly into our core sync engine. I pushed back, said it violated separation of concerns. Honestly, we had a 6-week deadline and no capacity. They moved it to a separate service. It shipped fine.
Names a real principle, then immediately reveals capacity was the actual driver.
A product manager pushed me to embed a notification feed directly into our checkout flow. I refused — we had 4 distinct user goals in that flow, and adding a feed broke the mental model entirely. He escalated. My manager backed me, and we shipped without it.
Genuine UX reasoning, but outcome-dependence slightly obscures the underlying principle.
A product manager asked me to embed a reporting dashboard directly into our checkout flow. I pushed back because it served 3 internal users, not customers. I wrote up the scope argument, proposed a separate internal tool, and they agreed.
Audience-based argument — wrong users, wrong surface — is crisp, portable, and proactively resolved.