A Little Bit of Perspective, Folks
I’ve tried to read as much as possible on the board since the Wisconsin game. Due to those pesky things like “work” and “having a life,” I haven’t been able to read everything. But I’ve seen enough to be really disappointed and frustrated with much of what’s going on. It’s also enough to make me concerned about what will happen the next time Duke loses, because I think we can all agree that Duke – and everyone else in the country – will probably lose again this season.
What’s missing from some – not all, but some – of the posts is perspective. But it’s not just one kind of perspective. It’s historical perspective. It’s mathematical perspective. It’s plain old basketball perspective. I realize there’s always a healthy influx of new posters with each new season, and I know that losses tend to both bring some of those people out of the woodwork, in addition to bringing out the worst in other people. But this isn’t just an issue with new posters. It’s a mix. And while I’ve read a lot of stuff I respect, I really think this board is in trouble if we can’t dial down the tone and pump up the knowledge a bit.
I’d like to help, if you’ll indulge me for a longish post.
The biggest issue, among many, is the number of people who are drawing broad, sweeping conclusions based on one loss to a solid team in a really tough environment during the month of December. I hope, as the initial sting wears off, you can recognize things that are overreactions. If not, let’s start this way:
Historical Perspective
Two years ago, in the Big Ten/ACC Challenge, Duke destroyed Wisconsin in Cameron by 24 points in a game that wasn’t even that close. It came on the heels of the Maui Invitational title, made Duke 7-0 and left everyone here thinking big. And Wisconsin? Well, after watching them play that game, it was hard to imagine their even finishing in the top half of the Big Ten.
Wisconsin ended up reaching the Sweet 16 that season. Duke lost in the second round.
Clearly, it was wrong to jump to major conclusions after that game. So it should make even less sense to make declarative statements after a close loss at Wisconsin, right? Right?
If that’s not enough, look back to some of Duke’s best teams from this decade, like the 2003-04 team that lost to Purdue in Alaska, or the 2001-02 squad, which began January with a loss at a weak Florida State team. You can only tell so much from early-season games, and you really can tell very little from one early-season game. Why?
Mathematical Perspective
One game in basketball isn’t close to a representative sample size. I don't even think it's representative in football, so it certainly is not in hoops. I think we’d all know that if Derek Jeter were to go 0-for-4 in a game in May, including three strikeouts on sliders down and away, that we couldn’t conclude that Jeter can’t hit a slider. Those of you who are NBA fans would know implicitly that the Suns’ losing to the Knicks two nights ago doesn’t mean much, or that Shane Battier can still guard athletic wings even after Al Thornton went for 19 on him last night or that Amare Stoudemire can score against elite teams, despite his 5-for-14 shooting against the Cavs. Nor, for that matter, would anyone judge Blake Griffin’s NBA future based on 10 minutes of playing time in his first game back from injury.
Yet, when it comes to Duke, that’s exactly what’s going on. I know the college season is significantly shorter than that of the NBA, and I know it concludes with a one-and-done tournament. But that still doesn’t make one game a representative sample size. Just as Lance Thomas wasn’t a nightly double-double because he played great UConn, he shouldn’t/won’t fall out of the rotation based on how he looked against Wisconsin. Just because Jon Scheyer looked out of sync against Wisconsin doesn’t mean he struggles against small, quick guards; not with mountains of evidence to the contrary, including the most recent game against UConn, last year’s matchups against Ty Lawson and Toney Douglas, etc. And judging Mason Plumlee, a freshman, in his first game back from a month-long injury? Come on. And if the concept of sample size doesn’t work for you, just consider this avenue instead:
Basketball Perspective
Most of you have played the game, right? Even if you didn’t play in high school, you’ve probably played pickup ball. You know that sometimes you have it, and sometimes you don’t. Sometimes that friend of yours who is slow and small and not even worth guarding hits everything he chucks at the rim. Sometimes you can’t get your go-to move to drop. Well guess what? Elite-level players aren’t immune to the vagaries of a game based on a lot of randomness, either.
I went through a bit of the post-game threads from both the Wisconsin and UConn games. And in addition to being struck by the different crowds the two games drew in terms of posters who only replied to one or the other, I was even more interested to find the contradictory comments from a variety of posters, reacting totally differently after games that were separated by less than a week.
I don’t want to single people out, because there were tons of examples that fit what I said above. But, for instance, here’s what one person wrote after the Wisconsin game:
“I can't agree with the generally upbeat reaction here. We played horrible defense, and it seemed clearly to be poor play by us more than great play by them. The Badgers were patient (and many teams we'll play couldn't match them in this respect in a million years) however, we always delivered a path to the basket. We had a whole game to fix it, and did not. Both Plumlees and Dawkins appeared tonight to be not ready for big time defense. Very discouraging.”
Here’s what the same person wrote after the UConn game:
“We made UCONN look like a not very good team. We literally imposed our will on them, and did it without much offense, without scoring from Singler, and with no help from the Zebras (the third foul on Plumlee was the worst call I have every seen, anywhere, anytime). This is exactly the kind of poor shooting that has led to a Duke loss in non-conference games recently, particularly in the NCAAs. Not so tonight, and likely not so this season. This is really something to build on.”
It’s so easy to fly high after a big win and sink low after a tough loss. But, again, it doesn’t mean we should be jumping to conclusions in either situation. The above examples are tame compared to what was written after both games, which is actually why I picked them – no need to highlight some of the more extreme stuff written after last night.
Many people were pumped about Zoubek and Thomas after the showing against UConn. Now, many people (including some of the same people), don’t think they’re rotation-worthy. The truth, as always is probably somewhere in between.
What’s worse is the people making declarations that Duke “can’t win a championship” because of X, Y and Z that were on display last night.
Fact: This team is not close to fully developed.
Fact: Two freshmen are among Duke’s top seven players.
Fact: The team is still installing a new offense.
Fact: We’ve seen enough of Jon Scheyer over four seasons – including against teams much better than Wisconsin – to know that his performance last night was a complete aberration.
Fact: We’ve seen enough of Nolan Smith to know he’s better than he played against Wisconsin, too.
So those are just a few reasons, from a basketball perspective, to avoid viewing last night’s game as a proxy for March. But what’s even worse are statements like (and I’m paraphrasing a bit):
“Once again, Duke is a jump-shooting team, and we won’t win that way. In fact, that means another early-round flameout.”
“Coach K won’t play his bench enough and that will cost us in big games down the stretch.”
And, of course, “We can’t win with [Insert big man].”
Those are result-oriented fallacies, driven purely by the most recent thing we saw. Because, clearly Duke CAN beat a good team with its bigs, which we saw against UConn. Duke CAN win with a short bench late in the season, which we saw in the ACC Tourney last year, during three championship seasons, etc. Duke ISN’T just a jump-shooting team, which we also saw against UConn.
And that’s to say nothing of all the people who said “Andre Dawkins should have played more in the second half,” without realizing that he was on the floor for the final 16-plus minutes (and responsible for several of the defensive breakdowns, I might add). Or the people who ranted about Duke going away form the zone, without recognizing that we had trouble rebounding out of it and that the man-to-man D was actually better late in the game, and that Wisconsin just hit some tough shots. Or many of the other details people missed under a cloud of emotion.
Look, there are plenty of things to criticize after the loss. Duke didn’t execute its end-game scenarios well. The bigs didn’t play well in that game. Nolan needs to do a better job of kicking when he drives; that’s been evident in multiple games. Duke needs to integrate Mason Plumlee and have him reach his own potential for the team to reach its full potential. But any weakness that Duke displayed last night can be corrected. It just takes a bit of vision and a dose of faith.
And, finally, there is no clear recipe for a championship team. March involves a lot of things – including luck. If anyone tries to tell you that a team has to have a go-to scorer in the post to win it all, he/she is wrong. Just luck at the UConn team that beat us in 1999 – Jake Voskuhl wasn’t exactly the type of guy you run stuff through in the post. If anyone tries to tell you that a team needs an NBA-caliber, break-you-down point guard to win it all, he/she is wrong, too. Look at Syracuse in 2003. Or UConn in 2004 (Taliek Brown? Really?) Or even Taurean Green on Florida’s back-to-back champs. And if anyone tries to tell that this Duke team definitively can’t win a championship, he/she is wrong, too. We’re not the favorite, but as DBR has been fond of saying for more than a decade, the odds are against everyone. We have weaknesses, but we also have legit strengths that will enable us to beat anyone on the right day.
We can't keep doing this around here. We can't keep coming down so hard after every single loss. We can't become so emotionally invested that we lose sight of why we enjoy Duke basketball so much and only focus on what's wrong. We can't feel compelled to voice every frustration that pops into our head.
I know it’s tougher to see the good stuff and the potential of this team, or any team, after a loss. But sometimes you just need to take a step back to regain a sense of perspective.
Another way to look at the issue...
I agree with Jumbo's comments. Another way to look at the Wisconsin game to put things in perspective is to suppose that on our next to the last play Singler had made his running layup and been fouled in the act, making the foul shot to put us up by 1 with about 5 seconds left. Although this didn't happen, it certainly isn't an unreasonable outcome of the play. We would then very likely have won the game. How would that 1 slightly altered outcome of 1 shot have altered the response to the game. Would the sky still be falling on the season? Or would we be celebrating a great comeback and win over a tough team and declaring our team ready for the final 4? The success of that one shot certainly doesn't change how we played the previous 39:55 minutes of the game, but I believe it certainly would have changed many of our responses to it. As Jumbo points out, based on 1 game and certainly based on 1 shot from the end of the game it isn't fair to conclude either the best or the worst about this year's team.
No idea which "side" of this argument I fall into, but
I'll just offer my perspective. I am one of the posters who felt strongly that Wednesday's game was more of an indication of a trend than just one event.
I, for instance, even wrote a post that said that Wisconsin played a great game and I was not so much worried that we lost this game. I was more concerned that we didn't use it as an opportunity to grow toward the goal of a great team at the end of this year.
Instead of using a motion offense and getting the ball inside, we resorted to a dribble/drive offense with a bunch of one-on-one garbage when the game got close. My point, and the point I think many others agree with, is that if we resort to that type of play in a game in December when there is very little meaning for the overall outcome of the season, it is unlikely we will have the ability to stick to our game plan later when we are in a close game.
I also pointed out that we need to make a conscious effort to feed the post and give Miles (and Mason when the time comes) chances to succeed (and fail) so they learn what can and will work in the future. My posts happen to have come after a loss, but I (and I am sure many others) have been thinking these things even in the wins this year. I agree with the point that it might be better to discuss these things when people are less fired up over a loss.
I wouldn't changed out (in?) Dawkins as a starter because we have our 1-3 spots being filled by our best players. It might be interesting to separate Nolan and Scheyer at times (while Dawkins is in) just to give the opposition a different look, but I still think our 1-3 is the best we have, even if they didn't play well on Wednesday. That different look would be the threat of a (JJ-esque) shooter coming off screens all over the court and making his man trail him on defense. Making a guy work that hard on defense to trail a shooter of screens is great for the other four guys even if he never gets a shot off. However, the fact that Dawkins was in for the last 16 minutes of the game and people can say, "He should have played more," only indicates the issue with his current level of play. He didn't make his present felt for 12 of the 16 minutes he was in. We didn't even know he was on the court. Part of that is the fault of our dribble/drive one-on-one garbage and poor ball movement. The other part is that he wasn't making any plays of note (rebounding, defensive, etc). If he can go unnoticed that long, he probably doesn't need more playing time. He just needs to be used effectively when he is in the game (maybe like the senario I offered, maybe another way).
Lastly, I did not agree that our defense was "horrible." I though Hughes made a bunch of shots he never makes. I thought their big guys made a lot of threes that we could not have expected. When a team shoots like that, it is almost impossible to guard them. The only issue I had with our defense was our perimeter guys letting their guys get into the lane so easily. Again, though, that might have been a reaction to Wisconsin's incredible outside shooting. I thought Nolan, who is a leader for us on defense, was particularly suspect. I know everyone says Dawkins has defensive lapses, but his do not stand out to me nearly as much as Nolan's did on Wednesday. To clarify, I am not saying Nolan isn't a good defender, just that he had a bad game.