>Ignore feature requests — don't build what users ask for; understand the underlying problem instead That sounds like good advice on the surface but it should

>Ignore feature requests — don't build what users ask for; understand the underlying problem instead That sounds like good advice on the surface but it should be "understand what the user is asking for" then see if it is a valid thing, after which you can decide how to accomplish it. Users usually come to you with the last bit. They ask you to do it in a particular way.