<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=1375001637486124&amp;ev=PageView&amp;noscript=1">

Fictional test content for Avanzia Marketplace QA. Back to the test blog

When to say no to a feature request

Fictional test content for Avanzia Marketplace QA.

Saying no is part of building something focused. It does not have to be unkind.

Understand the problem first

Ask what the person is trying to achieve. The request is often a solution to a different problem.

Check it against your goal

If it does not help the people you serve most, write it down and say so.

Say what you will do instead

Offer a workaround, a date to revisit, or a pointer to another tool.

Keep a visible list

People accept a no more easily when they can see that the request was heard.