Malamasala
Profile Options
#751
0
Lurkios on 03/08/2012, 12:59 PM - view
From past experience, it sometimes is just that the company does not know how to handle the situation. They think that if they go out and give information, it will upset people. But it is the opposite. As long as you give detailed information, people tend to be happy, even with negative answers.
Example of good community feedback:
"We've been reading the threads regarding the Elin changes and we are sorry that we didn't first check with you before doing the changes. We like the idea of a download of the KTERA pack for those who wish to use the older armors, but do not have time to work on this until after launch. If you give us a couple of months after launch to get this through with BHS, it would probably work out fine."
Example of bad community feedback:
"We did a business decision to change the armors since we think it will appeal to more people."
In the good example here, their fear is that by saying they'll TRY something, people will claim they promised it, and they'll get crap for not delivering. But this is not true. Some will be that way, but the majority are old and wise and accept that plans can fail. It just needs to be a form of communication that shows things are being worked on.
Like 1 month after launch, they follow the issue up with "We contacted BHS regarding the KTera armor pack, and are currently negotiating the terms."
Ok, so now we want some promise of those changes - because from what I can tell, En Masse is completely ignoring the issue. If they planned to make changes all they have to do is say as much.
From past experience, it sometimes is just that the company does not know how to handle the situation. They think that if they go out and give information, it will upset people. But it is the opposite. As long as you give detailed information, people tend to be happy, even with negative answers.
Example of good community feedback:
"We've been reading the threads regarding the Elin changes and we are sorry that we didn't first check with you before doing the changes. We like the idea of a download of the KTERA pack for those who wish to use the older armors, but do not have time to work on this until after launch. If you give us a couple of months after launch to get this through with BHS, it would probably work out fine."
Example of bad community feedback:
"We did a business decision to change the armors since we think it will appeal to more people."
In the good example here, their fear is that by saying they'll TRY something, people will claim they promised it, and they'll get crap for not delivering. But this is not true. Some will be that way, but the majority are old and wise and accept that plans can fail. It just needs to be a form of communication that shows things are being worked on.
Like 1 month after launch, they follow the issue up with "We contacted BHS regarding the KTera armor pack, and are currently negotiating the terms."