Bagel Press

in a recent task at work, we were trying to decide upon a song to use in the company reel, and the result left me wondering if we had really built a consensus at all.

essentially, each person involved submitted a set of songs to the group and then each member of the group voted on their top picks. our first mistake was not specifying how many picks to choose and whether to indicate order of preference. What ended up happening was that some people submitted a top three, some a top six (as that was the number of people involved) and while some indicated the order of preference, some did not. the ultimate choice was based upon the song which received the most number 1 votes.

the issue i had with this result was that the song which received the most #1 votes did not appear at all on two voters lists. it left me wondering whether there would have been more overall satisfaction if a song had been given more weight for appearing on everyone’s lists, albeit in a lower position. i also wondered how the ability for people to apply a negative vote (ie. a vote for a song they absolutely did not want) would have affected the results.

what i’m thinking of is some kind of consensus building tool which is not so simplistic as a simple ‘vote for your favorite’, which i see as prone to create more polarized situations in which some people wind up extremely happy while others end up completely dissatisfied (see: our process of electing government officials). there’s surely got to be an easy to understand way to make the whole process more sophisticated.

I’ve been pondering to do lists lately, and one of the shortcomings i’ve experienced with to do lists is that, when working in teams, my to dos are sometimes partially or entirely contingent upon someone else in the team completing something on their to do list.

in the end, when someone at the beginning of the chain (myself included) falls behind on one of their to dos, it makes it appear on the surface as though people on the end of the chain went over their budgeted time, when in fact they may have actually completed their task faster than originally budgeted but finished later than planned because of the prior setbacks of others on the team.

i wonder if there is a more robust to do list tool than the ones i am using to link up lists in this way and to visualize the time spent more effectively.