I think the 75% threshold should still apply, as it works to protect the minority.
However,
I think there should be an official 5-10% "reconsider" threshold for questions that come close to passing.
Concealing the results before voting is important, as it encourages voters to consider their options, or abstain, instead of just voting in line with the majority. This is rendered useless though if you're able to change your vote.
I propose there be some general responses that players must select when voting to give the community and devs some context as to why they voted the way they did. There are many different reasons for selecting "Yes" or "No", and for the latter especially, sometimes it's hard to gauge why a question failed, which makes amending it difficult, as we saw with Raids armours. This way, we're able to see a breakdown of specific reasons and they can be addressed accordingly. As an example, when voting "No", players would then be asked:
- No, the rewards aren't good enough.
- No, the rewards are too good.
- No, I don't agree with the concept.
- No, I don't think it's old school.
- No, it increases xp rates too much.
- No, it doesn't award enough xp.
- No, it has an adverse effect on other aspects of the game.
In a perfect world, the first vote should be tentative. Once a poll has passed, it should be worked on and then put up on a beta/tournament-style world so that players can experience it for a short period and provide feedback before giving their final verdict (ideally, a separate voting booth in that world). While this sounds like a lot of work, and somewhat complicated, it would help to iron out the kinks before the content hit the main game. It alleviates the need for repolls down the track that distract from newer projects and add to the already large backlog of changes.
Measure twice, cut once.
28-Jan-2017 10:10:34
