Saying no is the deliverable

Every client arrives with a list. Sometimes it is a document, sometimes a sentence that starts with "we also need." The list is never the problem. Treating it as the brief is.

A list is a record of everything anyone has ever wanted. It has no author and no priority. It grew because saying yes is free at the moment you say it, and expensive for years afterwards.

What a feature actually costs

The price is not the time to design and build it. That is the deposit. The real cost is the maintenance, the support conversations, the extra branch in every future decision, and the attention it takes from the thing that mattered.

Products rarely fail because something is missing. They fail because so much is present that nobody can find what they came for. I have never been asked to rescue a product that was too simple.

Every feature you add is a promise to maintain it forever.

No is not a refusal

Said flatly, no sounds like withholding work, and clients are paying for work. So it has to arrive with the reason and the alternative, or it is just an obstacle with a designer attached.

What I actually say is closer to: this is what you asked for, this is what I think you are trying to achieve, and here is why those two point in different directions. Then I show what opens up if we cut it.

Almost nobody argues with that. What people resist is being told no. What they want is to be told why.

Earn it first

Said badly, this becomes cover for a designer who simply does not want to do the work. The difference is evidence. A no that comes from research, from the data, from the people who use the thing, is a professional judgment. A no that comes from taste is taste wearing a better jacket.

So earn it. Understand the business and the problem well enough that your refusal is the most informed thing in the room. Then say it once, plainly, and be ready to be wrong.