Thursday, June 3, 2010

Instant Replay and the Human Element

I'm fairly certain that almost anything that could be written about yesterday's not-quite-perfect game has already been written. Outrage, certainly, has been commonplace, as has, on the contrary, a respect for the class and dignity with which Jim Joyce and Armando Galarraga have handled the situation.

For any of my readers who are unaware, Armando Galarraga - an unheralded pitcher for the Detroit Tigers - was perfect through 8 2/3 innings last night, falling one out short of a perfect game. The kicker is that, on the 27th hitter, first base umpire Jim Joyce missed a call, awarding a hit to a batter who was - as replays have shown quite conclusively - out. Galarraga retired the next hitter, but the damage was done. Instead of a perfect game, or even a no-hitter, Galarraga had a complete game, one-hit shutout. Impressive, but not historic.

Amidst the backlash has been a swell in the ranks of baseball fans and, perhaps more importantly, journalists who support instant replay in baseball. The argument is simple and clear: replay cost Galarraga a perfect game, only the 21st in baseball history (and this would have been the first time ever that 3 had occurred in a single season). Just as high-profile missed calls on home runs a few years ago helped to usher in the review of so-called "boundary plays" in baseball, this missed call will likely hasten the already inevitable introduction of replay on safe or out calls at the bases.

For my own part, I have no qualms about the introduction of replay to baseball.* The major arguments against it, as far as I can tell, are that it would 1) cause the game to be longer, 2) cost a lot of umpires their jobs, and 3) eliminate the "human element" from the game. The last of these is the most slippery, and also, not surprisingly, the most frequently heard defense of traditional umpiring.

* Indeed, I'm an advocate of a computer-called strike zone. To me, this is an even clearer case than replay at the bases. Anyone who has watched an NFL game knows that replay is no guarantee that the call will be made correctly. All too often it simply cannot be determined whether a player makes a catch, for example. In baseball, this is equally true. In all of the baseball games I have watched, I have seen countless plays where, even in slow motion, I can't tell whether the runner made it to the bag first, whether the outfielder really got his glove under the ball, or whether that chopped down the line was in fair or foul territory when the third baseman touched it. Frankly, replay is imperfect, and that's before you get into questions about how to handle situations like a ball called foul that should have been fair.

Balls and strikes, on the other hand, are much simpler. Every team in the league, and every MLB television broadcast to boot, is using Pitch-FX data to map the exact location of each pitch. Bloggers and analysts across the Interweb are using that data to build actual vs. rule-book zones, to track how pitchers approach different hitters, and how umpires call the ball differently depending on the count (the zone, for instance, is much much much smaller on 0-2, and much much much larger on 3-0). If we can do all of that complex and interesting stuff, why can't we just let the Pitch-FX computer take over calling balls and strikes? Who loses in that setup? Sure, it would violate some umpire union contract - which probably is the biggest barrier - but it would help batters and pitchers by ensuring a more consistent zone, it would speed up the game by eliminating entirely arguments about balls and strikes, and it would reduce the incredulous cries of "WHAT!" from fans after blown calls behind the plate.

Hey, maybe we fans would miss complaining about poor umpiring behind the plate... But I suspect not. I'll take the correct call over the opportunity to complain when a Aaron Cook sinker gets miscalled any day.

Length of Game

I'm not convinced that replay would significantly lengthen the game. I hardly think that baseball should go to an NFL-style challenge system because there are plenty of ways to do replay that are more efficient. Tennis, for example, has a much faster challenge system, thanks in part to the obvious yes-or-no quality of the calls to be made. But the lesson is the same: don't make replay a big deal and it won't take long. There are a number of good proposals already floating in the blogosphere about instant replay that would specifically mitigate this concern, so if you're unconvinced, I encourage you to look around.

More than that, however, replay eliminates argument. Baseball games would be shorter if managers did not argue so many close calls. In the time it takes Jim Tracy to amble from the dugout to second base and back every time Dexter Fowler is caught stealing, some replay official could check the play, determine the accuracy of the call on the field, and relay that call to the umpires. And then have time to make a coffee and read an article from the New York Times. The point being, efficient replay would probably speed up the game, not slow it down.

Umpire Contracts

In reality, the second of the concerns above is the most problematic. MLB umpires are, in essence, like Supreme Court justices: once appointed, they retain the position for life or until they choose to retire. Whereas MLB players have to continually prove themselves or else face unceremonious release, umpires are essentially given a free pass, thanks to a strong union and, frankly, the comparative simplicity of what they do (compared, that is, to what players do).

If it is impossible to fire umpires anyway, how likely is it that umpires will be willing to accept assistance from technology that takes the hardest, most controversial, and probably most interesting part of their jobs away from them? Umpires are people, too, and they like making difficult decisions about who's safe and who's out at pivotal moments in a game, or else they wouldn't do what they do. Trying to take away a big part of what someone does, even when there's a better way, is hard. Look at how much trouble traditional newspaper journalists have had accepting blogs and Internet reporting and you get the idea.

Moreover, whereas NFL officials have a lot of judgment calls to make, even with replay, MLB officials are mainly enforcers of a fairly straightforward rulebook. There are not that many judgment calls in baseball, especially when you slow the game down on camera. What I mean is, rarely do you get into a situation where a call, after all available evidence has been considered, is still debatable. Oh sure, we have our own perceptions; Rockies fans will always think that Holiday touched the plate, Padres fans not so much, but such situations are the exception and not the rule. And, really, the point is that there still should be an answer to the question: was he safe?

Not so with a charging foul versus a blocking foul in basketball. Not so with a holding penalty or a pass interference in the NFL. The only thing that is comparable in baseball is the check swing, which is defined as, essentially, a judgment on the part of the umpire as to whether the batter tried to swing at the pitch. Everything else is clear-cut, or should be.

I think this is why, in the end, the union will resist replay. NFL officials have embraced replay because it is an aid, not a replacement. In MLB, replay is a replacement. Technology can not only help the people involved do better, it can actually do almost the whole job better. There's a difference, to extend the analogy, between using a calculator to help you solve equations in applied physics and using a calculator to divide fractions for you. In the first case the tool is aiding a bigger goal; in the second, it's replacing a less-capable human. In the first case, the tool feels necessary, in the second case - and especially if we're really good at dividing fractions without a calculator - we see the tool as helpful in ensuring accuracy and speeding up the process, but we can live without it. MLB umpires, undoubtedly, are really really good at their particular kind of division problem, but that doesn't mean the calculator isn't faster and more accurate. The problem is, because the calculator is not needed, per se, it's hard to sell a powerful union on the obsolescence of its members.

Hell, we still demand that kids learn how to divide fractions without calculators.

The Human Element

I've already started to address the third and most nebulous of the arguments against instant replay in the previous section, but I haven't really clarified what I think people mean when they say they want the "human element" to stay in the officiating of the game.

I confess, actually, that this impulse is confusing to me. Almost everyone who wants the "human element," I think, is really saying they want umpires to make bad calls in the favor of their own team. Or at least they want the possibility that such will happen. Having been to a number of baseball games, and having watched some large, barely-finite number more on the TV and computer, I think I can safely say that most fans don't really like it when umpires make bad calls that hinder their own team. I have, not once, heard an announcer or nearby fan say, after a missed call at first or a strike three six inches outside against the cleanup hitter: "Well, I don't like that call, but thank God for the human element." Mostly, there are cries of "BOO!" and "Kill the Umpire!" Indeed, the latter is immortalized in Casey At Bat, baseball's most famous poem.

Nor do I believe that people want to complain about bad calls. As I said in the posterisk above, while complaining is cathartic, the correct call will always be preferable. No, I really do think the human element means the slight chance that my team will be able to do better than it should have, thanks to that variation in consistency in the umpire's strike zone, and the off chance that he'll call Holiday safe, even if he didn't touch the plate.

The ironic thing is, most of the people who virulently support the need for the human element in umpiring and officiating are the most likely to complain about inconsistency among the umpires. Former pitchers - who often find their way to the broadcast booth - rail on consistency. "I don't care where the strike zone is, as long as it's consistent." This quotation, all by itself, is steeped in irony. They do care. They want the strike zone to be consistent. They want it to be where, in the end, it is supposed to be. They may like the game-to-game variation between umpire who calls pitches on the corners strikes versus the umpire who calls high pitches strikes and so on (something we could easily work into a computer, if we really like it that much, but I doubt we would, which goes to show), but the call for consistency, when taken to its logical conclusion, is a call for standardizing balls and strikes, both within games and between games.

And why not? In baseball, we can. I am hesitant, as you readers probably know, to take the human element out of things like teaching and learning, because those are far too complicated for a computer to manage effectively. But baseball is a much simpler thing, a much more quantifiable thing. And it does no injustice to the players or the fans if you get calls right. More than anything, I think replay and a computerized strike zone would add to the human element by allowing the truly remarkable humans who play the game to do it better.

A final thought: if, as is often said, umpires have done best when no one remembers them, then what is so human about the job to begin with? Don't we humans want to do things that are memorable? When we talk about the human element, don't we mean that we want to be able to talk about the glorious successes and the tragic failures and epic struggles that occur when man confronts man, or man confronts self, or man confronts some nebulous force? Perhaps, from that perspective, there's a wonderful human story in Jim Joyce's missed call. Perhaps. But if your best day on the job is the one where you go unrecognized, and if your worst day - the day for which you will always be remembered - is the day that you cost a no-name pitcher from Venezuela what is almost certainly his only shot at a perfect game, isn't time to think about what kind of human element we have in officiating baseball, and whether it is really worth such adamant defense?

Tuesday, June 1, 2010

Have Done Versus Will Do



After watching the above video - sent along to me and my fellow LDTers by one of our cohort members - I'm struck not by the differences in the ways we interact with time, but by the similarities. Regardless of whether we tend towards present hedonism or are instead future oriented - or, I suspect most often, some balance of the two - I think we are all beholden to the past in a subtle and not always obvious way. That is, whether we live in the moment or live for the future, it is the past that shapes that living, and the past which allows us to create expectations for both the present and the future.

A silly example of this is in how baseball teams sign players. While increasingly the MLB is moving towards younger, cheaper talent, there is still tendency to pay enormous salaries to older players not because of what they will do, but because of what they have done so far. The same problem runs rampant in the NFL and the NBA and, I imagine, European Soccer.

Where the reality of paying for what has happened instead of what will becomes more troublesome is in business or politics. In theory, where baseball and football players reach the heights of their abilities in their late twenties, we men and women of the real world don't really even start our proper careers until we're 30, and aren't expected to have the skills or experience necessary to lead until we're 50 or older. The assumption here - based on experience, granted - is that we continue to learn and improve as we get older, and that more knowledge, especially experiential knowledge, equates with more ability.

The problem is, while even the most future-oriented decision maker elects to do what he thinks will result in the best outcome, all of that future orientation comes from what has happened so far, collected from both personal experience and from learning through books, articles, and conversations with others (that is, the personal experience of others). That's not a problem, per se, expect that it is a terribly unreliable way to make effective decisions.

Which is not to say that there's a better way to make decisions. We can't, after all, depend upon much else than past information. Indeed, the word "information" practically has the past built into its very meaning. Rather, what I think we too often fail to realize is that, because the past is an imperfect predictor of the future, and because the systems and situations in which we make decisions are usually mind-boggling complex (whether we acknowledge it or not), there is simply no good way to know what will work, and it is irrational to expect anyone to make the right decision at almost any time.

The famous saying "hindsight is 20/20," comes to mind. But that's just the thing; hindsight isn't 20/20. Sure, we can know what happened, and we can watch the "will do" turn into a "has done," but even so, we are left with a single, anecdotal data point in a vast field of possible results. "What would you have done differently?" is, actually, one of the most difficult questions to answer when you really think about it, because there's simply no way to know what the effects of a different action would have been.

All of which is to say, time is a complicated, confusing thing that we often take for granted because, frankly, we must. Efforts like those in the video above to characterize our personal conceptions of time are useful, certainly, but we have to also remember that how we interact with the temporal world is not so easily categorized that it fits into neat boxes. All of us - at least all of us Westerners - to one degree or another, understand time in a fundamentally similar way, and while there are permutations between our understandings, it is not easy to say that high school drop-outs do so because they have different temporal priorities. Hindsight, in that case, is not 20/20, and there is no reason to believe that addressing that supposed cause will change anything about the future.

Saturday, May 29, 2010

The Role of Language in Politics

