<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

A respectful way to decline feature requests: understand the problem, check your goals and offer a useful alternative.

Saying no is part of building a product people trust.

Understand the problem first

Ask what the person is trying to do before discussing the feature.

Check it against your goals

If it does not serve the people you built the product for, say so plainly.

Offer an alternative

Point to an existing option, a workaround or a date when you will look again.