<?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 for KnowledgePay Blog</title>
	<atom:link href="http://www.knowledgepay.com/blog/?feed=comments-rss2" rel="self" type="application/rss+xml" />
	<link>http://www.knowledgepay.com/blog</link>
	<description></description>
	<lastBuildDate>Tue, 29 Nov 2011 21:40:32 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
<meta xmlns="http://www.w3.org/1999/xhtml" name="robots" content="noindex,follow" />
	<item>
		<title>Comment on Job Titles Do Have a Purpose by Drew Brown</title>
		<link>http://www.knowledgepay.com/blog/?p=51#comment-64</link>
		<dc:creator>Drew Brown</dc:creator>
		<pubDate>Tue, 29 Nov 2011 21:40:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.knowledgepay.com/blog/?p=51#comment-64</guid>
		<description>I readily admit that job titles have a purpose and I couldn&#039;t agree more that what was said in the first paragraph.  I am a traditional Comp person and I&#039;ve always believed that the job title should say something about the role of the job in the organization.  Job titles should be as functional as possible.  For example, HR jobs should have HR job titles, finance jobs should have finance job titles, and so on.  I have debated with managers who like to call the jobs in their organization some exotic derivative of a standard job title thinking that there may be some kind of premium associated with a new and sexy job title.  I normally tell managers that they have the discretion to use any public title they want, but when it comes to identifying a job by its title in our HR systems, that&#039;s my domain and I hold firm to exercising the discretion of identifying jobs by their internal systems-related job title.  I am as protective of the job descriptions as I am job titles  because job titles are part of the job description.  In any organization, you have to pick your battles so I allow managers to control their external public job title in exchange for them relinquishing their control over internal job titles.  I do find that sometimes the battle shifts in a debate over whether or not a standard job needs to have a modification created over minor differences in the original job classification.  I find that the battles over the proliferation of job classifications is a much harder battle to fight.  Ultimately, I&#039;ve found that my relationship with a given manager will determine if I can keep the list of job classifications to a reasonable level and I use that same relationship to come to an agreement over job titles.</description>
		<content:encoded><![CDATA[<p>I readily admit that job titles have a purpose and I couldn&#8217;t agree more that what was said in the first paragraph.  I am a traditional Comp person and I&#8217;ve always believed that the job title should say something about the role of the job in the organization.  Job titles should be as functional as possible.  For example, HR jobs should have HR job titles, finance jobs should have finance job titles, and so on.  I have debated with managers who like to call the jobs in their organization some exotic derivative of a standard job title thinking that there may be some kind of premium associated with a new and sexy job title.  I normally tell managers that they have the discretion to use any public title they want, but when it comes to identifying a job by its title in our HR systems, that&#8217;s my domain and I hold firm to exercising the discretion of identifying jobs by their internal systems-related job title.  I am as protective of the job descriptions as I am job titles  because job titles are part of the job description.  In any organization, you have to pick your battles so I allow managers to control their external public job title in exchange for them relinquishing their control over internal job titles.  I do find that sometimes the battle shifts in a debate over whether or not a standard job needs to have a modification created over minor differences in the original job classification.  I find that the battles over the proliferation of job classifications is a much harder battle to fight.  Ultimately, I&#8217;ve found that my relationship with a given manager will determine if I can keep the list of job classifications to a reasonable level and I use that same relationship to come to an agreement over job titles.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Market Pricing Social Media Jobs (Really, Any Emerging Job Family) by Mel Croner</title>
		<link>http://www.knowledgepay.com/blog/?p=34#comment-31</link>
		<dc:creator>Mel Croner</dc:creator>
		<pubDate>Tue, 20 Sep 2011 16:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.knowledgepay.com/blog/?p=34#comment-31</guid>
		<description>Chris has it exactly right!  One can guess at the market for a job or group of jobs, like social media, or one can obtain market data that provides a valid estimate of what, really, is being paid.  Salary data gathering sites such as Monster as well as networking sites such as LinkedIn can point to the general direction of &quot;going&quot; rates.  However, the validity of such information must be taken with a grain of salt as there is no systematic follow-up to job matches and much of the data are self-reported.  (Puffing is not prevented!!)

The Croner Digital Content &amp; Technology Survey starts with a planning meeting of participants to define what jobs are needed in the survey and the descriptions of these jobs.  If these jobs are out there in enough participating companies, they will be included in the survey and data on the market rates reported.

While social media jobs are moving fast, they are not moving that fast.  As Chris pointed out, &quot;hot&quot; jobs come and go.  Social media jobs currently are in the spotlight.  Next year, it will be other jobs.

The secret to understanding the market is simple, participate in relevant, professionally conducted surveys and use the data produced.</description>
		<content:encoded><![CDATA[<p>Chris has it exactly right!  One can guess at the market for a job or group of jobs, like social media, or one can obtain market data that provides a valid estimate of what, really, is being paid.  Salary data gathering sites such as Monster as well as networking sites such as LinkedIn can point to the general direction of &#8220;going&#8221; rates.  However, the validity of such information must be taken with a grain of salt as there is no systematic follow-up to job matches and much of the data are self-reported.  (Puffing is not prevented!!)</p>
<p>The Croner Digital Content &amp; Technology Survey starts with a planning meeting of participants to define what jobs are needed in the survey and the descriptions of these jobs.  If these jobs are out there in enough participating companies, they will be included in the survey and data on the market rates reported.</p>
<p>While social media jobs are moving fast, they are not moving that fast.  As Chris pointed out, &#8220;hot&#8221; jobs come and go.  Social media jobs currently are in the spotlight.  Next year, it will be other jobs.</p>
<p>The secret to understanding the market is simple, participate in relevant, professionally conducted surveys and use the data produced.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Jacqueline Kuhn Recognized by IHRIM by Tom Mandel</title>
		<link>http://www.knowledgepay.com/blog/?p=14#comment-3</link>
		<dc:creator>Tom Mandel</dc:creator>
		<pubDate>Thu, 07 Jul 2011 14:35:47 +0000</pubDate>
		<guid isPermaLink="false">http://v2.knowledgepay.com/blog/?p=14#comment-3</guid>
		<description>Congratulations Jacqueline!! Good job!</description>
		<content:encoded><![CDATA[<p>Congratulations Jacqueline!! Good job!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

