Week 15 Quick Reads

Week 15 Quick Reads
Week 15 Quick Reads
Photo: USA Today Sports Images

by Vince Verhei

With 7:47 to go in the fourth quarter on Sunday, Detroit Lions quarterback Matthew Stafford was sacked and fumbled. Oakland Raiders linebacker Aaron Curry recovered the ball for a touchdown, putting his team up 27-14 and seemingly knocking the Lions out of the playoff picture. With his team's season on the line, Stafford stepped up to save the day, throwing for 143 yards and a pair of touchdowns on the next two Lions drives to lead Detroit to a 28-27 victory. It was the third time this season Stafford has overcome a double-digit deficit to win. Has Stafford established himself as an elite quarterback? How does he stack up next to his NFC playoff peers?

For the season, Stafford now ranks ninth among quarterbacks in DYAR (Defense-adjusted Yards Above Replacement). That's the good news. The bad news is that five of the quarterbacks ranked above him are guys he'll likely have to beat to get to the Super Bowl. How does Stafford compare to those other quarterbacks in specific situations? We can answer that question using DVOA (Defense-adjusted Value Over Average), which measures value per play. More information on DYAR and DVOA can be found here, but in a nutshell: yardage matters, first downs matter, consistency matters, and avoiding turnovers matters a lot.

In alphabetical order, here are the six quarterbacks to whom we're comparing Stafford today:

  • Drew Brees, New Orleans Saints
  • Eli Manning, New York Giants
  • Aaron Rodgers, Green Bay Packers
  • Tony Romo, Dallas Cowboys
  • Matt Ryan, Atlanta Falcons
  • Alex Smith, San Francisco 49ers

While Tarvaris Jackson and the Seahawks or Caleb Hanie and the Bears still have mathematical hopes at reaching the playoffs, the NFC field will likely come from those seven teams (including Stafford and the Lions).

Stafford ranks sixth among that field in DVOA over the course of the season, but the beauty of DVOA is that we can separate it into a number of different categories. For starters, we can measure each passer's performance by quarter. Stafford is last among this group in first-quarter passing DVOA, fourth in the second quarter, and third in the third quarter. However, despite his late-game heroics, he ranks just six in the fourth quarters and overtime. Stafford's big finishes are not guaranteed, and the NFC's other top quarterbacks are also capable of clutch end-of-game play.

We can further break DVOA down by, er, down. Stafford ranks second among this group (behind Rodgers) in first down passing DVOA, but slips to sixth place on second downs and a distant seventh place on third downs. The lesson here is that the Lions are better off passing early in drives, rather than running to set up makeable third downs. (DVOA accounts for yards needed for a new set of downs, so Stafford's bad showing here doesn't mean that he was left in third-and-long situations.)

