<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Mo Minutes, Mo Production</title>
	<atom:link href="http://basketball.razzball.com/mo-minutes-mo-production/feed" rel="self" type="application/rss+xml" />
	<link>http://basketball.razzball.com/mo-minutes-mo-production?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=mo-minutes-mo-production</link>
	<description>Fantasy Basketball Advice</description>
	<lastBuildDate>Fri, 17 May 2013 19:12:28 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.5.1</generator>
	<item>
		<title>By: Fenris-77</title>
		<link>http://basketball.razzball.com/mo-minutes-mo-production#comment-157151</link>
		<dc:creator>Fenris-77</dc:creator>
		<pubDate>Sat, 16 Jun 2012 01:41:22 +0000</pubDate>
		<guid isPermaLink="false">http://basketball.razzball.com/?p=4056#comment-157151</guid>
		<description><![CDATA[For player movement analysis it&#039;s invaluable. (for those of us geeky enough to look it up).

I used it pretty much all the time though. What that does is give me a firmer baseline to fall back on mentally, since the numbers are consistent from player to player across teams. It makes it easier to look at stat X and locate it in the matrix of other players in a given tier or in general. Player eval at more-of-a-glance is what I&#039;m pointing too I suppose. Obviously I look at the straight per-36 too, but the pace adjusted metrics are useful beyond just inter-team comparison shopping.

Another point I thought I&#039;d make, since you&#039;re pointing at USG% anway, is that looking at Offensive Rating (ORat) set next to USG% is even more useful. ORat (for those of you following along at home) is a player efficiency metric (like PER kinda, but offense only). Being able to set efficiency next to USG% gives us a really good picture of where a player might have room for growth. 

Guys with high ORats can more often sustain an increase in USG% without crapping the bed. Not everyone obviously, as there are lots of players who&#039;s game and skill set is specifically high efficiency/low USG%. Even those guys tbhough, often bigs , have a more predictable transition to starting roles in many cases. Gortat is the poster boy there, but there are lots of examples.

The best part is that Basketball Reference lists ORat right next to USG%, so it&#039;s an easy once glance thing either way.]]></description>
		<content:encoded><![CDATA[<p>For player movement analysis it&#8217;s invaluable. (for those of us geeky enough to look it up).</p>
<p>I used it pretty much all the time though. What that does is give me a firmer baseline to fall back on mentally, since the numbers are consistent from player to player across teams. It makes it easier to look at stat X and locate it in the matrix of other players in a given tier or in general. Player eval at more-of-a-glance is what I&#8217;m pointing too I suppose. Obviously I look at the straight per-36 too, but the pace adjusted metrics are useful beyond just inter-team comparison shopping.</p>
<p>Another point I thought I&#8217;d make, since you&#8217;re pointing at USG% anway, is that looking at Offensive Rating (ORat) set next to USG% is even more useful. ORat (for those of you following along at home) is a player efficiency metric (like PER kinda, but offense only). Being able to set efficiency next to USG% gives us a really good picture of where a player might have room for growth. </p>
<p>Guys with high ORats can more often sustain an increase in USG% without crapping the bed. Not everyone obviously, as there are lots of players who&#8217;s game and skill set is specifically high efficiency/low USG%. Even those guys tbhough, often bigs , have a more predictable transition to starting roles in many cases. Gortat is the poster boy there, but there are lots of examples.</p>
<p>The best part is that Basketball Reference lists ORat right next to USG%, so it&#8217;s an easy once glance thing either way.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JashFath</title>
		<link>http://basketball.razzball.com/mo-minutes-mo-production#comment-156874</link>
		<dc:creator>JashFath</dc:creator>
		<pubDate>Fri, 15 Jun 2012 07:54:25 +0000</pubDate>
		<guid isPermaLink="false">http://basketball.razzball.com/?p=4056#comment-156874</guid>
		<description><![CDATA[@Fenris-77, Very true, pace plays a large role when comparing players. This post was more wired towards the evaluation of bench players and undervalued starters. When targeting players to trade for, you definitely want to consider pace. A player on the run-n-gun Suns will have better looking projections than a player on the half-court Celtics, which could be misleading if you don&#039;t account for the different types of offenses.]]></description>
		<content:encoded><![CDATA[<p>@Fenris-77, Very true, pace plays a large role when comparing players. This post was more wired towards the evaluation of bench players and undervalued starters. When targeting players to trade for, you definitely want to consider pace. A player on the run-n-gun Suns will have better looking projections than a player on the half-court Celtics, which could be misleading if you don&#8217;t account for the different types of offenses.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Fenris-77</title>
		<link>http://basketball.razzball.com/mo-minutes-mo-production#comment-156717</link>
		<dc:creator>Fenris-77</dc:creator>
		<pubDate>Thu, 14 Jun 2012 23:04:03 +0000</pubDate>
		<guid isPermaLink="false">http://basketball.razzball.com/?p=4056#comment-156717</guid>
		<description><![CDATA[I prefer pace adjusted Per-36 to the out-of-the-box version. I like taking out the pace bias, especially from those fast teams. Pace adjusted metrics are also a lot more useful more comparing players from different teams.]]></description>
		<content:encoded><![CDATA[<p>I prefer pace adjusted Per-36 to the out-of-the-box version. I like taking out the pace bias, especially from those fast teams. Pace adjusted metrics are also a lot more useful more comparing players from different teams.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
