<?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: benefits workshop</title>
	<atom:link href="http://blogs.win7deployment.com/kimpartridge/2009/05/benefits-workshop/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.win7deployment.com/kimpartridge/2009/05/benefits-workshop/</link>
	<description>An IT Manager deploying Windows 7</description>
	<lastBuildDate>Thu, 13 Aug 2009 05:20:44 -0700</lastBuildDate>
	
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kim</title>
		<link>http://blogs.win7deployment.com/kimpartridge/2009/05/benefits-workshop/comment-page-1/#comment-2</link>
		<dc:creator>Kim</dc:creator>
		<pubDate>Mon, 18 May 2009 12:34:37 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.win7deployment.com/kimpartridge/?p=26#comment-2</guid>
		<description>Well I have read the report, actually scanned through it, but in some detail. So now I can roll the dice to see which staff will no longer be required  seeing as the report indicates halving the support team. I think the report or at least the input process needs a little more work. 
However it is still valuable as it clearly reflects where the opportunities are for some cost reduction, end user support being the most measurable. More difficult to measure is the indirect cost of improved end user productivity due to improved reliability of their tools. But in our environment this could be substantial as at present as an IT company we place very few restrictions on our user population and this will be an opportunity to meet a compromise with some of our business. I expect to be able to take a role based view, balancing need, desire (yes in our business it is relevant as a substantial percentage are of course technologists and desire translates to passion about what we do.) and risk.
Of course the other opportunity with reduced cost is to invest those savings in improved service and skill development further increasing the collective knowledge of the organisation.
The projected payback period of 8 months is also attractive, but will need to be measured. This suggests that the project could be budget neutral within the one budgeting period for me working well within our planning cycle.
Kim</description>
		<content:encoded><![CDATA[<p>Well I have read the report, actually scanned through it, but in some detail. So now I can roll the dice to see which staff will no longer be required  seeing as the report indicates halving the support team. I think the report or at least the input process needs a little more work.<br />
However it is still valuable as it clearly reflects where the opportunities are for some cost reduction, end user support being the most measurable. More difficult to measure is the indirect cost of improved end user productivity due to improved reliability of their tools. But in our environment this could be substantial as at present as an IT company we place very few restrictions on our user population and this will be an opportunity to meet a compromise with some of our business. I expect to be able to take a role based view, balancing need, desire (yes in our business it is relevant as a substantial percentage are of course technologists and desire translates to passion about what we do.) and risk.<br />
Of course the other opportunity with reduced cost is to invest those savings in improved service and skill development further increasing the collective knowledge of the organisation.<br />
The projected payback period of 8 months is also attractive, but will need to be measured. This suggests that the project could be budget neutral within the one budgeting period for me working well within our planning cycle.<br />
Kim</p>
]]></content:encoded>
	</item>
</channel>
</rss>
