<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Avoid Starting Out on the Wrong Foot in Software Deployment</title>
	<atom:link href="http://www.performancesolutionstech.com/avoid-starting-out-on-the-wrong-foot-in-software-deployment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.performancesolutionstech.com/avoid-starting-out-on-the-wrong-foot-in-software-deployment/</link>
	<description></description>
	<lastBuildDate>Wed, 11 Jan 2012 20:34:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
	<item>
		<title>By: sharley</title>
		<link>http://www.performancesolutionstech.com/avoid-starting-out-on-the-wrong-foot-in-software-deployment/comment-page-1/#comment-35</link>
		<dc:creator>sharley</dc:creator>
		<pubDate>Fri, 25 Jul 2008 16:31:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.performancesolutionstech.com/index.php/avoid-starting-out-on-the-wrong-foot-in-software-deployment#comment-35</guid>
		<description>This blog is very useful. Can&#039;t tell you the times when choosing the software prior to identifying the objectives we need to overcome as a company generally comes after the selection of the software. Only to find out that the software does not meet the needs.

By identifying needs first, software second, helps us to ensure a good fit, think through the business problems we need to conquer and to do this successfully, we find that collaborating across all business units is a must. If not, we find major gaps in our plan to improve and achieve our plans. Once we have all the input it becomes less of a thought process to identify how the organization will use the software to overcome our pain points. The implementation becomes less complicated and our objectives are clear, everyone knows what their role is, we have a better idea of the metrics we need to measure for success, and we move forward with direction that makes sense and maps to our plan. I find the investment immediately becomes worth the time and effort.

Having these important pieces to the puzzle figured out beforehand then serves as requirements for applicable consulting engagement, software configuration and training objectives.

Thanks for this valuable information!</description>
		<content:encoded><![CDATA[<p>This blog is very useful. Can&#8217;t tell you the times when choosing the software prior to identifying the objectives we need to overcome as a company generally comes after the selection of the software. Only to find out that the software does not meet the needs.</p>
<p>By identifying needs first, software second, helps us to ensure a good fit, think through the business problems we need to conquer and to do this successfully, we find that collaborating across all business units is a must. If not, we find major gaps in our plan to improve and achieve our plans. Once we have all the input it becomes less of a thought process to identify how the organization will use the software to overcome our pain points. The implementation becomes less complicated and our objectives are clear, everyone knows what their role is, we have a better idea of the metrics we need to measure for success, and we move forward with direction that makes sense and maps to our plan. I find the investment immediately becomes worth the time and effort.</p>
<p>Having these important pieces to the puzzle figured out beforehand then serves as requirements for applicable consulting engagement, software configuration and training objectives.</p>
<p>Thanks for this valuable information!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

