We've all been there. User requirements piling up at every turn, some useful, some well...less useful.
"I want to enter in this one thing, then have it pull in a file from here, change it to this, and email these three people, but only when it's this thing but not that, and not EVERY time, and I want to know who is on the email, and it should pull up in Outlook, ALWAYS. Can you build it?"
Me (in my mind): "Yes, for four zillion hours of development time, and then it will only help you and not the other 98% of the user base. Not to mention Outlook integration which is always a joy".
Me (reality): "How often do you perform this task? It may be easier to just perform this specific process manually since it appears to change regularly over time. That way you will also have full control of what information is sent to whom with no surprises, and you can use Outlook without issue." <phew>
The story is a short one. Don't accommodate every user's request on the planet, there are impacts. Users don't design systems, you design systems (or work with people who do?). If you cater to every request from a user you will get killed with upkeep and make a system "clunky" (I shudder when I hear that word from a user). The fastest way to lose usage / adoption and kill your system is to get bogged down with one or two enhancements that help .01% of the population.
Keep your eyes on the prize and try to build things that help your greater vision and user base.
I'm not saying don't listen to people, but just take a step back and always think about the experience for everyone else before you put user xyz's enhancement in.
How do you deal with enhancements from users that you know will eat up time and only help a few people? (especially from upper management!)
Please comment below!