<?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: How well documented is your process?</title>
	<atom:link href="http://blog.andresvivas.com/how-well-documented-is-your-process/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.andresvivas.com/how-well-documented-is-your-process/</link>
	<description>A blog about Practical, Effective IT Strategy Planning, by Andres Vivas</description>
	<lastBuildDate>Thu, 12 Jan 2012 22:08:15 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Andres Vivas</title>
		<link>http://blog.andresvivas.com/how-well-documented-is-your-process/comment-page-1/#comment-10</link>
		<dc:creator>Andres Vivas</dc:creator>
		<pubDate>Thu, 04 Dec 2008 13:50:45 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andresvivas.com/?p=73#comment-10</guid>
		<description>Greg,
Thanks for your comment.

You are correct. The struggle to complete or update the SOPs usually comes from the feeling that they are not worth the time you put into them. There is always something more important to accomplish, right? But then, the cost is too high when there is a real need like training a new employee or to recover from a system failure and we find the documentation is outdated or simply not there.

I think it is important to work on them periodically, to create a good habit that allows you to complete this important step.</description>
		<content:encoded><![CDATA[<p>Greg,<br />
Thanks for your comment.</p>
<p>You are correct. The struggle to complete or update the SOPs usually comes from the feeling that they are not worth the time you put into them. There is always something more important to accomplish, right? But then, the cost is too high when there is a real need like training a new employee or to recover from a system failure and we find the documentation is outdated or simply not there.</p>
<p>I think it is important to work on them periodically, to create a good habit that allows you to complete this important step.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Greg</title>
		<link>http://blog.andresvivas.com/how-well-documented-is-your-process/comment-page-1/#comment-9</link>
		<dc:creator>Greg</dc:creator>
		<pubDate>Wed, 03 Dec 2008 05:39:23 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andresvivas.com/?p=73#comment-9</guid>
		<description>Hey Andres, I&#039;m not in IT but I do agree with documenting proceedures and keeping them updated.  Unfortunately I get lazy and let this lapse quite often.  Maybe I need to set aside 2-3 hours a week to work on this.  Thanks for posting this up.</description>
		<content:encoded><![CDATA[<p>Hey Andres, I&#8217;m not in IT but I do agree with documenting proceedures and keeping them updated.  Unfortunately I get lazy and let this lapse quite often.  Maybe I need to set aside 2-3 hours a week to work on this.  Thanks for posting this up.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andres</title>
		<link>http://blog.andresvivas.com/how-well-documented-is-your-process/comment-page-1/#comment-4</link>
		<dc:creator>Andres</dc:creator>
		<pubDate>Thu, 27 Nov 2008 02:34:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andresvivas.com/?p=73#comment-4</guid>
		<description>Alec,
Yes, you are correct. I know we are not there yet, but we are working to reach that state where all the documents are up to date.

The first step is to identify the need to have SOPs. 
Second is to have the Subject Matter Expert (SME) responsible for the function to write the documentation. 
And third, and probably most difficult of all of the steps, is to create the habit for the staff to keep them up to date. I&#039;ll probably blog about this in the near future. 
Thanks,
Andres</description>
		<content:encoded><![CDATA[<p>Alec,<br />
Yes, you are correct. I know we are not there yet, but we are working to reach that state where all the documents are up to date.</p>
<p>The first step is to identify the need to have SOPs.<br />
Second is to have the Subject Matter Expert (SME) responsible for the function to write the documentation.<br />
And third, and probably most difficult of all of the steps, is to create the habit for the staff to keep them up to date. I&#8217;ll probably blog about this in the near future.<br />
Thanks,<br />
Andres</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alec Satin</title>
		<link>http://blog.andresvivas.com/how-well-documented-is-your-process/comment-page-1/#comment-3</link>
		<dc:creator>Alec Satin</dc:creator>
		<pubDate>Thu, 27 Nov 2008 01:33:14 +0000</pubDate>
		<guid isPermaLink="false">http://blog.andresvivas.com/?p=73#comment-3</guid>
		<description>Hi Andres,
Sounds as if your company is in pretty good shape.  Too often SOPs are written once, put on a shelf and forgotten until they are needed at which point it&#039;s discovered that they are months (years?) out of date.
Alec</description>
		<content:encoded><![CDATA[<p>Hi Andres,<br />
Sounds as if your company is in pretty good shape.  Too often SOPs are written once, put on a shelf and forgotten until they are needed at which point it&#8217;s discovered that they are months (years?) out of date.<br />
Alec</p>
]]></content:encoded>
	</item>
</channel>
</rss>

