Every UX practitioner knows the moment. A stakeholder asks for the impossible, the insane, or the immediate. You listen politely and start composing the most diplomatic version of “no” you can manage.
Try a different word
I want to suggest a better word: how. Not because every request is a good idea. Some are spectacularly bad. But because “how” forces us to explain what we know instead of simply announcing a conclusion.
Sometimes the act of working through the question reveals a creative solution or a perfectly acceptable compromise. Other times, the path turns out to be so expensive, risky, or disruptive that the sensible decision becomes obvious to everyone.
“No” gives the business a UX conclusion. “How” gives the business UX expertise.
Make the trade-offs visible
How much research would give us confidence? What would we have to stop doing to make room? What happens if our assumptions are wrong? Are we prepared to invest the time, budget, and credibility?
These are not gotcha questions. They are legitimate business questions, and the stakeholder shares accountability for the answers.
A better partnership
“No” gives the business a UX conclusion. “How” gives the business UX expertise. That distinction matters.
Even when the business chooses a direction I disagree with, the conversation has made the risks and reasoning legible. If things go badly, we can learn from what we anticipated. If they go well, we can learn from what we missed. Either way, we are a better partner than a color printer with veto power.