web analytics

With or Without You: OKC and Nick Collison

January 7, 2011
By

The concept of With-or-Without-You is very basic. If you are playing, is our team better or worse? If the team is worse with you available, then that’s a really bad sign! It’s the core concept behind such basketball metrics as +/-, Statistical Plus/Minus and Advanced Plus/Minus. In baseball, Tom Tango and MGL work with it a lot.

At its basic level, however, we can just look at games when a player was hurt or otherwise out. How did the team fare? With starting PF Jeff Green out, do the Thunder collapse? How about key backup PF/C Nick Collison? As a Thunder fan, I have followed the dialogue amongst the fans as they ponder the defense and the role of the post players. (Mostly on DailyThunder.com–good job, Royce & Co.!)

Yesterday, Hickory High took a look at what Nick Collison is doing. I’m going to look at this subject again, and expand to include all of the key Oklahoma City Thunder players that have missed time.

First of all, I’ll bring in OKC’s team chart, to illustrate how their season has gone. Again, these team charts are adjusted for opponent, rest days, and location, to provide a clear view of how well the team played compared to NBA average.

Team Game Chart OKC

OKC's Team Game Chart for this season

Next, let’s see who was missing for each game, and how the team did on offense, defense, and overall. The data will be in a table at the end of this post for copying.

With-or-Without You OKC

OKC's game performances, and who was missing

So what do we see?  Well, OKC’s defense was worse with Nick Collison out.  OKC played well with Jeff Green missing, and with Nenad Krstic missing.  And their offense is bad without KD.

To further isolate the effects, I ran a regression to predict how well the team would play on offense, defense, and overall, based on who was playing in the game and who was not.  The results are pretty impressive:

Player Point Differential Offense Defense
Kevin Durant 5.3 9.5 4.2
Jeff Green -10.9 -9.1 1.7
Nenad Krstic -3.7 -2.4 1.3
Nick Collison 7.3 1.9 -5.4

First: negative is good for defense; positive is good for offense and overall.

Next: Wow! Collison can play some D!  And…  Jeff Green hasn’t been very good.  He seems to kill the offense (probably because of his 52% TS%, 4.3% ORB%, and 8.7% AST%, all of which are rather low).  Kevin Durant seems to kill the defense, but he sure can light a fire under the offense!

Of course, this is a very small sample size, but it does serve to highlight the very things OKC fans have been noticing this year: Nick has been very valuable, in fact the most valuable of the 4 players who have missed games.  And yes, OKC fans, the Thunder has played better with both Jeff Green and Nenad Krstic out.  (That would imply that more minutes for Serge Ibaka would be a good thing, no?)

Overall, OKC with everyone playing has been about +1, or 1 point above average per 100 possessions.  That’s rather mediocre; about a 44-win team.  However, OKC has played to the level of their competition quite a bit, so they have won more games than one would expect.  It appears that the team has quite a bit of upside to exploit, with changes to player roles and rotations a prime area to look at.

As promised, the data table in copyable form:

