<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Talent Alley &#187; James Krouse</title>
	<atom:link href="http://talentalley.com/author/james-krouse/feed/" rel="self" type="application/rss+xml" />
	<link>http://talentalley.com</link>
	<description>It&#039;s All About Talent</description>
	<lastBuildDate>Fri, 18 May 2012 05:51:58 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
		<item>
		<title>Determining Pay Scale</title>
		<link>http://talentalley.com/2011/04/15/determining-pay-scale/</link>
		<comments>http://talentalley.com/2011/04/15/determining-pay-scale/#comments</comments>
		<pubDate>Fri, 15 Apr 2011 06:33:17 +0000</pubDate>
		<dc:creator>James Krouse</dc:creator>
				<category><![CDATA[Advancement]]></category>
		<category><![CDATA[Workplace Management]]></category>

		<guid isPermaLink="false">http://thejobshopper.com/?p=999</guid>
		<description><![CDATA[Joel Splosky, founder and CEO of Fog Creek Software, writes about a transparent payscale in his article Why I Never Let Employees Negotiate a Raise.  At first glance, Splosky seems to be suggesting one of those crazy, radical, workplace ideas that only software companies can handle.  Like free cappuccinos or air hockey: I wanted Fog Creek to have [...]]]></description>
			<content:encoded><![CDATA[<p>Joel Splosky, founder and CEO of Fog Creek Software, writes about a transparent payscale in his article <em><a href="http://www.inc.com/magazine/20090401/how-hard-could-it-be-employees-negotiate-pay-raises.html?nav=related" target="_blank">Why I Never Let Employees Negotiate a Raise</a></em>.  At first glance, Splosky seems to be suggesting one of those crazy, radical, workplace ideas that only software companies can handle.  Like free cappuccinos or air hockey:</p>
<blockquote><p>I wanted Fog Creek to have a salary scale that was as objective as possible. A manager would have absolutely no leeway when it came to setting a salary.</p></blockquote>
<p>But as he describes the system more, it doesn&#8217;t sound so radical.  Basically, Fog Creek determines a level for everyone based on Experience, Scope, and Skill.  Experience being how many years an employee is bringing to the table, scope being how much management they need or how many folks they&#8217;re managing, and skill being what they&#8217;re actually able to do.  Basically, every employee is assigned a pay level based on an average of Scope and Skill.  That average is  then compared to a sliding scale based on years of experience.  There&#8217;s an infographic in the article <a href="http://www.inc.com/magazine/20090401/how-hard-could-it-be-employees-negotiate-pay-raises.html?nav=related" target="_blank">here</a>.</p>
<p>Splosky is pretty convincing at heading off arguments about salary inversion &#8212; that&#8217;s when the market determines that rookies are worth more than current employees when labor markets are tight and demand for workers with certain skills are in high demand.  He basically says that employers should bite the bullet and give everyone a raise or determine other workplace incentives to keep employees.</p>
<p>There are a couple of possible issues here, the first being that Splosky&#8217;s payscale system seems geared toward the software industry.  While Skill, Scope, and Experience may seem like universal measures, they may be more difficult to apply to an accounting team or marketing department.  Second, it seems that even this simple scoring system could get complicated very quickly and many of the measures are subjective, essentially eliminating any fairness and transparency that was originally intended.</p>
<p>Still, this system is admirable in that it exists.   Many companies give raises (or don&#8217;t give them) based on whether or not they want an employee to stay and as a motivational tool.  Since most managers don&#8217;t have a system for giving raises, it becomes a shoot-from-the-hip, gut reaction game.  That&#8217;s just not good business.  Splosky found a system that works for his company.  Creating one for your company is also important, but it&#8217;s important to:</p>
<p>1.)  Keep It Simple:  Creating extra work and bureaucracy isn&#8217;t going to help anyone.  Even a simple three part rating system at Fog Creek can get complicated.</p>
<p>2.)  Realize It&#8217;s Not a Cure All:  Employees are motivated by all kinds of things and, for the most part, crave fairness.  A system like this will promote fairness, but will not be completely fair in and of itself.</p>
<p>3.)  Don&#8217;t Fear Transparency:  Splosky&#8217;s most radical suggestion is complete transparency in pay.  Employees may share information any way so why pretend that salaries are secret?  Don&#8217;t let someone&#8217;s &#8216;level&#8217; become code for salary and another numer to hide.</p>
<p>4.)  Tailor a System:  Creating a system that&#8217;s right for your market and company culture is important.  Some work environments are driven by efficiency, others by service, and others by sales.  It&#8217;s important to determine what drives your company and create a system that rewards the right combination of people and skills.</p>
<p>Read Splosky&#8217;s full article at Inc.com <a href="http://www.inc.com/magazine/20090401/how-hard-could-it-be-employees-negotiate-pay-raises.html?nav=related" target="_blank">here</a>.</p>
]]></content:encoded>
			<wfw:commentRss>http://talentalley.com/2011/04/15/determining-pay-scale/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

