Glynor,
I wish I could write as succinctly as you can. That "pet issue" list is great stuff. I have copied and pasted your four steps on the effective way to word a "pet" issue request on my openoffice.org word processor, so that I can keep it in my documentation, and possibly pass it on to others. (Glynor, I hope you are not expecting royalties, if I pass those steps on to some others
).
Funny thing is that a day or two ago, I posted, for about the third or fourth time, my hope for MC to have a 64 bit version. That is a pet thing of mine. However,
I understand that the resources are limited, and that the MC staff, would like to magically fix everything. But, they will be pragmatic and work on bugs first, then will do enhancements that will be of most importance to customer request (as well as how long it can take). Maybe others might add on to my request for the enhancement as well, not in a critical way, but saying things like, "Yeah I would really like a 64 bit version as well, especially with Windows 7 and the promise that MS is going to pay much more attention ot the 64 bit users. So maybe, my pet enhancement might go higher in the enhancement cue, as it would serve to our teammates, the MC developers, that their customers are telling us that coming out with a 64 bit version is important to them.
Whenever I ask for a enhancement/change, I always try to post it, in a way that hopefully would be taken as positive by the team, which include the family of customers. Just like you were describing Glynor.
A last point. Glynor, I have been in IT for sometime over two decades. I hate to admit it, but when I was in college, I had to punch cards that would represent my Fortran, Assembler or whatever computer language I was using. But, most valuable over the years were some of the "soft skills" classes that I was able to send myself to as well as participate in, from a firm I was working for.
One in particular, showed how, by being overly emotional, showing frustration at a customer service person, like a bank teller for example, then seeing the person storm out of the bank and NOT get what he needed accomplished.
Then showing a video, with a model, like Glynor mentioned. I have learned, and just used Friday for a very difficult situation I was in, how the words, "Can you please help me", can be magical. Especially that magic of "please help me". For the most part, people on the customer service lines are used to hearing others frustration and a lot of criticism, and if they help someone, usually people don't call to thank them, or acknowledge them (when doing computer/system admin support), when things just work flawlessly.
So when someone says, "Can you help me, or I really would appreciate your help, etc, if it is not the poor off shored contractor, I have had people do the most remarkable things, even from the IRS. So I think Glynor that there is a universal significance to what you have written.
Media Center is so unique, in this day of Corporate buyouts and off shoring. The increased distance between the customer and the product that keeps getting worse and worse.
There are many times that I might spend a lot of time just looking for a contact email or phone number. So many make you go through the knowledge base first, for about 10 passes (I am exaggerating on the 101 times of course), then if you ever can get to the alleged support email or form to enter, what I tend to get back is something from either a computer or a off shore contractor, who doesn't have the training, experience, and motivation to answer you question. Sometimes, on the phone, I wait for the off shore contractor to get on the web site and is quoting me, what I also am looking at from the web site at the same time. Sometimes the calls turn into training sessions, where I am the trainer.
On email, I can tell when I am getting some electronic message that is direct from some "help desk" software and it is obvious that my query wasn't read.
Jon
I've been on this forum for a long time, and I guess I'd say this...
Just because no one takes immediate action on a particular bug report or request, doesn't necessarily mean that it has been ignored. I've seen, personally, instances where things I've asked for (where it seemed "ignored" for all intents and purposes), were eventually implemented months and/or years later. A perfect example is the Tremote capability, which I've clamored for for years!
The JRiver team seems impressive because of all the great work they put out almost every day. However, in reality it is a quite small (but mighty) team. They do the best they can to address user concerns and requests, but some things need to be "triaged". Could they sometimes do a better job of communicating and/or tracking these requests? Sure. But we all have things we could improve upon, and honestly, I think that the level of responsiveness that we get out of them is still heads-and-shoulders above what you get from 99.9% of other software development firms. (I've submitted no fewer than 50 bug reports regarding Windows 7 to Microsoft during the Beta and RC program. I've had zero responses.)
The other suggestion I'd have is this...
If you want to stand the best chance of getting some "pet" issue implemented/fixed, the most important factor is you. How likely you are to get the response you desire is a DIRECT consequence of how effectively you:
1. communicate your need
2. explain how it will impact other users as well as yourself (they frown on spending resources on "specialty" needs from niche audiences, for obvious reasons)
3. illustrate a range of possible actions that they could take to address the issue or concern
4. remain vigilant about the issue (posting it once in the build thread is often not enough, if it is a major/systematic concern). The squeaky wheel really does get the oil, so long as it squeaks in a nice tone.
Author
Topic: Re-read your post and tell me ... (Read 2358 times)