GmGameAdj OEAdj DEAdj Eff MarWinOut
110/27/10 vs. CHI6.9-5.312.2WNC
210/29/10 @ DET3.14.3-1.2WNC
310/31/10 vs. UTA-11.011.3-22.3LNC
411/03/10 @ LAC-10.37.5-17.8LNC
511/04/10 @ POR11.75.16.7WNC
611/07/10 vs. BOS-6.1-2.8-3.3LJG NC
711/10/10 vs. PHI6.92.94.0WJG NC
811/12/10 vs. POR19.920.4-0.5WJG NC
911/14/10 vs. SAS-4.57.8-12.3L
1011/15/10 @ UTA25.49.615.8WJG
1111/17/10 vs. HOU12.7-1.514.2WJG
1211/19/10 @ BOS2.9-14.517.4WKD JG
1311/20/10 @ MIL-9.8-12.52.8WKD JG
1411/22/10 vs. MIN5.31.83.5W
1511/24/10 vs. DAL2.913.1-10.2L
1611/26/10 @ IND4.61.33.4WNK
1711/28/10 @ HOU8.46.12.2LNK
1811/29/10 vs. NOH-6.4-11.24.8W
1912/01/10 @ NJN-0.51.7-2.2WKD
2012/03/10 @ TOR-5.18.4-13.5LKD
2112/05/10 vs. GSW5.47.6-2.2WNC
2212/06/10 @ CHI-1.2-0.3-0.9L
2312/08/10 @ MIN4.7-4.89.5W
2412/10/10 @ NOH5.3-5.210.5WNK
2512/12/10 vs. CLE4.4-11.716.1WNK
2612/15/10 vs. HOU14.86.68.2WNK
2712/17/10 vs. SAC-1.0-2.21.2WNK
2812/19/10 vs. PHO2.610.4-7.8LNK
2912/21/10 @ CHA4.9-10.615.5WNK
3012/22/10 @ NYK-5.91.7-7.6LNK
3112/25/10 vs. DEN10.43.56.9W
3212/27/10 vs. DAL-7.97.6-15.5L
3312/29/10 vs. NJN7.5-5.212.8W
3412/31/10 vs. ATL6.0-3.19.1W
3501/01/11 @ SAS-26.0-13.2-12.8L
3601/04/11 @ MEM5.17.1-2.1L
3701/06/11 @ DAL11.3-1.512.7W
Share

Tags: , , , , ,

4 Responses to With or Without You: OKC and Nick Collison

  1. Sammy on January 7, 2011 at 1:24 pm

    Cool beans, DSMok1! Thanks for the work, and thanks especially for the new blog.

  2. DanielM on January 7, 2011 at 1:26 pm

    Thanks, Sammy!

  3. Crow on January 7, 2011 at 3:37 pm

    Is your regression essentially Adjusted +/- at game level instead of play level? There obviously is going to be some loss of precision going from play level tracking of impact to game level summary.

    Did you adjust for overall season level quality of team faced or not? (Also adjusting for who is out for the opponents would be a possible refinement, if not already done.)

    I think there is some merit to this type of effort. I had previously talked years ago about some type of team specific re-runs of Adjusted +/- to try to optimize within team ratings more than that achieved by a broad league level rating effort of all players within and between teams.

    • DanielM on January 7, 2011 at 4:07 pm

      I started with the completely adjusted game efficiencies–adjusted for opponent, rest, and location. So yes, this is fully adjusted for opponent.

      Then, I just looked at how good the team did with or without the player. OKC was 7.3 points per 100 possessions better with Nick Collison available.

      So this isn’t Adjusted +/-. This is more analogous to VORP, because it’s not per possession, but rather gives a point value to overall value to the team, per team possession. It’s also not relative to league average. It’s just “With or Without You”.

      Sure, granularity is given up. But since the goal is the team level impact, anyway, we gain by not having to translate from individual impact to team impact.

Leave a Reply

Your email address will not be published. Required fields are marked *

DSMok1 on Twitter

To-Do List

  1. Salary and contract value discussions and charts
  2. Multi-year APM/RAPM with aging incorporated
  3. Revise ASPM based on multi-year RAPM with aging
  4. ASPM within-year stability/cross validation
  5. Historical ASPM Tableau visualizations
  6. Create Excel VBA recursive web scraping tutorial
  7. Comparison of residual exponents for rankings
  8. Comparison of various "value metrics" ability to "explain" wins
  9. Publication of spreadsheets used
  10. Work on using Bayesian priors in Adjusted +/-
  11. Work on K-Means clustering for player categorization
  12. Learn ridge regression
  13. Temporally locally-weighted rankings
  14. WOWY as validation of replacement level
  15. Revise ASPM with latest RAPM data
  16. Conversion of ASPM to" wins"
  17. Lineup Bayesian APM
  18. Lineup RAPM
  19. Learn SQL