As any reader of this blog likely knows, I am generally displeased with the nature of political discourse in the United States. Thanks to major, for-profit media outlets like CNN, Fox, and MSNBC, our national discourse is shaped and our language is carefully selected to represent primarily the interests of the few extremely wealthy men who run those companies. As a result, we spend a lot of time talking about issues like abortion, stem cell research, and immigration policy - all admittedly important - and not much time talking about things like the structure of power, voting policies, and income distribution. Of course, we talk about those latter things some, but with those issues, as with the more popular and sensational issues listed before, the whole debate is framed by major media outlets. And that's the real point: the range of acceptable opinion has almost nothing to do with the range of possible solutions.

Perhaps the biggest reason for this is the brilliant associations the so-called right and left have made around each others' positions. Anything strongly conservative is "fascist," and anything strongly liberal is "socialist, communist, or Marxist." None of those words is used according to their actual meaning, but rather they have become bugbears, denoting some vague sense of evil and despair that comes from running a government that is not, as we call it, "moderate."

Moderate is much more a myth than words like Socialist and Fascist. How so? Because the concept of moderate depends upon a linear model of political discourse. For some reason we've all bought into the Facebook Likert scale of politics; each position is scored from strongly liberal to strongly conservative, with the middle being moderate. Why should this be? What is so linear about politics? On a superficial level, sure, it makes sense: if I believe the government should take measures to prevent illegal immigration, it is fairly easy to draw a straight line from there to the opposite position, which says that illegal immigrants should be granted amnesty. But does it really make sense to draw that line? Even if we can turn the general sense of what should be done into a linear continuum, surely there's room for debate on the how?

Consider: one person might argue that we need to build a big wall along the Mexican-American border. Another might say we need to round up all of the illegal immigrants in the country and deport them. Yet another might argue that we should work closely with the Mexican government to improve working conditions there, so as to minimize the incentives for immigration. Still another might argue that we ought to do our best to simplify immigration law so that it is easier to determine who is legal and who is not. And so on. The thing is, many of these positions are not mutually exclusive for any reason other than where they stand in our perceived left-right linear model of politics. Yet, if you were to ask most Americans, they would think that the border fence idea and the simplified immigration law idea are irreconcilable.

This is just a single example, but we could do the same with almost any issue. Try it yourself. Take a major, hot-button issue. Map out the conservative position and the liberal one. Then determine possible solutions, and see whether they are mutually exclusive.

I should say, what I'm talking about is not a moderate position, because that implies finding the midpoint of a line. My point here is that we are imagining - we believe almost unquestioningly - in a line that does not exist. There is no linearity in political solutions. Even a yes or no question like "should the USA reduce its military budget" cannot be answered by liberal-says-yes and conservative-says-no. The issue is more complicated than that. The issue is not, fundamentally, linear.

With all that in mind, I want to return to the words we use in politics to denigrate opposing positions. "That's socialism!" is the cry around which - ironically - many people rally when talking about President Obama (ironic because Obama is about as far from being a socialist as everyone who derides him for it; indeed, he probably has fewer socialist beliefs than most of the people who criticize him). No explanation is needed. No examination of why socialism is bad, how it works and doesn't work, and why we have to fear socialist reforms is offered in the national discourse. We take for granted that socialism is evil, that it has been tried and does not work, that income and wealth should never never never be distributed throughout the population.

In 1967, the median income in the United States was roughly $33,000. Someone in the 95th percentile, on the other hand, made roughly $89,000 per year. That's significant disparity, but not outrageous.

By 2003, the median income in the United States was roughly $43,000, while the 95th percentile had risen to $154,000.

I don't have the more recent numbers, but I suspect the gap is still growing. And here I wonder, when we start talking about economic policy, why we talk about socialism in such evil terms. Does the richest 5 percent of the country really need to make 4 or 5 times as much as the median (and lets not talk about the bottom 20 to 25 percent, who make less than a living wage)? Is it not possible and, perhaps, reasonable to change the way that income is distributed, not in some bizarre pseudo-Marxist equal way, but simply so that everyone can survive?

Here's the point. I'm guessing that, if you take out all political language, almost everyone will agree that, yes, everyone should have a chance to make it. Hell, it's in the declaration of independence. The thing is, we've been hoodwinked into thinking that equal opportunity exists under our current economic and social structures when it certainly does not. We've been fooled into thinking that we have a "welfare state," where people at the bottom are there only because they are lazy and incompetent. We've succumbed to the idea that there is no alternative - in the best of all possible worlds, to quote Voltaire - to what is increasingly a reverse-socialism in our economic policy.*

*That is, we have socialized losses and privatized gains, a truly despicable situation. Remember that the bailout was paid for by tax payers and paid out to large investment and insurance companies. In other words, a problem caused, at least in part,** by income disparity, was "solved" by increasing income disparity. Brilliant!

**It is worth noting that the biggest economic collapses of the last century occurred at the times of greatest income disparity; that is, in 1929, in 1987, and in 2008. Hmm...

All this because there is no language available to have a rational discourse around economic (or almost any other) policy. You believe in changing the tax structure so that it is more progressive? You're a socialist-communist-Marxist pig who doesn't deserve to be in the country, let alone the conversation. How much worse if you use the word - socialism - yourself? Gone are the days when Albert Einstein, Bertrand Russell, and John Dewey proudly called themselves socialists. Today you have to apologize, all because of the power of language.

What terms are available, however, is not the issue. The issue is that we have an entire political and social and culture machine that uses language to force us to think of politics as linear, and forces us to continually reinvent meaningful terms because the ones we try to use continually get twisted and saddled with innuendos and connotations they don't, in themselves, warrant. Language is a powerful thing - maybe the most powerful thing there is - and it seems we don't know how and don't want to use it responsibly.

Tuesday, May 25, 2010

Impressions of Walla Walla

My first impressions of the little middle-of-nowhere town that is home to world famous onions, a budding wine industry, and Whitman College were somewhat muddied by the unfortunate loss of a filling late on the night before my brother's college graduation. I was flossing my teeth when I felt a strange pop in my mouth, and soon saw a small, but quite hard white piece of something resembling plaster in the sink. Immediately I suspected that a filling had fallen out, and a quick rinse with water from the sink confirmed my suspicion in a thoroughly unpleasant way.

I wouldn't say getting water into the hole in my tooth from which my filling had been ejected was painful, but there was a kind of metallic hollowness in the sensation that frustrated me. Needless to say, the pleasure of attending graduation the next day, and eating what by all rights should have been a wonderful family meal thereafter was somewhat lessened by the presence of what seemed to me an increasingly sensitive and gaping void on the upper left hand side of my mouth.

Fortunately I was able to get to a dentist as soon as I returned to Palo Alto, but that doesn't change the strangeness and discomfort of the situation. Indeed - and before I talk about Walla Walla - there's something unsettling about any personal injury, and in an especially odd way, injuries to the teeth and mouth remind the injured of his or her own frailty. It is so easy to take for granted our seeming invincibility - that is, though we may ache or be sore from time to time, it is easy to play off such minor annoyance - in that, heretofore, most of us have existed and continue to exist in a more or less intact state continuously for as long as we can remember. I have no recollection of missing limbs or digits, or being unable to hear or see. Much less can I imagine being dead.

That might be silly to say, but I think it is silly only because it is so far from our consciousness most of the time. Something as simple as a missing filling, however, blows a hole in the entire facade. The seeming impenetrability of the body - and what is more impenetrable than the teeth, in particular? - melts away. Eating a strawberry, sipping on water, and even breathing hard send an echo of pain and, more disturbingly, incompleteness through the mouth. Where there should be me, there is nothing. And if something as trivial as a small missing filling can set off such a reaction, I cannot imagine what people who have lost fingers, or worse, must feel.

Anyway, that's a strange backdrop against which to discuss Walla Walla, Washington, but I mention it because it was a strange backdrop against which I encountered Walla Walla, Washington.

Walla Walla is certainly idyllic, despite the windy and cloudy weather during the weekend. The rolling hills and distant mountains reminded me of some combination of Northern California and New Mexico, the former because there was green everywhere, the latter because the mountains were actually mountains, and not hills masquerading as such. The outskirts of the town betrayed a mixture of old, industrial poverty and a modern almost production-free middle class suburb disconnected from any metropolis. Alongside the old decaying train that sat on unused tracks - a train, my brother informed me, that had not moved in his four years at Whitman - there were wineries and elaborate housing developments.

