I agree. These kind of surveys with multiple options make it very difficult to judge what the priorities of people are and what amount actually supports what. I'm guessing that's why SE only counted one vote from everyone in the hair style contest. If we had individual answers from everyone on an Excel sheet it would be possible to analyze it properly.
I think you improved it there. Something I just realized as I was typing this, is that if you want to include the previous percentages you could mention that they are minimum percentages. For example, (referring to my previous post) the support for public parsers could be 50.42% (minimum) or all the way up to 100% (maximum). No parser support is somewhere between 17.09% - 33.89%. You can find the maximum percentages by comparing to the highest individual vote count (the group parser one) as the total voter count. It's the worst case scenario where as many people as mathematically possible voted triple and double.
You're right. If we had 100 votes on pear ice cream and 100 votes on toffee ice cream, there would be no way of knowing if it's a case of 200 people highly opinionated about ice cream or 100 people who simply like any ice cream. In either case they are equally as popular, but if the shop knew which scenario was true they should probably consider whether they want to serve pear-toffee cones for everyone or perhaps let the customer pick one flavor.
Then there are also opinions about whether the parser (personal or group) should be optional, and further whether it should be optional to be parsed by others, optional to be parsed in casual content, or optional for the party leader to parse in premade groups. Sigh...
I suggest a survey of yes/no answers that really go into detail to avoid any misinterpretation. The survey should save individual answer sheets, so that people voting yes or no in specific parts could be separated and analysed as a subgroup.
1. Do you want a tool to measure your own damage per second? yes/no
2. Do you want a tool to measure other player's damage per second? yes/no
3. Are you opposed to other players seeing your own damage per second? yes/no
4. Are you opposed to players seeing the damage per second of other players (not you)? yes/no
5. Are you opposed to players seeing their own damage per second? yes/no
6. Are you opposed to players being able to measure dps in casual content in some way? yes/no
7. Are you opposed to players being able to measure dps in hardcore content in some way? yes/no
8. Do you think a player should be given an option to hide their individual dps from others if a party-wide parser was implemented? yes/no
9. Do you think a party leader in a premade group should be able to parse all party members after notifying the party and selecting the parser option in duty settings? yes/no
10. Do you think it is important to give players a chance to avoid parser harassment by allowing players to opt out of parser use, be it by hiding their numbers from others or by choosing content or premades where a parser is not used? yes/no
11. Do you think it's important to establish guidelines about what is considered reportable parser harassment and what isn't? yes/no