September 28, 2012

Week 4 Storylines: RG3, Haslett and Redskins Embattled Defense



In Tampa Bay this week, where the Buccaneers are preparing to host the Washington Redskins on Sunday afternoon, the talk is about "containing RG3." As it should be. From the outside looking in, the most intriguing thing about the Redskins is their suddenly dangerous offense, led by dynamic rookie quarterback Robert Griffin III.

The phrase "highest scoring offense in the NFL" has a certain cachet, after all. It gets attention. It's also a legitimate concern to opposing teams. The Redskins are scoring a crisp 33 points per game, which projects out over the course of the season to 528 points. Clearly, preparing to play Washington had better involve crafting a plan designed to keep the hotshot rookie from "going off" and dominating Sunday night's Sportscenter highlights.

What the Bucs are not saying publicly, however, but what Redskins fans and observers know all too well they are probably thinking, is that to beat the Redskins these days what you really need to do is throw the damn ball. Like, throw it a lot. All day, all over. Deep, short, left, right, middle, whatever--just throw it.

Because the Redskins defense, statistically sound enough against the run (9th overall), has been performing so abysmally against the pass (31st) that the team is giving up 33.7 points per game. To put that number in perspective, the Redskins are on pace to set the all-time NFL record for points allowed (539) in a 16-game regular season. That infamous distinction currently belongs to the 1981 Baltimore Colts, who rolled over to the tune of 533.  

So rather than reveling in the surprisingly prolific training-wheel phase of their young franchise quarterback's career, and enjoying realistic discussions about Washington competing for a playoff spot (rarely a realistic expectation behind a rookie quarterback), Redskins fans face each successive week more convinced that the defense is simply incapable of stopping anybody, or of holding any lead.

The Redskins face the first real crossroads game of 2012 on Sunday. With a win, they can finish the first quarter of the season 2-2, with both wins against NFC opponents. A 2-2 September would bring another few weeks of playoff relevance in a season that, in the long view, is more realistically the launching pad to a new era.

With a third consecutive loss, however, and a fall to 1-3 in the deeply competitive NFC East, the 2012 season almost certainly will become an extended test lab for 2013 and beyond. That would not be the end of the world, obviously--not in view of the dawning reality that this franchise fellow is the real deal--but still a huge disappointment given the unexpected early success of the offense.

At 1-2 the Redskins are on the edge. It didn't have to be that way. Consider:

16 games were played in the NFL last week. Know how many teams scored enough points to overcome the 38 the Redskins surrendered in their 38-31 loss to Cincinnati? Two. Tennessee and Detroit played one another in a 44-41 overtime thriller. That's it. Care to guess how many teams won scoring 31 points or less? Thirteen.

Two weeks ago, on the road against the St. Louis, the Redskins scored 28 points against the Rams and lost, 31-28. Care to guess how many games NFL teams won that week scoring 28 or less?  Thirteen.

In week one against New Orleans, Washington put 40 on the board. A good thing, as it turned out, because the game still came down to Drew Brees lobbing one potentially blown Hail Mary call into the Redskins end zone for a tying touchdown on the final play of the game.

I have heard talk this week about the "sample size" of three games being too small to seriously consider in projecting out how poor the Redskins defense might be this season. Fair enough.  What I have not heard much about is the larger defensive picture. What about eight games? Here are the points allowed in the last eight games the Redskins have played:
12/04/11 vs Jets (L) – 34
12/11/11 vs Patriots (L) – 34
12/18/11 @ Giants (W) – 10
12/24/11 vs Vikings (L) – 33
01/01/11 @ Eagles (L) – 34
09/09/12 @ Saints (W) – 32
09/16/12 @ Rams (L) – 31
09/23/12 vs Bengals (L) – 38
Take away the outlier against Eli Manning and the defending Super Bowl champion Giants, who for some reason served as Jim Haslett's personal loofah last year, and over the past half a season the Redskins defense has surrendered a dismal ... 33.7 points per game. 

The problem hasn't just surfaced this year. It isn't just about the loss to injury and knuckleheadedness of safeties Brandon Merriweather and Tanard Jackson, respectively. It isn't that cornerbacks Josh Wilson and DeAngelo Hall are incapable of even average play.  It isn't just about losing linebacker Brian Orakpo and defensive end Adam Carriker for the season in week two. The harsh truth is that Redskins defense has been broken for a while now, and it says here that should come as no surprise.