I suppose an economy based upon wine production is more industrial than some towns, or at least is some combination of industry and agriculture, but traveling into Walla Walla itself transforms the picture of a hardworking farm town into a small town American service economy. The Main Street is littered with wine tasting rooms, mechanics, and clothing shops, the only oddity being the overabundance of the former. Indeed, there are so many, and such upscale wine rooms that you would be forgiven for mistaking certain parts of Walla Walla for some chic Napa Valley getaway location populated by Silicon Valley millionaires. That Walla Walla has no such millionaires nearby - or, at least, hardly the same density as the Bay Area - makes the apparent success of the wine rooms all the stranger.

Walla Walla, for all the appearances of a self-sufficient land of wine and, I guess, tourism, is really organized around a single thing: Whitman College. That may be my biased perspective as well, given that I was in the city specifically to witness a graduation from the College, but its fortuitous location along the edge of the center of town, and its fairly substantial size make it an all-too-apparent part of the town's culture. Considering that the town has only some 30,000 residents, it is not surprising that even a small liberal arts college like Whitman makes up a significant piece of the fabric of the population.

But Whitman is more than just a collection of students in a town, it is the architectural framework around which the town is built. Arriving on Whitman's campus feels like arriving in the heart of Walla Walla, as if the town exists for the sake of the College. The buildings on the campus are like the Platonic forms of the buildings off campus, the perfect mirror for an imperfect world. The quaint Eastern Washington world of the town can only hope to aspire towards being like their collegiate neighbors. No wonder that, out of a town of only 30,000, there were seven graduates in my brother's class originally from Walla Walla, students undoubtedly enchanted by the magical city of continual youth, fresh ideas, parties, climbing walls, and enthusiastic learning that borders the old-American, red-neck agricultural world in which they had grown up.

Perhaps my truest glimpse of Walla Walla was had in leaving the town via the two-gate airport. I should say, the two "gates" were two doors approximately twenty feet from each other in the, for lack of a better word, terminal. My flight, at undoubtedly at the peak season for Walla Walla air travel, was one of two scheduled for Monday, both going to Seattle. Our 6:50 AM departure seems logical only because I imagine some wealthy Seattle businessmen who weekend in the Washington wine country, and can't bring themselves to drive the whole forty five minutes to Pasco each Monday morning.

Despite the early flight, what struck me as so perfectly small-town-America-meets-liberal-arts-college was the combination of passenger and security official that greeted my wife and I at the airport. We arrived plenty early - at about 5:45 - but were in line for security for some 20 or 30 minutes, thanks to a painfully slow checkpoint at which about one of every five passengers was pulled aside for a rigorous pat-down. The man in front of us was forced to pull out his iPad, a perfectly befuddling device to our security operators, for further inspection, even though Apple promises it is airport safe, and, as the man himself explained, he had been through security in Dallas, New York, San Francisco, and Denver without getting stopped before.

I have a theory that airport checkpoint rigor is inversely proportional to the size of the town in which the airport is located, and Walla Walla confirms this theory. But what was funny here was not the slowness of the checkpoint at 6:00 AM, with only one flight full of sleepy college graduation attendees, but rather the incongruity between the obviously conservative, God-fearing, gun-toting, true-blooded Americans running the checkpoint and the obviously liberal, iPad-toting, probably agnostic, New York Times reading, globally conscientious patrons of the airport. All of this was accentuated by a beautiful warning at the entrance to the security line about the American government's concern over whether Venezuelan airports were up to our security standards, as if anyone native to Walla Walla could name a single city in or person from Venezuela, let alone intend to travel there. I suppose the sign, then, was for the benefit of we world-traveling parents, friends, and siblings of the graduates.

Tuesday, May 18, 2010

Is It Luck?

There is perhaps no more polarizing argument in the baseball statistics world than the argument over "clutch." On the one hand, there's disagreement about what clutch even means, whether a batter up with the bases loaded in the 5th inning of a tie game is in as clutch a situation as a batter up in the ninth inning with two outs, his team down by three runs. The latter is a save situation, of course, and making an out ends the game. But there's a much better chance of actually changing the outcome of the game with the bases loaded in the 5th inning of a tie game. A double, for example, will likely give you a three run lead, where a double in the 9th will put a runner on second, still with two outs and down by three.

