search

pgeu / pgeu-system

Mirror of the PostgreSQL Europe Conference and Membership management system.
MIT License
20 stars 28 forks source link

Talk voting tool is not clear on what is a good vote #127

Closed andreasscherbaum closed 1 year ago

andreasscherbaum commented 1 year ago

The voting tool uses 0-9 as voting. It might be intuitive to say that 9 is the highest vote, but occasionally a CfP team member reaches out because that's not written and documented anywhere in the UI itself.

It is written in the help, but people don't read that.

danielgustafsson commented 1 year ago

I don't have strong feelings on whether we should mandate a system, but isn't it more flexible like it is now, where each PC can decide for themselves what 0 and 1-9 mean and agree on a definition internally before voting starts?

If we want to change and put the information where users can't avoid seeing it, we should change the dropdown to be "0 - Lowest, 1, 2, 3, 4, 5, 6, 7, 8, 9 - Highest" I think.

andreasscherbaum commented 1 year ago

Proposal: above the voting box, under the "Update" and "Reset", add a line:

Use 1-9 for voting, where 9 is the best. Score 0 does not mean "really bad", it just means "no vote". Absence from voting for colleagues and close relatives.

Text up for discussion.

andreasscherbaum commented 1 year ago

@danielgustafsson The help states how this is used, and "0" has a special meaning anyway. 0 should not be used for voting, which is confusing by itself.

mhagander commented 1 year ago

ISTM that there are two, separate, issues.

One is that 0 has a "magic" meaning. That's clearly terrible, and should be fixed. Without having looked at the code, that looks like it should be a trivial fix, since <option> elements have two different fields for value and display. But.. Saying that may come back to bite me :)

The second issue is "what is good". This seems to be similar to the issue we had years ago (IIRC also in Germany) with the feedback forms which had a scale 1-5 and some people thought 1 was good, other people thought 5 was good. That one was solved the way @danielgustafsson suggests above, by indicating the highest and lowest value in the dropdown.

I have a feeling that kind of indication is going to be more clear, since it's more "in your face" than a string of instructions at the top of the page, which will become invisible as soon as you scroll off the page. But the downside is it uses up more horizontal screen estate which in this particular form is kind of limited.

Not sure which of those I'd prefer (other than fixing the 0 -> "no vote" thing).

I think at some point @xocolatl was looking at a redesign of this page. I'm not sure if you got far enough on that one, @xocolatl, to hvae any input from that one that should affect this discussion?

andreasscherbaum commented 1 year ago

The width of the column is defined by the width of the username, and most usernames are wider than "9 - best". I think using that is ok, and if that doesn't work for anyone, it can be adjusted later on. Doesn't have to be perfect, gradually improving works for me as well.

mhagander commented 1 year ago

Hmm. Fair point -- my test accounts are all mha1, mha2 etc, which makes it different, but yeah probably not so relevant out in the real world.

I think from a usability perspective, that one will be better than adding a text about it.

The other question is of course as mentioned by Daniel if we want to not specify it to let each team decide on their own. But given it's causing confusion this way, restricting it to "9 is always the good one" is probably a valid loss of flexibility.

andreasscherbaum commented 1 year ago

Did anyone ever not use "9 is best"? And if yes: why? Because it was unclear, or because they specifically wanted it that way?

If there is no good reason to offer the choice, I vote for not make it more confusing. Otherwise the help also needs to be updated, which today states that 9 is best. It's just that the UI does not reflect that today.

danielgustafsson commented 1 year ago

My proposal is to do the following:

The horizontal real estate issue doesn't bother me (and I'm most often on a 13" screen), it's still small and limited by the username (as mentioned above) which might be longer making this a no-op. If we care and want to reclaim some space we can rename the "Average" column to "Avg" since values in that column is limited in width to "X.XX".

mhagander commented 1 year ago

The middle point, "0 -> No vote" has already been implemented :)