How to suggest improvements to the software you love

Do you have a favorite utility or application, and just wish it would do one little thing, that would improve your experience with the program? I get that feeling all the time. It can be a helpless feeling for us non-developers, since we're sort of at the mercy of the software we can find to do what we need done. But there is hope. Below I'm going to provide a few tips that can help you to get changes affected in your favorite software, if you're willing to be patient, careful and very respectful.

1. It might seem obvious, but use software that is being actively developed. I can't count how many times I've found myself using a program and wishing that something would be fixed or improved with it, only to find that it's an abandoned product that hasn't been updated for two years. If that's the case, it really may be worth the trouble to ditch the old software and find something comparable that is being actively developed. Now, I'm not suggesting you go and throw away perfectly good utilities if they do everything you need them to. If that's the case, rock on - who cares if it's getting updated. But if you wish something were different, the tension you feel with the product is probably already high enough to make a search for something better worthwhile. Luckily you know a site that brings you tons of useful downloads every day.

2. Okay, now that you've got actively developed software, find out where the developer or developers hang out. Online, I mean - don't go stalking people. Most developers are writing software because they earnestly want to help people get something done. While the onslaught of feature requests can be quite daunting for developers, most of them weather the storm because they know that they will be able to either find a trend amongst all of the requests, or find a real nugget of good information that they can turn into their next killer feature. So don't just find a forum for the product, see if there is a feature request forum or topic, or maybe one for the beta version of the software. Oh, and if you're looking to get a change done in the software, help out the developers by beta testing their software and providing useful feedback.

3. Once you've found the right place to make your suggestion, it might just contribute to the trend that will hopefully convince the developer to make the change you're looking for, if it's a common request. If it's not a common request, here's how to request a feature that the developer will see as the nugget of good information that they can turn into their next killer feature. Oops, I feel a sub-list coming on:

   1. Honestly consider whether your suggestion will only benefit you, or if it will truly make the product better. If your idea passes that test (and be brutally honest with yourself), your next task is to...

   2. Sell your idea to the developer. You know it's a great idea, but the developer probably has never considered their product the way that you have. It's a matter of perspective, so you need to take great pains to effectively communicate your idea. This means use spell check, write complete sentences, use proper grammar and follow the common-sense rules of written communication. Pretend you're writing to your boss, or better yet, writing to someone to convince them to give you a job. In other words, be professional. At the same time, try to get them excited about the possibilities your idea presents.

   3. If your pitch is successful, the developer will likely reply to ask you further questions about your idea. And even if they don't - another user might, so make sure you take part in the conversation. Give the developer all of the information they request, and if it's another user engaging you, be respectful. Chances are, even if the developer hasn't replied, they're probably watching the conversation. Sometimes it's the conversation that helps enlighten the developer to your wonderful idea.

   4. If you're not already beta testing the product, get with the program. It's the best way to know whether your idea has been used, and will give you the opportunity to give feedback about the way your idea was implemented.

4. Finally, if your idea isn't accepted, don't get discouraged. Some developers have very specific product development paths in mind, and aren't looking for outside input, or are only looking for input that fits their ideas of where the product should go. That's okay - just know when to quit. If they've made it clear they aren't going to pursue your idea, be respectful and gracious - thank them for their time, and wish them luck (and mean it).
   

Tags: commercial, development ideas, DevelopmentIdeas, freeware, howtos, ideas, opensource, shareware, software changes, software suggestions, SoftwareChanges, SoftwareSuggestions, suggestions