What about field position? At Football Outsiders, we break the field down into five 20-yard segments, starting with the red zone (you're probably familiar with this one), and then moving back to the front, mid, back, and deep zones. Stafford is first in this group in the front zone, which keeps Detroit from kicking too many long field goals or short punts. However, he's no better than fifth in any other zone. Stafford needs to play better by the goal-line, but also on his own side of the field.

And then there's the length of the passes. Stafford is third in DVOA on passes thrown behind the line of scrimmage. However, he's a distant seventh in passes thrown up to 15 yards downfield, and just fifth on passes thrown 16 yards or deeper. The Lions have a dangerous screen game, but Stafford falls short of his peers on medium and deep throws.

It's been a breakout year for Stafford, and a great year for Detroit. If the Lions are counting on their quarterback outplaying his opposition in the postseason, though, they're in for a rude awakening.

Quarterbacks
Rk
Player
Team
CP/AT
Yds
TD
INT
Total
DYAR
Pass
DYAR
Rush
DYAR
1.
Drew Brees NO
32/40
412
5
0
295
294
1
Brees' game against the Vikings was the best game for any quarterback this season. Before opponent adjustments, it worked out to 346 YAR, but Brees is penalized for playing a flimsy Vikings defense that has now given up the most touchdown passes in the league (26) while tying for the fewest interceptions (six). Brees now leads the league with 2,159 passing DYAR on the season, ahead of both Tom Brady (2,022) and Aaron Rodgers (1,999). However, Brees also has more than 50 pass plays more than Brady, and nearly 100 more than Rodgers, and Rodgers is still the league's top quarterback in DVOA.
2.
Philip Rivers SD
17/23
270
1
0
224
224
0
At halftime, San Diego was ahead 17-7 and the game was still in doubt. Rivers then did this in the third quarter: 5-of-7, 89 yards, with every completion gaining at least 11 yards and a first down, including a 28-yard touchdown. At the end of the third San Diego was ahead 31-7, and Rivers threw only one more pass after that.
3.
Matt Stafford DET
29/52
391
4
0
198
192
5
Stafford won the game with two late touchdown drives, but his "clutch" performance (fourth quarter, within one score) wasn't as good as you'd expect: 7-of-12 for 96 yards, six first downs, one touchdown, plus a 17-yard DPI.
4.
Carson Palmer OAK
32/38
367
1
0
195
195
0
Palmer's passing wasn't quite as great as his raw numbers look. He had 11 failed completions, tied with Matt Hasselbeck for most in the league. His third-down passing was particularly deceptive: he went 6-of-7 for 38 yards, but none of those completions actually picked up a first down. He also had one failed fourth-down pass. On fourth-and-1 from the Detroit 24 in the first quarter, Palmer threw incomplete to Denarius Moore into the end zone. Given the game's final margin, the Raiders probably regret that playcall.
5.
Kyle Orton KC
23/31
299
0
0
189
189
0
Orton threw seven passes in the fourth quarter, each while protecting a one-score lead. He went 5-for-7 for 86 yards and four first downs. Of course, he may have been ahead by more than one score if he hadn't gone 1-of-6 for 8 yards and no first downs in the red zone.
6.
Matt Ryan ATL
19/26
224
3
0
161
161
0
Atlanta defeated Jacksonville 41-14, and it easily could have been worse. Ryan threw six red zone passes. One was a 6-yard touchdown to Roddy White. Two were completed passes that failed to convert third downs, and three were incomplete.
7.
Tony Romo DAL
23/30
249
3
0
159
151
9
Romo completed each of his first four passes. Then he threw one incompletion, then hit five in a row. He had some more muddled success, then hit seven in a row. This was all before halftime.
8.
Michael Vick PHI
15/20
274
1
1
156
136
21
Vick on deep passes (more than 15 yards past the line of scrimmage): 5-of-7, 178 yards, one Hail Mary interception.
9.
Tom Brady NE
23/33
320
2
0
115
127
-12
New stat idea: In basketball, point guards get an assist for getting the ball into teammates' hands and putting them in position to make plays. So let's give quarterbacks an assist for any completion with at least 10 YAC. Brady had nine assists against Denver, and has 80 on the season. Nobody else has more than 67 (Matthew Stafford and Philip Rivers).
10.
Alex Smith SF
18/31
187
1
0
113
106
7
11.
Tarvaris Jackson SEA
19/31
227
1
0
96
105
-9
Second-half numbers: 15-of-19 for 176 yards, nine first downs (including a touchdown), no sacks, no interceptions. At one point in the third quarter he completed four passes in a row for 33, 43, 21, and 10 yards.
12.
Cam Newton CAR
13/23
149
2
0
94
75
19
Newton had six carries for 56 yards against Houston. Three of them were third-down conversions (with 10, 8, and 2 yards to go). One was a 13-yard gain on second-and-8. And one was an 11-yard gain on second-and-12. Third-quarter passing: 3-for-9, 6 yards, no successful plays. Fourth-quarter passing: 3-for-3, 57 yards, three first downs.
Rk
Player
Team
CP/AT
Yds
TD
INT
Total
DYAR
Pass
DYAR
Rush
DYAR
13.
Aaron Rodgers GB
17/34
235
1
0
50
27
23
Not counting the Packers' bye week, Rodgers had ranked in the top 10 in quarterbacks every week of the year, and ten times in the top four. He finished 12th in Week 15, in perhaps the season's most surprising defeat. He gets a small boost over his raw numbers for playing the Chiefs' defense, which has been tougher than most against opposing quarterbacks. He gets a bigger boost from his rushing value -- his three carries resulted in a 5-yard gain on second-and-7, a 19-yard gain on second-and-4, and an 8-yard touchdown on third-and-3.
14.
Matt Moore MIA
10/20
217
2
0
47
47
0
The entirety of Moore's value basically came on one three-play stretch over the first and second quarters: 30-yard completion to Charles Clay; 22-yard touchdown to Anthony Fasano; 31-yard completion to Brian Hartline. He actually had negative DYAR over the rest of the day.
15.
Rex Grossman WAS
15/24
185
1
2
43
43
0
First quarter: 6-of-9 passing, 57 yards, but only three first downs, with two interceptions and a sack. His last pass of the quarter was a 7-yard gain on fourth-and-1, and it was more or less smooth sailing from there.
16.
Jake Locker TEN
11/16
108
1
0
42
39
4
Hat tip to Tom Gower for pointing this out: At one point, Locker went 9-yard completion, 9-yard completion, 9-yard run, 9-yard completion. Then he was sacked for a loss of ...

(wait for it)

... 9 yards.
17.
John Skelton ARI
28/46
313
1
1
15
13
2
Skelton's last eight passes of regulation: 3-of-8, 26 yards, no first downs. He still got credit for a fourth-quarter rally and an overtime win. Clutch, baby.
18.
Tim Tebow DEN
11/22
194
0
0
14
3
11
Facing a fourth-and-17 down 18 points in the fourth quarter, Tebow was sacked for a 28-yard loss. That is, by far, the biggest mega-sack of the year, easily surpassing Cam Newton's 20-yard sack against Indianapolis.
19.
Andy Dalton CIN
15/26
179
0
1
13
13
0
Dalton failed on his first three third-down plays. He then converted four in a row before failing on his final try.
20.
Seneca Wallace CLE
18/31
226
1
0
12
1
12
What? He's still in the league? Well, yes. At the start of the fourth quarter, Wallace and the Browns were ahead 17-7. From that point on, Wallace went 4-of-10 for 38 yards, only one first down, plus two sacks and a fumble, and Cleveland lost in overtime. Earth to Mike Holmgren: Seneca Wallace is 31 years old and a 9-year pro. He's not going to get any better. Give up and move on.
21.
Dan Orlovsky IND
11/17
82
1
0
12
12
0
You've got to actually see Orlovsky's play-by-play in its entirety to appreciate the pure nothingness of it all. It's fantasy football in the mind of Sartre. In the first half he went 8-of-14 for 48 yards with no sacks, no interceptions, and no first downs. His last play of the half would have gone for a first down, but Pierre Garcon fumbled the ball away. (Failed dreams of completion, indeed.) In the third quarter, he had three plays: a 7-yard gain on third-and-6; a 9-yard gain on first-and-10; and an 18-yard touchdown to Reggie Wayne. And then, perhaps having achieved fulfillment, he would pass no more. Keep in mind, the Colts won.
22.
Kellen Clemens STL
26/36
229
1
0
5
9
-3
Third downs: 5-of-7, 28 yards, two first downs, plus three sacks and a fumble.
Rk
Player
Team
CP/AT
Yds
TD
INT
Total
DYAR
Pass
DYAR
Rush
DYAR
23.
Josh Freeman TB
18/27
148
1
0
4
6
-2
First half: Two completions for 14 yards, two incompletions, two sacks, no first downs. And then, on his first play of the third quarter, he was sacked again. From that point he started picking up first downs and stuff, but by then Tampa Bay was down multiple touchdowns.
24.
Ryan Fitzpatrick BUF
31/47
316
2
3
-6
-11
5
Fitzpatrick in his "back" zone (between his own 20 and his own 40): 11-of-17 for 84 yards, only two first downs, six failed completions, two sacks, and two interceptions.
25.
Ben Roethlisberger PIT
25/44
330
0
3
-25
-25
0
26.
Eli Manning NYG
23/40
257
0
3
-26
-26
0
For the season, Eli has 689 DYAR on deep passes, fifth behind Rodgers, Brees, Rivers, and Romo. Against Washington, though, he went 3-of-8 for 72 yards with three interceptions (and a 43-yard DPI) for -73 DYAR on deep balls.
27.
Christian Ponder MIN
15/31
120
2
1
-46
-60
14
My God, there were some miserable quarterback performances this week. Ponder started 2-of-6 for 8 yards with no first downs and a sack. Then he threw a 10-yard touchdown to Toby Gerhart. His next 12 dropbacks produced three completions for 23 yards, five incompletions, three sacks, one intentional grounding call, and no first downs. That is one first down produced in 21 plays. And we haven't even gotten to Blaine Gabbert yet!
28.
T.J. Yates HOU
19/30
212
0
2
-69
-75
7
Third down passing: 4-of-9 for 22 yards, two first downs, two interceptions.
29.
Joe Flacco BAL
23/34
226
2
2
-95
-100
5
The Ravens were only down 17-7 at halftime. Flacco's first two passes of the third quarter were first downs to Torrey Smith and Ed Dickson. His next 15 dropbacks produced one first down (a 10-yard gain on second-and-5), three sacks, two interceptions, and one fumbled completion (which isn't Flacco's fault, but still).
30.
Matt Hasselbeck TEN
27/40
223
0
2
-98
-94
-4
First half: 8-of-16 for 78 yards, but only three first downs. The Titans were actually ahead 6-3 at halftime because, well, it's the Colts. Hasselbeck made a lot more big plays after that, but also had all three turnovers in the second half.
31.
Blaine Gabbert JAC
12/22
141
1
1
-104
-106
1
Gabbert's first pass of the fourth quarter was an incompletion. To that point in the game, he had dropped back 13 times. One of those plays was a 21-yard gain on second-and-16. He had three other completions for a total of 1 yard. Meanwhile, he was sacked five times, fumbling twice. To repeat some mind-boggling info: In 13 dropbacks, Gabbert had one successful play, negative net yards, five sacks, and two fumbles. That's -152 DYAR. He then engaged in some major league stat-padding in the fourth quarter, when he was down by five touchdowns (and even then, he threw an interception). Gabbert now has -686 DYAR on the year. That would be among the bottom 10 seasons of all time, but David Carr's record of -1,113 with the expansion Texans in 2002 is safe.
32.
Mark Sanchez NYJ
15/26
150
2
2
-107
-82
-25
It probably wouldn't have given the Jets the win, but the final margin against the Eagles would have been a lot closer if Sanchez had played better in the red zone: 5-of-7 passing, 29 yards, two first downs, one touchdown, one sack, one interception. That touchdown came in the fourth quarter, and cut the lead to 26 points.
33.
Caleb Hanie CHI
10/22
113
1
3
-135
-149
14
In 26 dropbacks against Seattle, Hanie had only six first downs. Meanwhile, he was sacked four times and threw three interceptions, including a pair of pick-sixes. His first-down performance was remarkably impotent: 1-of-6 passing with an interception, with his only completion going for -4 (that's minus-four) yards.
Five most valuable running backs
Rk
Player
Team
Rush
Yds
Rush
TD
Rec
Yds
Rec
TD
Total
DYAR
Rush
DYAR
Rec
DYAR
1.
C.J. Spiller BUF
91
1
78
1
89
45
43
In the first seven months of his career, Spiller was a backup, and a consistently bad one. The former first-round draft pick posted a rushing DVOA of -10.5% in his rookie year, and precisely matched that figure in the first 14 weeks of 2011. He was a model of efficiency against Miami, though, with nine of his 12 carries gaining 5 yards or more. He finished with 12 carries for 91 yards and a touchdown. He was also thrown 11 passes, catching nine of them for 78 yards, including gains of 11, 14, and 19 yards.
2.
Darren Sproles NO
33
0
79
1
57
8
49
3.
Pierre Thomas NO
44
1
41
0
56
31
25
If you could combine Thomas and Sproles into one player — Pierren Sprolesmas, perhaps -- he would have been the most valuable running back of Week 15. As it was, Thomas and Sproles finished second and third in the weekly rankings. Thomas had just eight runs and only two pass targets, but six of those runs gained 5 or more yards, another was a 1-yard touchdown, and his two receptions gained 25 and 16 yards. Sproles wasn't nearly as steady on the ground -- six of his eight runs gained 3 yards or fewer, with the other two going for 6 and 14 yards -- but he caught five of the six passes thrown his way, and four of those receptions gained 9, 13, 18, and 39 yards. Their combined statline: 16 carries for 77 yards and a touchdown, with seven catches in eight targets for 120 yards.
4.
Steven Jackson STL
71
0
72
0
46
4
43
Virtually all of Jackson's value came as a receiver. He caught nine-of-ten passes, including seven successful catches, five first downs, and four receptions of 10 or more yards.
5.
Arian Foster HOU
109
1
58
0
42
28
14
Eleven of Foster's carries against Carolina were successful. He was stuffed for no gain or a loss just once, had five first downs (including a touchdown), and three runs of 15 yards or more. He also caught five of the six passes thrown his way, including gains of 22 and 25 yards.
Least valuable running back
Rk
Player
Team
Rush
Yds
Rush
TD
Rec
Yds
Rec
TD
Total
DYAR
Rush
DYAR
Rec
DYAR
1.
Cedric Benson CIN
74
1
11
0
-55
-58
3
Benson's raw numbers (22 carries for 74 yards) may not earn him an invitation to Canton, but they hardly sound like the worst runner of the week, either. So why is Benson at the bottom of our rankings? Benson was stuffed for no gain or a loss nine times, but more importantly, he fumbled three times. The Bengals recovered all three of his fumbles, but our research has shown fumble recovery is more about luck than skill and so Benson is punished for putting the ball on the ground regardless of who eventually fell on it. Two of those fumbles came after Benson gained at least 10 yards, turning big-time positive plays into big-time negatives. He was also thrown two passes, catching one for 11 yards.
Five most valuable wide receivers and tight ends
Rk
Player
Team
Rec
Att
Yds
Avg
TD
Total
DYAR
1.
Calvin Johnson DET
9
14
214
23.8
2
113
In addition to the numbers listed above, Johnson drew two defensive pass interference penalties for 14 and 17 yards. Seven of his receptions gained 17 or more yards. The other two gained only six yards apiece, but one was a touchdown and the other was a first down on third-and-4. The Lions threw him seven balls in the fourth quarter, and he caught four of them (plus the two DPIs) for 130 total yards.
2.
Malcom Floyd SD
5
6
96
19.2
1
60
Five of Floyd's targets came on second down, one on third down. Each of his catches went for a first down, and each gained 12 or more yards, including a 28-yard touchdown.
3.
Darrius Heyward-Bey OAK
8
9
155
19.4
1
57
Has the 2009 first-round draft pick finally shed the bust label? Heyward-Bey set career highs with eight catches and 155 yards against Detroit. Six of those catches gained first downs, and a seventh would have as well if Heyward-Bey had not fumbled at the end of a 29-yard gain.
4.
Brent Celek PHI
5
6
156
31.2
1
57
Celek's final catch was a 6-yard gain on third-and-9. His first four catches went for 38 yards, 26 yards (and a touchdown), 13 yards, and then 73 yards.
5.
Aaron Hernandez NE
9
11
129
14.3
1
57
Hernandez' big catches included gains of 16, 22, 25, and 46 yards. His short catches included two 8-yard gains on first-and-10 and a 1-yard touchdown.
Least valuable wide receiver or tight end
Rk
Player
Team
Rec
Att
Yds
Avg
TD
Total
DYAR
1.
Damian Williams TEN
2
6
15
7.5
0
-41
Dedicated readers may remember Williams' name from Week 11, when he was also the least valuable receiver in the league. Though he wasn't quite as bad against the Colts on Sunday as he was a month ago against Atlanta (one catch for 16 yards in 11 targets!), he was still virtually useless against one of the softest defenses in the league. Tennessee threw him six passes on Sunday. Two were caught, one for a 9-yard gain on first-and-10, the other for 6 yards on third-and-13. The other four fell incomplete.

Comments

224 comments, Last at 22 Dec 2011, 8:17pm

#88 by nat // Dec 20, 2011 - 1:25pm

Wow.

I understand how you arrive at two "stuffs" (arguably the best results possible, considering the score and time remaining) would each? cancel an earlier TD in a one-point game. I understand that a two yard gain to get a first down might be below average. But this isn't a sign that Brady played badly on those plays. It's a sign that DVOA has problems judging short yardage situations, and deep problems when clock management becomes important.

Just what was the baseline success value on a first-and-goal from the one, up eleven with less than five minutes left to play? Where those plays treated as similar in value to, let's guess, a six yard sack on second-and-ten?

Points: 0

#91 by jimbohead // Dec 20, 2011 - 1:29pm

re: seneca wallace - its ok Vince. We all understand the horrors of being a Seahawks fan during the late Holmgren era.

Points: 0

#92 by nat // Dec 20, 2011 - 1:33pm

Regarding Vick and Brady, you might take a look at the total baselines for each team in the games. Is it possible that Brady and Vick were judged differently, not because of the success points over average they each earned, but because those success points were divided by different denominators?

As you point out, first-and-goal from the one sets a very high bar, and that high bar devalues ALL plays in the game, not just one.

Points: 0

#94 by Vincent Verhei // Dec 20, 2011 - 1:41pm

Is it possible that Brady and Vick were judged differently, not because of the success points over average they each earned, but because those success points were divided by different denominators?

I don't even need to check that. Not only is that possible, I'm sure it happens all the time. What's your point?

Points: 0

#113 by nat // Dec 20, 2011 - 2:14pm

My point is that they were graded on different scales. Each success point is supposed indicate equal amounts of success - at least after subtracting out the "average" success for the situation. That's how the success value was designed to work.

Consider: If Vick and Brady each make the same play in the same situation in the first half of his game, why does YAR wait to the end of the games to figure out which play had the most value? They were exactly the same. Obviously. Any other answer is wrong.

But that's exactly what YAR does when it divides by a game-specific total baseline. It waits (unnecessarily) until the end of the game to determine (wrongly) that the two plays had different value. (edit: I am assuming here that YAR is figured the same way as VOA. Correct me if I am wrong.)

Subtracting out a situation-specific baseline to get "success over average" is good. Applying a game-specific scaling factor is bad.

Points: 0

#128 by Eddo // Dec 20, 2011 - 2:51pm

YAR doesn't divide by anything, it's a counting stat. And I'm fairly sure the statement "If Vick and Brady each make the same play in the same situation in the first half of his game, why does YAR wait to the end of the games to figure out which play had the most value?" is wrong. If both Brady and Vick throw an eight-yard pass on first-and-ten with 5:00 left in the first quarter, they'll both get the same YAR for it.

The "D" part, I believe, is applied afterwards, though.

Points: 0

#148 by nat // Dec 20, 2011 - 3:42pm

YAR converts (success points minus replacement level) to YAR-yards. If that factor is game-specific or play-specific, my concern remains. The grading scales for two QBs would be different - albeit in two different ways. If the factor is constant, then life is good.

For VOA, the scaling factor isn't constant, which leads to problems. I assumed YAR had the same issue. I'd love to be wrong.

Points: 0

#173 by Joseph // Dec 20, 2011 - 8:57pm

nat,

I believe Eddo is correct about YAR--it's a counting stat, and so the factor/grading scale/etc. is constant. If I understand it correctly, it is somewhat based on Success Rate. The "D" in DYAR is a different factor for each team, and I believe is divided into running plays vs. passing plays. In other words, when teams played MIN the last few years, success on runs was rewarded more than passing success.

Points: 0

#180 by nat // Dec 20, 2011 - 10:08pm

Well, I hope you're both right.

I understand about the D factor being different for different teams. That's as it should be, which is why I focused on YAR instead of DYAR.

Points: 0

#182 by Vincent Verhei // Dec 21, 2011 - 12:09am

Both VOA and YAR are based on the same principles:

* Calculate the Point Value for each play.
* Calculate the average-level and replacement-level performances for all plays in similar situations.
* Calculate the difference between Point Value and average Point value or replacement point value
* For VOA, the resulting number is then expressed as a percentage of the average point value. For YAR, the resulting number is then modified to resemble value in terms of yards of field position. This modification is the same for all plays and all teams. It is set for each play at the point it happens, and does not change at the end of the game or at the end of the year.
* After all that, both VOA and YAR are modified for opponent.

Points: 0

#186 by nat // Dec 21, 2011 - 8:59am

That's a relief. YAR, at least, isn't hit by the team and game specific scaling problem.

Thanks for a clear explanation. Excellent job.

Points: 0

#194 by Thomas_beardown // Dec 21, 2011 - 12:52pm

Why would you think it was?

The "D" that prepends YAR or VOA is the opponent adjustment part that does game specific adjustments.

Points: 0

#197 by nat // Dec 21, 2011 - 1:13pm

Because VOA itself is subject to a game-specific scaling factor when it is converted from "total success points above average" to a percentage. This happens before the "D" adjustment is applied.

If your team gets into an unusually large number of short yardage situations, its total baseline for that game will be unusually high. That will devalue the excess success points you team earns from each and every play (not just the short yardage ones), forcing your team's VOA closer to zero for reasons having nothing to do with quality of play.

Imagine two teams, each with 60 offensive plays, each with a 10 yard gain on second-and-nine from midfield in the first half. Those two plays could contribute a different amount to those teams' VOAs, not because the plays are different, but because the teams got into different situations in the second half.

Why should a second half play change the value of a first half play?

Points: 0

#198 by Thomas_beardown // Dec 21, 2011 - 1:21pm

"Why should a second half play change the value of a first half play?"

I don't think it does. Unless you have a specific example of this.

Points: 0

#199 by nat // Dec 21, 2011 - 1:35pm

If you go back to the "Last Word on the Jets Week Five" article, you'll see that

VOA = sum(success-baseline) / sum(baseline)

By beginning-level algebra, that's the same as

VOA = sum( (success-baseline)/ sum(baseline) )

The inside term is just this: the success value above baseline from one play, divided by a factor related to the overall mix of plays for the entire game.

QED: each play's contribution to VOA is scaled by a factor determined by other plays. That includes first half plays whose value is largely determined by what situations (therefore baselines) come up in the second half.

I hope that's clear enough. I could walk through an example from that game if you want.

Points: 0

#202 by Thomas_beardown // Dec 21, 2011 - 2:42pm

That's how you calculate VOA for an entire game, not for one play.

So yes, doing worse later in the game will lower your VOA for the game, but if you took a 1 play section out and looked at it, it wouldn't.

Points: 0

#206 by nat // Dec 21, 2011 - 3:49pm

The effect I'm talking about has nothing to do with how well you do in the second half. It has to do with the baselines you face throughout the game.

You are right that you can take out a section of a game and create yet another scaling factor for those plays. But that's not the scaling factor that is used in calculating the game's VOA. At best, that's a red herring. But really it's just another example of how a play's value is scaled inconsistently.

These are the steps of calculating VOA (leaving out redzone for now):

(1) A success over baseline score is calculated for each play.
(2) A total baseline is calculated for the whole game.
(3a) Each play's score is divided by the total baseline to give its contribution to VOA.
(4a) Those impacts are totaled to give VOA

Technically, the VOA calculation reverses steps (3) and (4) like so:
(3b) The plays' scores are totaled.
(4b) The total is divided by the total baseline.

But division is distributive over addition. So (3a) and (4a) give the same result as (3b) and (4b). This is not a coincidence. It's mathematically the same calculation and means the exact same thing.

It's not that doing badly late in the game will lower your whole game VOA. It's that getting into a lot of high-baseline situations in the second half will lower the value (step 3a) of your first half plays. It doesn't matter how well you do on those second-half plays at all.

Why should getting into a lot of short yardage situations in the second half effect the value (3a) of a first-half play? It shouldn't. And yet, it does.

Points: 0

#205 by Vincent Verhei // Dec 21, 2011 - 3:47pm

You're off on this. The baseline for each play is just that, the baseline for each play. We do not use the same baseline for entire games. Otherwise, we couldn't do things like calculate DVOA on first downs across multiple games. The "sum of baselines" is determined by all plays in whatever sample you're talking about. Therefore, the "sum of baselines" for one play is in fact that one play.

If you're point is that a few unexpected results on high-leverage plays (high success on a play with a very low expected baseline, or vice versa) can skew DVOA, then you're correct. But don't you think teams SHOULD get extra credit for converting a third-and-20, or turning the ball over on first-and-goal at the 1?

Points: 0

#208 by nat // Dec 21, 2011 - 4:02pm

Vince:

Please look at the data presented in this article.

You will see that the games' VOA is indeed calculated from

sum(value over baseline)
divided by
sum(baseline)

You may never present a single play's VOA impact as a separate number. But your calculations do indeed scale a play's contribution to VOA in the way I have described.

Points: 0

#211 by Eddo // Dec 21, 2011 - 4:53pm

Yes, but your initial statement was:

"Consider: If Vick and Brady each make the same play in the same situation in the first half of his game, why does YAR wait to the end of the games to figure out which play had the most value? They were exactly the same. Obviously. Any other answer is wrong."

YAR does NOT wait until the end of the game to figure out which play had the most value. In fact, YAR will judge each individual as exactly the same.

What you're citing with the sums is the full-game VOA.

Points: 0

#213 by Vincent Verhei // Dec 21, 2011 - 5:15pm

But your calculations do indeed scale a play's contribution to VOA in the way I have described.

OK, when you word it that way, yes, you're 100% correct. When we analyze a group of plays -- whether it's in one game, one quarter, all third down plays, all red zone plays, whatever -- performance on those plays with the highest or lowest expected baselines will have the biggest impact on VOA. No question about that.

I guess what you're proposing is that rather than sum the values and baselines from all plays, we should calculate VOA for each play individually and then use the average of all DVOAs. Is that a fair summary of your argument?

Points: 0

#214 by nat // Dec 22, 2011 - 9:20am

Actually not quite. I don't want to move from a game-specific scale (total baseline) to a play-specific scale (baseline for each separate play). I want to move to a uniform scale, so comparing VOAs and DVOAs is valid.

Here's my thinking: A success point is supposed to be worth - in a predictive skill sense - the same in all plays. Because of the way success value is defined, the "zero point" for success may have a bias one direction or another for different situations. That should be okay, because we always compare to an average or replacement level for the situation.

The key point is that any additional success point represents the same skill over the opponent as any other success point. Success points are all the same size.

We'd like a VOA percentage point to have the same consistent size property. An extra 1% VOA for one team should represent the same increase in per-play dominance over their opponent as an extra 1% VOA represents for any other team in any other game. Otherwise, VOA won't work to compare raw performance in games and DVOA won't work to compare team quality.

The only way to accomplish that goal is to convert success points into VOA% using a factor that is proportional to the number of plays (in the game or season being judged) and no other factor.

The best divisor I can think of - it's the obvious one - is the number of plays in the game times the average baseline for all plays. In other words, the amount of success an average team playing against an average team with an average mix of situations would have had in the same number of plays.

That way you really could use VOA to compare raw performance, and DVOA to compare team quality. Every team, every game, every play would be graded on exactly the same scale.

Most of the time this hasn't been an issue, because the mix of situations in each game tends to be near some kind of "average" mix anyway. But every once and a while, DVOA coughs up a fur-ball. This inconsistent VOA scale could be a part of the problem. It may even be most of the problem.

Points: 0

#215 by nat // Dec 22, 2011 - 9:44am

If the previous post was too long to read, here's the short form...

Success points are all the same "size".
VOA percentage points should all be the same "size". (They aren't today.)
Use the average success for all plays in the database as the scaling factor.
VOA for a game or season will then be the average VOA for all the plays in the game or season, as it should be.

VOA would be improved for comparing teams' raw performance. DVOA would be improved for comparing teams' quality.

Points: 0

#216 by Vincent Verhei // Dec 22, 2011 - 12:09pm

So you do think that a third-and-2 conversion should have the same value as a third-and-20 conversion. Because they'd be worth the same number of Success Points, and what you're proposing sounds like a uniform baseline.

In fact, why bother with a baseline at all, then? Why not just use Success Points Per Play?

Points: 0

#217 by nat // Dec 22, 2011 - 1:16pm

Success Points Per Play wouldn't work because while Success Points are intended to be of equal value at the margin, there's nothing in the methodology that makes them have the same "zero point". A team's SP/P score would depend heavily on the situations they got into rather than their performance in those situations.

You could use Success Points over Baseline per Play (SPoB/P) to compare raw performance. But dividing by an average baseline instead of just the play count lets you quote a percentage, and thus to avoid have to indoctrinate everyone into the Success Point concept in detail.

Points: 0

#219 by Vincent Verhei // Dec 22, 2011 - 2:49pm

Success Points Per Play wouldn't work because while Success Points are intended to be of equal value at the margin, there's nothing in the methodology that makes them have the same "zero point".

But dividing by an average baseline instead of just the play count lets you quote a percentage, and thus to avoid have to indoctrinate everyone into the Success Point concept in detail.

I still don't understand what the difference is between these two, except that dividing by a uniform baseline average will result in a percentage. You'd still have the same teams ranked in the same order, by the same margins.

Points: 0

#220 by nat // Dec 22, 2011 - 3:41pm

Your quote skipped the important step: the difference between "Success Points" and "Success Points over Baseline". Note: "Over" here means "in excess of" and not "divided by".

Let's call them SPs and SPoBs.

SP/Play has the same "zero point" problem that SPs have.

SPoB/Play doesn't have a "zero point" problem, since it's measuring relative to a baseline. But it does end up being measured in Success Point units. That's fine for experts, but useless for most people. Most people don't understand or care what a success point is.

SPoB/(plays*average baseline in database) is as good as SPoB/Play, and puts all plays on an equal scale. It's effectively the same comparison, but converts it into units that make intuitive sense and are uniform: percentage of a typical play's success.

Using this approach, a +12% VOA would mean per play value "Above average by 12% of a typical play".

Points: 0

#221 by Vincent Verhei // Dec 22, 2011 - 3:54pm

OK. Followed most of that. One question: The "Baseline" in "SPoBs" -- would you have that be situation-specific, or use the league-average, all-situation baseline average?

Points: 0

#222 by nat // Dec 22, 2011 - 4:14pm

Great question!

Each play's success should be compared to the average or replacement-level success for that situation. That's what makes it adjust properly for situations.

But the league-average all-situation baseline should be applied as the scaling factor. That's what would make it valid for comparisons, and avoid the occasional truly weird VOA result.

All of this is "in my opinion" and "subject to off-season testing" etc. And all of this is targeted at making DVOA better, rather than complaining about any team's ranking.

Points: 0

#223 by dryheat // Dec 22, 2011 - 4:23pm

Oh my God...you nerds are still at this?

Points: 0

#224 by nat // Dec 22, 2011 - 8:17pm

Just about wrapped up for now. but thanks for asking.

Points: 0

#218 by nat // Dec 22, 2011 - 1:32pm

Your specific example just points out that the Success Point formula isn't perfect. (We knew that. Certainly for clock management situations, and perhaps for short or long yardage situations as your example suggests.) Compared to getting no gain in each situation, both of these plays get a new set of downs, but one of them improves field position more. They should be valued (a bit) differently.

But whatever the flaws in the Success Point formula, dividing by a per-play baseline isn't going to help. Nor is dividing by a per-game baseline.

Points: 0

#97 by Karl Cuba // Dec 20, 2011 - 1:46pm

"Stop trying to be funny, Vince. Know who you are.
Aww. Anyone agree/disagree with this? I liked it."

I think your writing has really improved this year and you are at least a bit funny.

Points: 0

#100 by Thomas_beardown // Dec 20, 2011 - 1:59pm

I enjoy Vince's comments and I think he's a huge upgrade on Barnwell.

Points: 0

#124 by Faint Praise (not verified) // Dec 20, 2011 - 2:34pm

This is me damning you.

Points: 0

#132 by bigtencrazy (not verified) // Dec 20, 2011 - 2:56pm

Strongly agree

Vince educates and shares.

Others.........did not.

HUGE change for the better.

Points: 0

#192 by BroncosGuyAgain // Dec 21, 2011 - 10:58am

Funny is in the eye of the beholder, so I wouldn't worry about one comment. I think you are doing a great job with this column and have set the tone properly.

Points: 0

#141 by MJK // Dec 20, 2011 - 3:12pm

His two-yard gain on second-and-1 was worth essentially zero DYAR. (It was actually a negative YAR play before we add in adjustments for playing the Broncos, whose run defense has been OK.)

Hmmm, I find this surprising. So, leaving out opponent adjustments, a 2 yard gain on 2nd-and-1 has a negative YAR? How high is the baseline for a 2nd-and-1 play? A negative YAR means that you expect a REPLACEMENT level quarterback to gain more than 2 yards on a sneak on 2nd and 1? Or just that you expect a replacement QB to gain more than 2 yards in some way, shape, or form? Given that most QBs either sneak the ball (generally gaining only a yard, if that) or attempt a pass, which probably falls incomplete a fair portion of the time, I'm surprised that the baseline for an average QB, let alone a REPLACEMENT QB, is more than 2 yards. Do we really expect Curtis Painter to consistently gain more than 2 yards on 2nd and 1?

I would buy that a replacement RB might have a higher expectation on 2nd and 1. I would also buy that a QB *might* have a higher expectation if you take both pass and rush attempts into account. But not that a QB rushing attempt would have that high of an expectation. Does YAR (and DYAR) take the ballcarrier's position into account when setting baseline, or just the scenario? Does it take the playcall into account? Are you claiming that Tom Brady didn't gain more yards then you would expect a replacement player of unspecified position to gain using any kind of play, or that Brady didn't gain more yards than you would expect a replacement QB to gain on a rush? Or something in the middle.

It seems counterintuitive to compare a rush by a QB to the expectations of a pass by a QB...it means that QB's that play for coaches that like to call safe, get-the-first-down-with-a-sneak-instead-of-trying-the-homerun-pass type of call will always end up with a worse DYAR. It also seems counterintuitive to compare a QB sneak to a designed run by a RB...obviously, your expectation for the RB will be higher.

Points: 0

#144 by Thomas_beardown // Dec 20, 2011 - 3:18pm

I think they expect a replacement level rusher to gain 2 yards on that play.

Points: 0

#181 by nat // Dec 20, 2011 - 10:18pm

I think the sneak is being compared to all designed runs for the QB, including bootlegs, draws, options plays and the like. I'm assuming Michael Vick is in the average somewhere. He's probably not just running sneaks. So perhaps gaining two yards is below replacement level as they calculate it. Especially when you consider that yard line and yards to go are always reported without any fractional part in the play-by-play.

Surprising. But not bonkers.

Points: 0

#150 by dryheat // Dec 20, 2011 - 4:10pm

It's just a weakness in calculating rushing DVOA for quarterbacks. Sneaks are essentially dives to get one yard, give or take a foot. The QB is usually going to the ground, forfeiting further yards. In these cases, if the QB gets the yard, he's gotten 100% of the yardage available on that play.

We all know this, so what to do about it? We could live with it, which isn't a major problem. Or somehow grade sneaks on a pass/fail basis....maybe treat them similar to the way DVOA treats runners getting a touchdown from a 1-yard plunge?

Points: 0

#183 by Vincent Verhei // Dec 21, 2011 - 12:16am

When quarterbacks run, they are compared to other quarterbacks who run. Yes, this means a Tom Brady sneak is compared to a Michael Vick scramble or a Cam Newton power dive play.

Points: 0

#187 by nat // Dec 21, 2011 - 9:07am

Shit. I forgot "undesigned" runs (scrambles). That makes QBs look like really good runners, since a scramble that loses yards isn't counted as a run, but as a pass play. Understandable. Problematic. But a hard nut to crack.

This would also explain the high replacement value for a goal-to-go-from-the-one QB running play. All scrambles from the one yard line score, by definition. If they don't score, they're not scrambles, and thus not counted as running plays.

Points: 0

#195 by MJK // Dec 21, 2011 - 12:57pm

Ah, yes. I see that this is a fundamental problem created by going off the official play-by-play and not charting data. Most negative QB runs are scored as "sacks" on the play-by-play, whereas any positive QB run (designed or undesigned) is scored as a rush. Hence the baseline for any QB rush is necessarily going to be very high...probably higher than for a RB.

So a coach by calling a sneak is automatically dooming his QB to a negative YAR play, even if it is the tactically correct thing to do.

This is going to grow to be an even bigger challenge if Cam Newton and Tim Tebow's successes cause the college option play to be seriously revived in the NFL. On an option, if the QB laterals it to the RB running behind/beside him, it's a rushing attempt by that back and won't affect the QB. If he passes it forward to the TE, it's a passing attempt. If the QB keeps the ball and is tackled for a loss, it will be recorded as a sack, I think, and hence not contribute to the rushing YAR baseline? If he keeps it and gains yards, he gets positive yards for rushing, pulling the YAR baseline up.

Points: 0

#196 by Thomas_beardown // Dec 21, 2011 - 1:00pm

It might cause weird splits for passing/rushing YAR, but the over all YAR should still do as good of a job as it was.

Well except QBs won't get any credit for pitching it on an option.

Points: 0

#87 by Raiderjoe // Dec 20, 2011 - 1:21pm

Andre roberts ztrArting to burst out

Points: 0

#90 by Vincent Verhei // Dec 20, 2011 - 1:29pm

It's a sign that DVOA has problems judging short yardage situations, and deep problems when clock management becomes important.

I disagree with your first point, but agree 100% on the second. Aside from wiping kneeldowns and clock-kill spikes off the record, there is no clock management variable in DVOA. We've never said there was.

Remember last week, when Marion Barber failed to stay in bounds on a 5-yard run against Denver, stopping the clock and giving the Tebows enough time to rally and win? That was a (barely) positive play in DYAR. Check the Audibles for that day, though, we ripped Barber for his dumb play. DVOA has flaws. We acknowledge that.

Points: 0

#98 by nat // Dec 20, 2011 - 1:47pm

I never said you never said....

It's okay that DVOA has flaws. It is, and should be, a work in progress. Although I harp on its flaws because I want to see DVOA improved, I appreciate what DVOA does: The focus on play-by-play results, the comparison to average, the non-linear value of yards gained, the value assigned to turnovers, the emphasis on repeatable skills... the list goes on.

I could be wrong about short yardage. Or there might be a problem in the huge step in value between 0 and 1 yard on first-and-goal from the one, and a problem with the huge baseline of such a play diluting the value of all other plays.

Points: 0

#146 by Jimmy // Dec 20, 2011 - 3:19pm

Couldn't you add an adjustment for a play when someone blows a chance to ice the game?

Points: 0

#110 by Maltodextrin (not verified) // Dec 20, 2011 - 2:12pm

On fourth-and-1 from the Detroit 24 in the first quarter, Palmer threw incomplete to Denarius Moore into the end zone. Given the game's final margin, the Raiders probably regret that playcall.

But Moore was wide open. Palmer overthrew him. That's not a reason to regret the playcall. It was a perfect playcall, bad execution.

Points: 0

#122 by zlionsfan // Dec 20, 2011 - 2:29pm

Agreed. It was a great call: fourth-and-one is an aggressive down, and with Detroit's success against short-yardage plays, something other than a run was a great idea. (I say that as a fan of strategy, not as a Detroit fan. My reaction to the play live was "oh, ****", which means it was a good call.)

Points: 0

#134 by Aaron Brooks G… // Dec 20, 2011 - 2:56pm

You're still arguing a performance-based evaluation, and not a method one.

Moore was wide open as much because Detroit performed poorly on the play, but Oakland had no way going into the play to know that. You're couching your argument as the playcall being good because Moore performed well. Vince isn't arguing that the playcall was bad because Palmer performed poorly, but because in the end-game situation, the difference between 0 pts and 3 pts was worth more than the difference between 3 points and 7 points, and despite volume-averaging of probability, scores still have discreet values.

Points: 0

#157 by LionInAZ (not verified) // Dec 20, 2011 - 5:26pm

I think there's a psychological factor as well. The Raiders were struggling to score points the previous three weeks. Their defense is suspect. They're facing a team that can go downfield and score in a hurry. You want to put them in a hole so that they're forced to eliminate some calls from the playbook. If you're up against a ponderous team like the Broncos or Titans, you'd probably go for the FG. But if you're up against the Saints or the Pats, you want every TD you can get, and you want to get them early because it's harder for you to play from behind than them.

Points: 0

#118 by zlionsfan // Dec 20, 2011 - 2:21pm

I think this was an accurate assessment of Stafford's season. (We might as well call it his "career", considering that it's been so different than his first two seasons. At worst, he's had little, nagging injuries that a lot of QBs get, but nothing like 2009 or 2010.) He's shown the ability to put points on the board in a hurry against defenses that are average or worse; against better defenses, his success is spotty at best.

I don't think it's a coincidence that the Lions are just 2-4 against current playoff teams, and both wins came against teams of questionable quality that haven't locked down playoff spots yet. Detroit has done a good job cleaning up against weaker teams (just one loss, and that was to good Chicago), but they've yet to demonstrate they can play at the same level against better teams. Too many mental mistakes (more than a few by Stafford himself) took away any chance they had of beating those better teams.

9-5 is certainly a pleasant change from everything that happened since Millen destroyed the team, but I've no illusions about what it means. After all, I remember a 12-4 team that arguably wasn't much better than this one ... hopefully the DVOA era will eventually extend back that far. The Lions that season still had trouble against quality opposition, getting blown out twice by the Redskins (although Barry missed the first meeting).

It didn't matter too much, though. When your expectations are perennially low, even a taste of success is enough for the moment. Following up 0-16 and 2-14 with 6-10 and then maybe 10-6 would be just fine ... a wild-card win would be even better, but even if it's a playoff loss, there is, for a change, hope for the future.

Points: 0

#145 by Aaron Brooks G… // Dec 20, 2011 - 3:18pm

Stafford had a putrid game @CHI (Cutler version) and poor ones against GB and @Atl.
He was decent home against CHI (Cutler version). The 2nd Chicago and GB games were played with a broken finger.

He played well against SF, Dallas, NO, and lit up a decent Denver defense. He's been more betrayed by a complete absence of a rushing attack in his losses. Probably because the Lions are down to their #4 RB and a street FA.

That 1991 team went 4-4 against teams with 10 or more wins and 9-1 against teams with 9 or fewer wins. There's no shame in the 1991 49ers or 1991 Redskins having your number.

Points: 0

#154 by Independent George // Dec 20, 2011 - 5:06pm

I haven't seen many Lions games this season, but it still looks to me like Calvin Johnson has a bigger impact on the offense than Stafford. I know it's by design, but it looks like there are at least 4-5 plays per game where he flings it up in the air and waits for Megatron to bring it in. It's reminiscent of Randy Moss in Minnesota.

Points: 0

#155 by Thomas_beardown // Dec 20, 2011 - 5:14pm

It's not just CJ, though he is the best, all the Lions receivers are big and tall and Stafford throws high all the time. It's hard to tell if this is an Eli-esque accuracy issue or if intends to do this every time.

It does mean that a really disciplined secondary has a solid shot at breaking those up, but it also leads a lot of CJ jumping over 4 guys for a TD.

I think it also simplifies things for Stafford.

Points: 0

#162 by LionInAZ (not verified) // Dec 20, 2011 - 6:01pm

CJ and Stafford practice those plays a lot. I think they've been doing it with Burleson too, but Stafford, CJ, and Pettigrew have had the most time playing together, so it makes some sense that they've worked together better.

Points: 0

#161 by LionInAZ (not verified) // Dec 20, 2011 - 5:57pm

It's also easy to underestimate the impact that Jahvid Best had on the passing game.
He was enough of a threat to break a long play on outlets that defenses could not afford to over-commit to covering CJ. It's been up to the TEs to make up for that, with mixed results.

Points: 0

#165 by Aaron Brooks G… // Dec 20, 2011 - 6:39pm

Johnson has a large effect, but the plays Johnson makes when Stafford is in are very different than the ones when Hill or Stanton are in.

Stafford throws those high bombs because CJ can catch them, not because he just throws high bombs. Hill and Stanton just can't make those throws.

Points: 0

#169 by LionInAZ (not verified) // Dec 20, 2011 - 7:19pm

To be fair, Shaun Hill made those throws a few times for TDs from within the 30 yard line last year (at least once against the Packers IIRC).

Stanton, on the other hand, has always been too erratic a passer to trust on that kind of play.

Points: 0

#168 by greybeard // Dec 20, 2011 - 7:12pm

Regardless of whatever his numbers were, he did not play well agains 49ers.

I watched a few Detroit games this year and Stafford has play is above average QB play. But, IMO, if you were to replace Megatron with a league average #1 WR, Stafford would not have looked good. Or if you were to replace Stafford with Shaun Hill the drop off would not be that big.

Points: 0

#170 by LionInAZ (not verified) // Dec 20, 2011 - 7:22pm

Talk all you want, he played a hell of a lot better than Alex Smith.

Points: 0

#174 by greybeard // Dec 20, 2011 - 8:59pm

I watched all of the games Alex Smith played and 4 games Stafford played this year Chi, SF, GB, Oakland.Alex Smith has played better overall IMO. Especially given the huge difference between their #1 WRs and their OLine quality I would say Alex Smith played head and shoulders above from Stafford.

Points: 0

#159 by LionInAZ (not verified) // Dec 20, 2011 - 5:45pm

I agree, this was an informative read and demonstrated some of the obvious shortcomings we've seen through the season (such as 3rd down performance).

It's hard to say how much of an impact the broken index finger has had on Stafford's play in the middle of the season. No one will ever admit that it affected his play.

The other factor is that he's only 23 years old, and he has played considerably fewer games than any of the other QBs listed above. I think it's fair to say that he hasn't peaked yet. Even small improvements in the running game and O-line performance would help a lot.

It's just very gratifying right now to have a QB who could even be considered in the top ten and could very well turn out to be the best QB in the history of the Lions team.

Points: 0

#125 by ASmitty // Dec 20, 2011 - 2:42pm

"Stafford won the game with two late touchdown drives, but his "clutch" performance (fourth quarter, within one score) wasn't as good as you'd expect: 7-of-12 for 96 yards, six first downs, one touchdown, plus a 17-yard DPI."

Uh. Part of what made his fourth quarter "clutch" was because, as you noted, he nedded two drives to win it: one to get within a score, and the other to take the lead.

Now, granted, they were down two scores because he was stripped for a touchdown, but still, the sentence as written makes little sense. It's like saying "Stafford won the game with two late touchdown drives, but if you take one of them out, his numbers aren't as good."

Points: 0

#171 by LionInAZ (not verified) // Dec 20, 2011 - 7:25pm

I think they're saying that a 'clutch' performance would have looked more like 10-12 passing without a big DPI call to help things along.

I don't care because the Lions won anyway.

Points: 0

#126 by Biebs // Dec 20, 2011 - 2:42pm

I'm curious as to how different Sanchez's numbers would have been if Holmes caught the pass in the red zone, instead of tipping the ball and it getting picked off.

I understand that tipped passes are a part of life for the QB. But I suspect that int in the red zone pushed sanchez numbers WAY down

Points: 0

#163 by BroncFan07 // Dec 20, 2011 - 6:21pm

"Orton threw seven passes in the fourth quarter, each while protecting a one-score lead. He went 5-for-7 for 86 yards and four first downs. Of course, he may have been ahead by more than one score if he hadn't gone 1-of-6 for 8 yards and no first downs in the red zone."

Yep, that's a Completely Competent Kyle Orton* kind of day if I ever saw one. 299 yds passing, 1 total TD, 4 FGs. No one is better between the 20s.

*Copyright V. Verhei

Points: 0

#184 by Bryan and Vinny Show (not verified) // Dec 21, 2011 - 12:35am

Yep. I liked Orton well enough here in Denver, but, sweet cripes, whenever they would get the ball inside the red zone, he was always dreadful. I don't know what the problem is.
At least with Tebow, he'll eventually just tuck the ball away and run toward the end zone. He may not get in, but there's usually at least some sort of progress.

Points: 0

#204 by TreeRol (not verified) // Dec 21, 2011 - 3:37pm

I'm not sure I get the point of assists. A QB who throws a 15-yard pass that is caught with 0 YAC is credited the same as a QB who throws a 2-yard pass that is caught and followed by 13 YAC. He gets the completion, he gets the yards, and he gets the first down or touchdown. But in the latter case he gets an "assist."

Want to lead the league in assists? Throw a lot of screens. Sure, the OL does all the work, but it's another stat that goes to the QB.

Seems like it could be a useful way to characterize an offense, but why is this a stat for the QB?

Points: 0

#207 by Vincent Verhei // Dec 21, 2011 - 3:50pm

It has some descriptive value, about the style of the QB and his offense. I would never say that more assists = better. I would say that more assists = different.

Points: 0

Save 10%
& Support Vincent
Support Football Outsiders' independent media and Vincent Verhei. Use promo code VINCE to save 10% on any FO+ membership and give half the cost of your membership to tip Vincent.