Take for example the 0-day promised patch that never came. This was a terrible public relations error by CA. Basically you promise your users something then don't deliver. You will never build any confidence in your company this way and you will alienate users. Saying nothing is actually worse as it implies apathy and a lack of support for the product. The answer is a balance with timely action.
Take the load/save bug of RTW. This is something we all are aware of --how negative the user base can become when a company denies or ignores perceived concerns from the users. It really doesn't matter whether the concern is real or imaginary, if there is a sizable contingent of users that see a problem, then it is a problem that has to be addressed. Its funny, but some moderators on the .COM site still don't understand this.
Now, MTW2 does have a lot of promise but the longer the community waits for a patch the more negative things will become. Negativity spreads and the longer it goes unchecked the worse it is. It doesn't lessen or go away with a patch, rather, it subtly damages on a long term basis the confidence users have in the company. Politicians have known this for years.
My suggestion is to release patches as things are fixed. The community will see some tangible progress and the negativity will start to reverse itself.
Bookmarks