When Mike Shanahan accepted the head coaching job in Washington, he hired Jim Haslett as his defensive coordinator. He did so for reasons no one has ever made particularly clear. Haslett’s resume as defensive coordinator at that time was average at best:
1996 (NO) – 13th overall (20th scoring, 3rd passing, 27th rushing)
1997 (PIT) – 6th overall (11th scoring, 18th passing, 1st rushing)
1998 (PIT) – 12th overall (7th scoring, 18th passing, 13th rushing)
1999 (PIT) – 11th overall (12th scoring, 4th passing, 26th rushing)
2006 (STL) – 23rd overall (28th scoring, 8th passing, 31st rushing)
2007 (STL) – 21st overall (31st scoring, 21st passing, 20th rushing)
For a more in-depth look at those years, and some context into the units he both inherited and left behind, feel free to look here. As to the past two years and three games in Washington?  Haslett's tenure in D.C. has done little to allay the initial skepticism, or to light any candles of hope that he finally his this NFL thing figured out and is about to join the ranks of elite coordinators:
2010 (WAS) – 31st overall (21st scoring, 31st passing, 26th rushing)
2011 (WAS) – 13th overall (13th scoring, 13th passing, 18th rushing)
2012* (WAS) – 30th overall (29th scoring, 31st passing, 9th rushing)
          * through 3 weeks

Yes, Haslett can come up with the occasional gem.. Every season he turns in a few games where the matchups fall right, the play-calling works, and the adjustments seem sound. The majority of the time, however, the game plans appear inconsistent week to week, he gets outguessed and burned too often calling plays, and the in-game adjustments yield too little improvement.

All of which begs the question ... would a midseason change help? Imposible to say.  Only Mike Shanahan, the other coaches and the players know if Haslett has "lost" the team, or if there is a better option already on the staff. But the alternative, unfortunately, is to continue sending a defense out week after week that comes up with a handful of big plays but simply cannot keep teams out of the end zone.

Worse, as time goes by, we hear more and more suggestions from other teams and coaches that the Redskins defense isn't hard to diagnose. The two most recent examples that spring to mind are St. Louis head coach Jeff Fischer and his "bring it, we got answers" attitude when asked about concerns over the Haslett blitz packages. And just this week, word whispered out of Cincinnati that the Bengals drew up that soul-killing wildcat touchdown bomb on the first play from scrimmage specifically to beat clear tells they had seen in Haslett's predictable zero-blitz response to the wildcat formation.

That kind of thing, over time, adds up. Particularly so when the stark evidence of the numbers seem to back it.  There really is no polite way of saying it, and I actually do kind of like the man's tough-guy, glowering image, but what it has come down to for me is the impression man is in a little bit over his head.



In fairness, Jim Haslett’s Washington biography is yet to be written. At this point there is no way to really know in which direction his trajectory is headed. The winds at present are are definitely blowing cold, though, and should it continue that way, the expression “zero blitz” could end up joining “rocket screen” and “what we do works” in the Redskins Ring of Lexicon Infamy. 

To my eye, Haslett’s record as an NFL defensive coordinator speaks for itself. And whether the 2012 Redskins defense turns it around and performs at an even average level, enough to give RG3 a fighting chance to have a winning rookie campaign, remains to be seen. For the record, though, I think Jim Haslett will be coaching elsewhere in 2013. Numbers alone never tell the whole story, that is a given. But sometimes what you see really is what you get.

Now for a little psychic whiplash:

Given the defensive disaster, there is every reason to tune in this Sunday hoping for the best but expecting the worst. Another 34-31 type of loss is easy to picture. On the other hand, Redskins recent history suggests that this is precisely the kind of game they play best in. They seem to reserve their best efforts for games they are expected to lose. 

I am on record as thinking Jim Haslett is a lame duck. That said, history shows he also manages every once in a while to craft an unexpected gem that buys him an eleventh-hour reprieve and another few weeks of benefit of the doubt. So against my better judgement, I am taking a deep breath, squaring my shoulders, and hanging this week’s prediction hat on Sunday in the Sombrero being being such a time.

Washington 26, Tampa Bay 23




No comments: