The Condorcet criteria itself is easy. If a candidate would beat every other candidate in a one-on-one matchup, that candidate should be the winner. There, that's it.
That's really how it should be described. And then as a next step, we can then describe "tiebreakers". Instead, wikipedia (and others) describe Condorcet only in terms of their tiebreakers, making Condorcet methods themselves appear flawed.
You see, loops are possible. In a vote, it's possible that A would always beat B, B would always beat C, and C would always beat A. And the various Condorcet tiebreakers (like Schulz) are ways to resolve those situations.
But the point is, if that happens, the vote really is accurately uncovering an indecisiveness that actually exists in the voting population. So it makes sense that a "tiebreaker" would be non-ideal in some sense. And they all are in some way. The problem is not with the tiebreaking methods. The problem is with the voting population.
I've always thought a good voting system would be the following:
First, rank the votes. If a Condorcet winner exists, the election is over. If not, restrict the candidate pool to the Schwartz set, and start a new round of campaigning so the voting population can research more and better educate themselves.
. Yes, we can argue that the Condorcet criteria is "perfect" if a Condorcet Winner exists, with one caveat: it implies the value that all votes have equal value. If you have that value, it's a logical implication that the Condorcet Winner (if it exists) should be the winner. But other values are possible, such as a utilitarian mindset of wanting to meet greatest social utility, such as some voters being far more passionate or educated than others. Following those implications bring up other tricky problems, though.
The other thing is, that I sometimes want to allow people not to rank an option at all (e.g. if they participated in a HackDay team, they shouldn't rank their own team), once you allow options to be unranked, you open up the possibility of multiple roots to the graph (e.g. one person votes that A > C and leaves B unranked, and another person votes that B > C and leaves A unranked), so you need to do something reasonable in that case too.
In my first implementation of ranked pairs, I would lock in results based on their victory margin, but if a number of results had the same victory margin, they would be locked in based on their order in the system - clearly wrong.
My favourite theory now is just to find all strongly connected components and collapse them into a group which is equally tied (not just the Schwartz set either - cycles can occur further down the graph and relative rankings are still interesting to competitors). The joint winners are all options in all groups that have no losses. http://kybernetikos.github.io/graff/demo/ was me playing around with the ranked pairs way of removing cycles compared to just grouping them.
Now I have to go back to the code!
Anyway, yes - you can come up with a full ranking of candidates in a Condorcet method by finding the condorcet winner (or schwartz set), removing, and running again, and keep going until you've fully ranked all candidates.
The essential difference between Schultze and what I like these days is that Schultze will try to resolve cycles, whereas I think it's better just to accept them and call it a tie. If you can't have ties, then I really like the earlier suggestion of rerunning the voting on just the ones in the Schwartz set.
I had a friend who worked advocating for simple runoff voting initiatives, but gave up because it was too much work having to explain it to be people.
On top of that, you then have to consider the potentially lower popularity of your favourite choice against that of the current lead contenders. Do you reduce your vote for the better of two evils so that your sincere preference has a better chance? Ugh.
I'm not trying to suggest tactical voting doesn't exist in other systems, but to suggest that it doesn't in Range voting is either misinformed or disingenuous.
With approval voting I have to make that decision, setting some kind of threshold of approval. With range voting it might be easier to just vote honestly.
At worst, everybody votes tactically and you get approval voting, which is still a good system. But sometimes the tactical decision is difficult, in which case range voting gives you the option of just voting honestly.
It's a good thing I didn't suggest it, then.
Valuing one voter over the others like that is a dangerous road to travel down.
Because whereas ordinal rankings at least arguably mean the same thing when different voters give them, cardinal scores don't have a consistent meaning, making all cardinal voting systems subject to GIGO problems in addition to any other issues.
> Range voting is the name of that system and, unlike Condorcet methods, it is not subject to Arrow's impossibility theorem.
No system that is not a form of ranked ballot system is "subject to Arrow's impossibility theorem", nevertheless, range voting is, beyond the GIGO problem faced by all cardinal methods, demonstrably subject to the same classes of tactical voting as approval voting, which means that while it is not in the class of of systems to which Arrow's theorem applies, it has flaws (from the perspective of the Arrow criteria) of the type that Arrow's theorem states that all the systems to which it applies must have. So the fact that Arrow's theorem doesn't apply to it doesn't actually make it any better.
AFTER EDIT: A comment posted while I was typing the first version of this comment mentions "range voting" as a response to the Arrow paradox. A commentary by an economist and a problem set by a mathematician may suggest to thoughtful readers here some issues to ponder while discussing whether or not range voting provides better trade-offs than our current voting system, and whether it indeed escapes the theorem proved by Arrow.
I strongly recommend this book for anyone interested in multi-participant decision systems, or anyone looking for a fun mathematical excursion. Sadly, the paperback (which I bought in graduate school for $25) is no longer in print and the price has jumped quite a bit.
"Independence Of Irrelevant Alternatives" is thought to be particularly problematic. There definitely are thought experiments that demonstrate that IIA is not as desirable a criteria (to rule out a voting system) as you would want. If a voting ballot runs afoul of IIA, it can point more to a confused voting population than a flawed voting method.
For instance, the Condorcet Criterion runs afoul of IIA. The Condorcet Criterion states that if a candidate would beat every other candidate one-on-one, that candidate would be the winner. Apparently it is possible to introduce additional candidates (that don't change the relative rankings between pre-existing candidates) such that a Smith Set is instead produced. However, it is not possible to introduce additional candidates such that a different Condorcet Winner is produced.
But let's think about what that says. A Smith Set is not a problem in itself. It means an indecisive or conflicted voting population. It is interesting that additional candidates can expose a conflicted voting population, a confusion that actually already was there; just covered up by the lack of candidates. In other words, if IIA changes a result from a Condorcet Winner to a Smith Set, it is an indication that the population was not given enough choice in the original ballot.
In that sense, IIA is actually useful, and not a flaw. It does not point out a flaw with the Condorcet voting mechanism; it points out a flaw with the limited choice of candidates (and time to research/understand those candidates) for that vote.
This is part of the problem with voting theory, is that they make unwarranted theoretical assumptions, such that a vote will always offer sufficient choice to a voting population. At any rate, I believe IIA is a flawed criterion, and therefore the Impossibility Theorem, while true, is less useful than it is celebrated to be.
But, as you say, Arrow's Theorem is simply too broad with it's definition of "fair". It's entirely reasonable for the voters to have a list of candidates they hate and a list of 3 candidates they would prefer, and for there to be a rock-paper-scissors situation among those top three candidates. It's entirely possible to have a voting system that only chooses from among the rock-paper-scissors options, and indeed every Condorcet system will make such a choice. Those options are the Smith set.
The tragedy is that Arrow's Theorem is often used to justify systems (like plurality or range voting) that often won't choose from among those top three, and might even choose the Condorcet loser! I'm not sure what a good definition of "fair" is, but I'd settle for not picking the candidate that would lose to literally every other candidate in a one-on-one election.
Yes, every social choice mechanism has issues, but some have an awful lot more issues than others.
That's actually an invalid use of it; while the concept of "better" is inherently subjective ("democratic" has multiple definitions, but many of them are objective) Arrow's theorem has nothing to do with that one way or the other.
Arrow's theorem says that a certain set of binary criteria that applies to voting systems that map from a set of ranked preferences to a single preference ranking cannot be met simultaneously, but it does not say anything one way or the other about the ability to differentiate objectively among voting systems on continuous-valued axes, including various operationalisations of "democratic".
Some voting systems genuinely are more democratic or better than others in an objective sense. For example, a voting system where one person determined by their status in society has their vote count and everyone elses is discarded is objectively less democractic than a voting system where a ballot is selected at random from all voters and is taken to determine the result.
Neither of these systems is as democratic as a system where everyone votes for their favourite and the one with the most votes wins, and that in turn is not as democratic as a condorcet-loser system, where it's not possible for a candidate that the majority rank last to win.
Just because all of the options have problems, it doesn't mean that there aren't options that are completely dominated by others.
Obviously this is true, but this is rarely one of the voting systems being considered in any discussion about voting systems.
If you think that Arrows theorem really does this, then you should stand by that assertion and defend all voting systems that Arrows theorem applies to as not objectively better than any other voting system that Arrows theorem applies to.
And yes, Arrows theorem applies to Dictatorship/Random Ballot/Plurality/Condorcet-loser methods which are the ones I used in my example.
The general point stands that there is no voting method that dominates every other voting method, but that there can be voting methods that dominate individual other voting methods.
Different voting systems can give you different angles on picking the option with the most direct support versus avoiding picking options that stir up a lot of dislike in the voting body.
The one actual concrete attempt to test this I've seen shows it, in the tested scenario, more vulnerable to strategic voting than plurality (or any other tested method.)
 http://rangevoting.org/ElectionByMajorityJudgmentExptEvidenc... [The method is referred to as "point summing" rather than "range voting".]
I think that paper is misguided and incorrect as an attack on range voting. Here's the page where that link occurs:
Here's the anchor: http://www.rangevoting.org/MeasTheory.html#numbersallowed
Finally, if you sum the scores, you are NOT doing range voting as is generally suggested. The idea of range voting is to average the scores. That is a totally different thing, especially when you (as you should) allow for no-opinion votes.
I can only conclude that the paper in question is not addressing actual range-voting as proposed. That said, I did not read it completely (nor am I especially interested in doing so, although someone could summarize the issues perhaps if any exist I have not addressed here)
Could you kindly let participants here know why your opinion has become that support for range voting? What issues did you consider along the way that you think are worthwhile for us to consider as we ponder which voting methodology to support in the various places where we live?
Just turned out I was wrong this time :)
If you just look at first picks, Newbie HBase wins 3 to 1. If for some reason Newbie HBase was in a 2/2 split with Mapreduce and KIR (flip James's top 2 votes), you then take into account 2nd rankings, which in this case means Newbie HBase wins again.
I don't believe you ever want to take into account someone's griefer vote, too much potential to game the system with no benefit to the group as a whole.
You're proposing plurality voting (plus a weird tie-breaker), which is the worst method on basically every criterion except for "simplicity" and "familiarity to Americans". It leads to really obvious vote-splitting, and people will vote strategically, because they know perfectly well what happens to honest votes in plurality voting. They will also simply propose fewer things.
If the computer is counting votes for you, simplicity shouldn't be the highest priority.
There's a reason people have put years and years of research into voting methods. The best method is unlikely to be the one you think of off the top of your head and post in an HN comment.
What I think is really weird is why would a system put much weight, if any at all, on someone's 4+ choice? We might be coming up with a result that received the most points, but are we actually coming up with a result that the most people will be happy with, or is it the least boring thing that people will put up with?
The thing to note about our particular situation is that we're really only a little interested in the #1 result. The app is primarily about helping groups prioritize things, for instance "What features do we need to build next".
Rating systems are a no go, because the whole point is to force people to choose and hence consider the tradeoffs (hence "ForceRank" :)
In this case, some of the voting system criteria such as "susceptibility to burying" play out a bit different than in a regular election. eg If everyone thing "Project C" is a great idea but Frank _hates_ Project C, we want to do what we can to highlight that fact, not just continue on our merry way with the majority vote.
The most common favorite is not the definition of democracy - it's just the method of choosing that is most common. It's sort of self-justifying; "it's what we've always done, so we should keep doing it". But, things change over time, and we have the ability to better understand large groups of preferences than we used to (when counting first choices was the only possible way to vote), which means a better ability to provide social utility and help a group of voters help themselves in the most useful way.
Anyway, ordinal method doesn't actually apply any "weight" to a 4+ choice. The concept of "weight" doesn't actually apply to a Condorcet method. All you're really communicating is that you prefer candidate #4 to candidate #5, and to candidate #6, etc. There's no extra proportional "power" or weight given to higher-ranked candidates, though, because you've already communicated that you prefer candidate #1 to all of them.
It really is the same thing as if someone gave you (n(n-1))/2 ballots of one candidate against one other, with you picking your favorite. It's just faster to communicate in ranked form. It also doesn't run afoul of "one-person, one-vote", because no voter has extra power compared to another voter.
Finally, yes - say that 49% prefer A, have B as a close second, and hate C. 49% prefer C, have B as a close second, and hate A. 2% prefer B and hate both A and C. B's definitely just the "least objectionable", but also should definitely win as the consensus choice, even though B only got 2% first-place votes.
So the idea that the algorithm ended up picking something ranked #2 by everybody over something ranked #1 by some people and #10 by some people is not actually crazy.
If you choose a system with ten gradations of voting, that's what you get - choices that are #2 for everyone are preferred over choices that are #10 for some people. If you don't like that result, don't choose that voting system. That's what a ten-point voting system is.
By the way, the images are wrong - the text implies that Matt ranked Newbie Hbase very low, but the image shows the opposite.