You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Seems almost silly to jump into (forgive me here, I do not mean this as some request/expectation, just sharing the spark your amazing work caused in my creative brain). The complexity might be bad (either in coding or in UX), but here's the idea:
Often events have some potential attendees who are more essential than others. As is, organizers can hover around the results and see who specifically is available when and take that into consideration. So, that's fine enough.
What if there were an option to prefer some attendees over others? For example, mark some attendees as required, thus automatically blocking off any of those attendees' 0's.
The main and more consistent idea would be marking 0-5 for each attendee as a sort of how-essential-is-it-for-this-person-to-come. That would result in reweighting the scores for the final heat map (multiply the scores by the organizers' or viewers' attendee-score). And for the runoff, a cut-off could be used like counting only the preferences of the set of attendees weighted above a 2 or above a 3 (ignoring the votes of lower-scored attendees when it comes to the runoff calculation). Of course, the reweighted-and-cutoff results could be shown alongside the straightforward one-person-one-vote results.
The text was updated successfully, but these errors were encountered:
That's an interesting idea. It's another case of going from the binary yes/no availability to a 0-5 star gradient! Right now you can do a binary include/exclude for attendees by clicking on their names, but you could also have a preference gradient for weighting attendees too.
I love this idea, but it does require some sort of implementation of #4 and #5.
whenisgood has a concept of temporary exclusion vs permanent exclusion as well. There is a value to keeping the person's availability for future viewing, rather than deleting it, while not considering it whenever the poll is pulled up.
Proposed feature
Seems almost silly to jump into (forgive me here, I do not mean this as some request/expectation, just sharing the spark your amazing work caused in my creative brain). The complexity might be bad (either in coding or in UX), but here's the idea:
Often events have some potential attendees who are more essential than others. As is, organizers can hover around the results and see who specifically is available when and take that into consideration. So, that's fine enough.
What if there were an option to prefer some attendees over others? For example, mark some attendees as required, thus automatically blocking off any of those attendees' 0's.
The main and more consistent idea would be marking 0-5 for each attendee as a sort of how-essential-is-it-for-this-person-to-come. That would result in reweighting the scores for the final heat map (multiply the scores by the organizers' or viewers' attendee-score). And for the runoff, a cut-off could be used like counting only the preferences of the set of attendees weighted above a 2 or above a 3 (ignoring the votes of lower-scored attendees when it comes to the runoff calculation). Of course, the reweighted-and-cutoff results could be shown alongside the straightforward one-person-one-vote results.
The text was updated successfully, but these errors were encountered: