<?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>No Secret &#187; Workflow</title>
	<atom:link href="http://noccrit.com/Steveblog/tag/workflow/feed/" rel="self" type="application/rss+xml" />
	<link>http://noccrit.com/Steveblog</link>
	<description>Not everything must be a CCrit.</description>
	<lastBuildDate>Fri, 12 Nov 2010 15:04:39 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.4</generator>
		<item>
		<title>Getting Paper Out of the Office</title>
		<link>http://noccrit.com/Steveblog/2010/01/getting-paper-out-of-the-office/</link>
		<comments>http://noccrit.com/Steveblog/2010/01/getting-paper-out-of-the-office/#comments</comments>
		<pubDate>Wed, 13 Jan 2010 12:20:06 +0000</pubDate>
		<dc:creator>noccrit</dc:creator>
				<category><![CDATA[CCrits]]></category>
		<category><![CDATA[Working Smarter]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://noccrit.com/Steveblog/?p=37</guid>
		<description><![CDATA[<p>I&#8217;m speaking in New York in three weeks on the topic Getting Paper Out of the (Attorney&#8217;s) Office, as part of a two-person panel at the LegalTech Conference and trade show.</p>
<p>Below are the main points I&#8217;m currently looking at for my part of the discussion. I&#8217;d love to hear from folks who have additional or [...]]]></description>
			<content:encoded><![CDATA[<p>I&#8217;m speaking in New York in three weeks on the topic Getting Paper Out of the (Attorney&#8217;s) Office, as part of a two-person panel at the <a href="http://www.legaltechshow.com/r5/cob_page.asp?category_id=62962&amp;initial_file=cob_page-ltech.asp" target="_blank">LegalTech Conference and trade show</a>.</p>
<p>Below are the main points I&#8217;m currently looking at for my part of the discussion. I&#8217;d love to hear from folks who have additional or different ideas.</p>
<ul>
<li>Use workflow systems to route work throughout the office
<ul>
<li>Optimize the processes behind them. Don&#8217;t automate broken processes (Steven&#8217;s First Rule of IT).</li>
<li>Reconsider &#8220;standard procedures&#8221; &#8212; should they really be standards?</li>
<li>Look to Lean Six Sigma to reduce waste and non-value-added activities.</li>
</ul>
</li>
<li>Use scan-on-demand when users request paper records from storage (which at least gets the paper into cheap storage space and over time will obviate those paper records)</li>
<li>Send documents to clients via PDF or Word (or equivalents).
<ul>
<li>Invoices, too: if clients don&#8217;t have electronic invoicing, don&#8217;t send them paper that they can lose track of.</li>
</ul>
</li>
<li>Get dual monitors, or an extra monitor in parallel with your widescreen laptop, to read large documents comfortably on screen</li>
<li>Use Kindle, Nook, smartphones, etc. to read documents during commute time (this is in New York, where most commuting is by means other than driving yourself; obviously, this is a very bad idea &#8212; but becoming unfortunately common &#8212; when you&#8217;re driving!)</li>
</ul>
<p>Suggestions welcome. Thanks.</p>
]]></content:encoded>
			<wfw:commentRss>http://noccrit.com/Steveblog/2010/01/getting-paper-out-of-the-office/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>A Healthcare-IT Professional Discusses Workflow</title>
		<link>http://noccrit.com/Steveblog/2010/01/a-healthcare-it-professional-discusses-workflow/</link>
		<comments>http://noccrit.com/Steveblog/2010/01/a-healthcare-it-professional-discusses-workflow/#comments</comments>
		<pubDate>Tue, 12 Jan 2010 12:59:38 +0000</pubDate>
		<dc:creator>noccrit</dc:creator>
				<category><![CDATA[CCrits]]></category>
		<category><![CDATA[Project Management]]></category>
		<category><![CDATA[Working Smarter]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://noccrit.com/Steveblog/?p=35</guid>
		<description><![CDATA[<p>Healthcare IT pro Elyse Nielsen has one of the best-named blogs around: AntiClue. She also has a recent post on workflow. In it, she lists what she sees as the top six workflow issues:</p>

Automating a bad process will just make it fail faster and magnify the problem. This is very similar to Steven&#8217;s First Law [...]]]></description>
			<content:encoded><![CDATA[<p>Healthcare IT pro Elyse Nielsen has one of the best-named blogs around: AntiClue. She also has <a href="http://www.anticlue.net/archives/001031.htm" target="_blank">a recent post</a> on workflow. In it, she lists what she sees as the top six workflow issues:</p>
<ol>
<li><em>Automating a bad process will just make it fail faster and magnify the problem</em>. This is very similar to Steven&#8217;s First Law of IT: Don&#8217;t Automate Broken Processes. It&#8217;s absolutely the #1 issue.</li>
<li><em>A clinical process may be the art of the workaround</em>. This is a relative of item #1. Workarounds happen, and indeed are often necessary&#8230; but don&#8217;t automate them unless the workaround itself is the best way to solve the problem long term.</li>
<li><em>Avoid grandiose workflows</em>. Yup, don&#8217;t boil the ocean. The 80/20 rule should be your watchword. Keep it simple. Then revise as you learn more.</li>
<li><em>(Specific to healthcare. I don&#8217;t know how to translate it well.)</em></li>
<li><em>Not everyone flows work the same way even when they perform parallel functions</em>.  It would be easier for you if they did&#8230; but the goal is to make it easier for the users, not the project team.</li>
<li><em>Engineer for the mainstream, not all the exceptions</em>. Here&#8217;s another version of the 80/20 rule.</li>
</ol>
<p>I&#8217;m not sure I&#8217;d list these as my top six, mostly because I think 1+2 and 3+6 are redundant&#8230; but they are important no matter how you number them.</p>
<p>Improving workflow may be the most significant thing an external professional (e.g., outside the user/customer community) can do to help out a team. It&#8217;s often surprisingly simple, at least at the 80/20 level. Junk simply accretes on processes. If you can get out the pressure washer and scrub off the accretions, you can make a dramatic difference. (Just make sure the spray from the pressure washer doesn&#8217;t hit the users; don&#8217;t wash the baby with the bathwater, so to speak.)</p>
]]></content:encoded>
			<wfw:commentRss>http://noccrit.com/Steveblog/2010/01/a-healthcare-it-professional-discusses-workflow/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Kludge or Inspiration?</title>
		<link>http://noccrit.com/Steveblog/2010/01/kludge-or-inspiration/</link>
		<comments>http://noccrit.com/Steveblog/2010/01/kludge-or-inspiration/#comments</comments>
		<pubDate>Mon, 11 Jan 2010 18:21:01 +0000</pubDate>
		<dc:creator>noccrit</dc:creator>
				<category><![CDATA[CCrits]]></category>
		<category><![CDATA[Working Smarter]]></category>
		<category><![CDATA[Goals]]></category>
		<category><![CDATA[Workflow]]></category>

		<guid isPermaLink="false">http://noccrit.com/Steveblog/?p=33</guid>
		<description><![CDATA[<p>A fascinating picture-blog called There, I Fixed It: Epic Kludges had a photo last week of a whiteboard competing for space with a light switch, reproduced in reduced size at right. Kludge or inspired work-around?</p>
<p>(A kludge, pronounced KLOOZHE, is a term for an ungainly quick-and-dirty solution to a knotty problem. It started in the tech [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignright" src="http://thereifixedit.files.wordpress.com/2010/01/129071075658332411.jpg" alt="" width="210" height="158" />A fascinating picture-blog called There, I Fixed It: Epic Kludges had a <a href="http://thereifixedit.com/2010/01/09/not-sure-bright-ideas-work-like-that" target="_blank">photo last week</a> of a whiteboard competing for space with a light switch, reproduced in reduced size at right. Kludge or inspired work-around?</p>
<p>(A kludge, pronounced KLOOZHE, is a term for an ungainly quick-and-dirty solution to a knotty problem. It started in the tech world but is now seeing currency elsewhere.)</p>
<p>So the whiteboard: kludge or inspiration?</p>
<p>I think it depends on your goal&#8230; which is the point of this post. How can you judge something like this in a vacuum?</p>
<p>Let&#8217;s start with an assumption on how it got there. The whiteboard arrived after the light switch was installed, and either the employee in the office wanted the biggest whiteboard that would fit or the whiteboard was pre-ordered and the installation person took installing it as a challenge.</p>
<p>I suspect different people might have different takes on it:</p>
<ul>
<li>Buildings and Grounds manager: Ugly, inappropriate, next time get the right-sized whiteboard.</li>
<li>Installer: Well, I got it up there. I hope my manager doesn&#8217;t find out.</li>
<li>Employee in the office: Thank you! I now have extra whiteboard space to sketch out ideas, space I wouldn&#8217;t have had if the board had been a foot shorter (stopping to the right of the switchplate).</li>
</ul>
<p>As in inveterate whiteboard user, I&#8217;m with the employee. I have whiteboards up all over the place. Frankly, I wish I&#8217;d thought of this in my last office at Microsoft!</p>
<p>(And if I were the B&amp;G guy, I&#8217;d applaud the installer for ingenuity, unless perhaps this was in a customer-facing lobby.)</p>
]]></content:encoded>
			<wfw:commentRss>http://noccrit.com/Steveblog/2010/01/kludge-or-inspiration/feed/</wfw:commentRss>
		<slash:comments>5</slash:comments>
		</item>
	</channel>
</rss>

