Blogpoll Philosophy Comment Count

Brian

Note to poll voters: if you did not receive an email from me, please let me know. The first poll comes out Monday and you must be apprised of URLs and such.

SB Nation's excellent Missouri blog Rock M Nation will be joining the BlogPoll this fall, and they've thrown out a question to their readers: how the hell should we put together our ballots? This shows seriousness, which is an admirable quality in a voter, but a lack of deference to the poll's President For Life, which is neither admirable nor uncommon.

I've learned over time that I can't tell people what philosophy they should follow when compiling a top 25 poll. Or, rather, I've learned I can tell people what philosophy to follow and they'll just do what they want to anyway. There's only so much control you can pretend to have when the most respected college football blogger around thumbs his nose at some of the poll's published guidelines and the funniest one slaps up haphazard ballots 30 minutes after the deadline, usually after IMing me something like "oh crap give me a few minutes."

So vote how you like, with one exception. This is the exception: ballots designed to call attention to themselves are verboten. The lone spiked ballot in poll history came from Notre Dame uber-blog Blue Gray Sky after the first week of the season. Because I am stupid I deleted it, but by BGS's own admission it was designed to highlight how silly releasing a college football poll after one week of play is. This is a perfectly fine argument to make, and one I might even agree with, but your ballot is not the place to make it. Some voters tend to call attention to their ballots by their voting patterns, whether it's Straight Bangin's sadly prescient Michigan pessimism or SMQ's resume-only first week ballot or Double Extra Point's uncanny ability to have the most boring ballot; these are okay because their notability is a side effect of the voter's habits, not the entire point.

Other than that, feel free to be stupid -- because you will be stupid, iron law of polling, that -- in whatever way you want to. But I do think a unified philosophy benefits polling. SMQ highlights how goofy this polling enterprise can be:

But no one involved with any of the mainstream polls, despite their all-too-frequent use of the term, has ever defined exactly what they mean by the concept of the best team, or how they reach that judgment in comparison with that team's peers. Most of the time, the terms are described in an abstract way, as a mental sum of perceived parts, as if there existed a secret rating system, EA Sports-style, that could settle the issue once and for all.

The BlogPoll's concept of the best team in a sentence: the BlogPoll attempts to rank teams in order of season quality. This is impossible to do before the season and silly to do in the first few weeks, and at these times the poll should be regarded as an approximate guess of which teams will end the year with the highest season quality.

Suggestions to effect this ideal follow.

Once you have enough information, vote by resume only. What qualifies as "enough information" will vary from voter to voter, but I'm sure most will agree once teams are eight or so games into their schedules there's plenty of evidence to go on. Personally, by week five I try to excise everything except results. At that point there's no reason to look at future schedules, no reason to look at preaseason expectations or shiny offensive baubles. Just the facts, m'am.

When you don't have enough information, vote by your guess at team strength, not schedule. In an ideal world everyone would play an identically difficult schedule and this wouldn't be an issue. This is far from an ideal world, and some team just have nummy soft schedules. This is often cited as a reason to rank them high -- SMQ explicitly calls it out as a factor in his preseason ballot -- and drives me crazy.

Place great importance on schedule strength. The poll's greatest development in three years of existence was its continued, extreme skepticism of a Hawaii team that barely eked out victories against poor WAC teams and found itself in the top ten of most major polls and in the BCS against Georgia. That ended with Warrior limbs flung across most of New Orleans and everyone hurredly pretending like that never happened. You should take schedules into account more than it seems the other polls do, IMO.

Style counts. This is really tricky. If a team has three fluke plays go against them and loses a game it statistically dominated, what do you do? Dan Steinberg's pet Vegas Top 25 virtually ignores fluky results and thus can claim to be a better predictive device for upcoming games. The BlogPoll aims to be descriptive, not predictive.

The sad reality of college football these days is that schedules are so watered down and multiple teams will have the same records or nearly identical records at the end of the year but they'll have taken different routes to get there. So, yeah, team A had a better season if it crushed all comers and were under serious threat only a few times while team B squeezed by by the skin of its teeth, assuming schedules are approximately constant.

Back to SMQ for a pithy summary:

That is, assumptions about "the best" are frequently proven wrong by actual events. The best system, then, is not a rigid assessment of perceived strength, but an extremely fluid, strictly achievement-based approach that systematically rejects assumptions and accounts for chaos -- the inevitable black swan -- as the natural order. If South Florida's resumé is the second-best in the country in late October, then yes, it's the second-best team at that point. But probably not for long.

Co-sign. Man the ballot stations.

Comments

helloheisman.com

August 12th, 2008 at 12:28 PM ^

SEASON QUALITY and TEAM STRENGTH can often contradict eachother, and sometimes the latter is the more appropriate than the former.

Example - After the first several weeks of last season, lets say you thought Purdue beat better opponents than Ohio State did.  Thus, by your voting standards Purdue had a better season quality than Ohio State, and should be ranked higher.

Additionally - do you think it's appropriate to rank teams based on how you think their record will play out at the end of the year?  It seems like 80% of polls do this (try to predict the future top 10 based on their probable wins/losses) instead of ranking them by what they've accomplished so far or how strong they appear.

UMaD

August 12th, 2008 at 1:08 PM ^

The Vegas poll handles TEAM STRENGTH perfectly. It is predictive.

The blogpoll should be the Ying to this Yang and focus on SEASON QUALITY. It should be descriptive.

helloheisman is right to call out this conflict.

If
you want to have a philosophy it shouldn't be variable over time. This lack of clarity causes confusion and leads to voters
doing whatever the heck they want.

 

UMaD

August 12th, 2008 at 12:30 PM ^

I wholeheartedly agree with voting by resume.  Adding the caveat that a
voter should, for the first 5 (or
so) weeks of the season, vote based
on their opinion of what the future will hold complicates things needlessly and
does the poll a disservice.  It’s confusing enough to try to weigh the
merits of various teams with variables like margin of victory, fluke plays,
strength of opponent, weather, early-season vs. late season,
home vs. road, etc.  If the aim
of the blogpoll is truly to be descriptive rather than predictive, why not maintain that consistency throughout
rather than applying it only after the nebulous "enough information"
presents itself?

Either hold off on voting till after week 5 (or so) or just deal with the
wacky early season rankings that come with resume voting. 

Jack

August 12th, 2008 at 6:12 PM ^

... to get all Pirsig on you and ask you to define "Quality." But I'm not an asshole. Well, I AM an asshole, I'm just not being one now.