3 ms·
That very much depends. Are you saying no because the requested feature doesn't match your vision, or because it doesn't match what the user needs? If it's the
by rwallace 13y ago
That very much depends. Are you saying no because the requested feature doesn't match your vision, or because it doesn't match what the user needs?
If it's the latter, great! You're on track to a first-rate product.
But most designers make the mistake of going with the former. That's why most products are second-rate.
- byamit 13y agoIf a feature request doesn't align with the product's vision, it's perfectly fine saying no. If the vision itself is flawed, then the product is not likely to succeed.
- rwallace 13y agoEvery vision is flawed, because we are fallible. The question is what we do about that. Do we keep the product nailed to the flawed vision until the last user has gone elsewhere, or do we use feedback from reality, from users telling us what they need, to improve the vision?