On the other hand, there's great disagreement about whether certain players can raise their game to perform better in clutch situations. Is it not the case, for example, that Derek Jeter simply plays better with his team down by a run in the 9th inning? Doesn't he become a better hitter? Likewise - and this is the other side of clutch - doesn't Alex Rodriguez suddenly forget how to hit home runs in the same situation, and turn into a puddle of self-doubt and failure?

The tricky thing, here, is trying to tell the difference between players who perform better in the clutch and players who perform better, period. Of course you want Albert Pujols or Derek Jeter up in the 9th inning with the game on the line, not necessarily because they are clutch, but simply because they are good hitters. The real question of clutch is not how well players perform in high leverage situations, but how much better or worse they perform in those situations relative to how they perform in normal situations.

Fortunately, Fangraphs keeps track of clutch. Their resolution of the first question - what counts as clutch - is based upon the very statistics that they pioneered: Win Probability Added (WPA) and Leverage Index (LI). Basically, for each and every major league game, Fangraphs keeps track of game situation and calculates the odds each team has of winning based on score, inning, outs, and runners on base. From there, they extrapolate the importance of a given situation. Intuitively, a high leverage situation is like the one I described at the outset: bases loaded in the 5th inning of a tie game. That's high leverage because the outcome of the next at bat will have a tremendous influence on the odds of each team to win the game. A strikeout will be huge for the pitching team, while a walk or a hit will give the batting team a run and the lead (and, again intuitively, the team currently with the lead is almost always favored to win the game).

Anyway, the point here is not to dive into WPA or LI, but rather to talk a little bit about clutch and the Colorado Rockies. As in years past, the Rockies are off to an awesome start pitching this season, but can't seem to hit to save their lives. That their defense has been suspect as well has helped to lead the team to a disappointing early-season record of 19-19. Not the end of the world, but .500 isn't about to catapult anyone into the playoffs, and playing .500 ball so far means the Rockies have to play way better than .500 the rest of the way to earn their first ever division title (or at least their first ever back-to-back playoff berths).

What ails the Rockies lineup, however, is not totally clear. While they have lacked star-power this year, what with Todd Helton and Troy Tulowitzki forgetting how to hit home runs, Miguel Olivo has been a pleasant surprise (at least so far), Carlos Gonzalez has been excellent, and Seth Smith might finally be working his way into the everyday lineup. The Rockies don't have the talent to have a top-flight offense, but they should be competent.

Except they can't hit in the clutch.

Whether clutch is a skill or not, the numbers are striking. The Rockies currently rank 28th out of 30 MLB teams in clutch hitting this season. That is, the Rockies perform significantly worse in high leverage situations than in normal ones, so much so that only two other teams (the Cubs and Brewers, incidentally) have been worse so far in 2010.

It is early in 2010, but what disturbs me is where the Rockies stand looking backwards to 2003, Clint Hurdle's first full season:

2009 - 27th
2008 - 23rd
2007 - 5th
2006 - 30th
2005 - 28th
2004 - 24th
2003 - 25th

Of course, 2007 was the year the Rockies made the World Series after an improbable run in September and October, and it stands out as an outlier in this list. What jumps out to me, though, is that the Rockies are really the only team routinely this low on the clutch list at Fangraphs. What are they doing wrong? Or is it just luck?

Any regular watcher of the Rockies over the last 10 years will confirm anecdotally what Fangraphs has in numbers: the Rockies routinely fail to produce in key situations. Back-to-back strikeouts with a runner on third and nobody out has been something of a theme for this organization. Again, is this an organizational problem? Is it a hitting coach problem? A manager problem? A personnel problem? Does it have something to do with Coors Field? Or is it just luck?

Obviously in 2009 the Rockies were fine without being a good team in high leverage situations, and Troy Tulowitzki - who has struggled to produce at his normal level in the clutch throughout his career - is still a fine player despite often failing in high leverage situations. There's also no reason to believe that Tulo, or the Rockies in general, will continue to struggle producing when it counts. And yet, as a fan, the trend is disturbing, and as a human being, I'm inclined to attribute the pattern to something.