<?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>OHSAS 18001 EXPERT &#187; Resources &amp; Tools</title>
	<atom:link href="http://ohsas18001expert.com/category/resources/feed/" rel="self" type="application/rss+xml" />
	<link>http://ohsas18001expert.com</link>
	<description>Operational Health and Safety</description>
	<lastBuildDate>Tue, 20 Apr 2010 18:48:36 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
		<item>
		<title>Out with the Old &#8211; In with the New</title>
		<link>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/</link>
		<comments>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/#comments</comments>
		<pubDate>Fri, 15 Jan 2010 15:07:03 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[record control]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=317</guid>
		<description><![CDATA[The start of the New Year is good time to pause, reflect and clean out. Many organizations use the start of the year as a time to review their OH&#38;S management system objectives and set new ones.  If their OH&#38;S programs are lagging in their implementation, new approaches or new assignments are considered.  This is [...]]]></description>
			<content:encoded><![CDATA[<p>The start of the New Year is good time to pause, reflect and clean out.</p>
<p>Many organizations use the start of the year as a time to review their OH&amp;S management system objectives and set new ones.  If their OH&amp;S programs are lagging in their implementation, new approaches or new assignments are considered. </p>
<p>This is also a good time to address all that PAPER – either physical paper or electronic paper.  This includes all those completed hazard evaluation forms, inspection checklists, excel spreadsheets, meeting notices and minutes, e-mails with various interested parties, incident investigations, corrective action reports,….</p>
<p>When I help develop record control processes and procedures for an organization, one of the concepts I try to incorporate is the inclusion of record schedules with record breaks and scheduled clean-out days. <span id="more-317"></span></p>
<p>A record schedule is a document that defines how a record is to be kept, how long it needs to be maintained in an active storage location and when it should be destroyed.  <a href="http://www.epa.gov/records/faqs/schedules.htm" target="_self">U.S. EPA has an informative discussion of the purpose and use of record schedules on its web site. </a></p>
<p>The first key to using a record schedule is organizing your records in a way that makes complying with your record retention requirements as easy as possible.  This usually means using record breaks – usually defined points in time when you start a new file. For example, rather than filing all of your records pertaining to a particular topic randomly in one file folder (physical or electronic), you file them by year so you can move an entire year’s worth of records to a different location (off-site storage or electronic archive) at one time. </p>
<p>The second key to using a record schedule is actually setting aside a time for moving old records out of active storage locations and getting rid of unnecessary records in accordance with your organization’s record retention policies. </p>
<p>Although this often appears to be an unimportant mundane task to “put off to another day” it is important to the smooth functioning of your OHSMS. </p>
<p>So, schedule your record clean-out day today.  By the way, wear comfortable clothes and order a pizza.  It will make the job easier.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2010/01/15/out-with-the-old-in-with-the-new/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Ban the Blame</title>
		<link>http://ohsas18001expert.com/2009/12/15/ban-the-blame/</link>
		<comments>http://ohsas18001expert.com/2009/12/15/ban-the-blame/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 13:29:20 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[corrective action]]></category>
		<category><![CDATA[incident investigation]]></category>
		<category><![CDATA[preventive action]]></category>
		<category><![CDATA[root causes]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=314</guid>
		<description><![CDATA[One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong.  This is not easy.  Often, the [...]]]></description>
			<content:encoded><![CDATA[<p>One of the key requirements of the OHSAS 18001 standard is establishing a procedure for taking corrective and preventive action (section 4.5.3.2).  Both corrective and preventive action need to include identifying the underlying causes – often called root causes – of whatever it is that is or went wrong. </p>
<p>This is not easy.  Often, the root cause investigation ends with a determination along the lines of “Joe screwed up.”  We play the blame game.</p>
<p>Why?</p>
<p><span id="more-314"></span>There have been a number of reasons advanced for this and most of them are probably true – at least in part.</p>
<p>Last week, a colleague lent me his copy of Dan Gano’s book – <a href="http://www.amazon.com/Apollo-Root-Cause-Analysis-Thinking/dp/1883677114/ref=sr_1_1?ie=UTF8&amp;s=books&amp;qid=1260882984&amp;sr=1-1" target="_blank">Apollo Root Cause Analysis.</a>  This book sets out a different way of approaching root cause analysis by focusing on defining a problem in terms of both the action and the conditions that caused the particular effect you are analyzing.  For example, you don’t get a fire (an effect) unless you have an ignition source (an action) as well as two conditions (fuel and oxygen at the right concentrations).  Remove either condition (fuel/oxygen) or the action (ignition) and the effect (fire) does not occur.</p>
<p>What I liked most about the book, however, was not the root cause methodology advanced in the book but the explanation of why we so often fall into the blame game.</p>
<p>In a word &#8211; storytelling.</p>
<p>As humans, we have a long tradition of storytelling.  It comes naturally to us.  It is how we have transmitted information for generations.  Everyone likes a good story.</p>
<p>Integral to storytelling is identifying your actors – answering the question “who” is central to telling a good story.  As Gano points out in his book, most incident reports provide a prime example of storytelling.  The initial focus is typically on who did what.  Unfortunately, for purposes of root cause analysis, storytelling sets us up for failure because it keeps us focused on the story &#8211; who, what, where and when &#8211; rather than focusing our attention on identifying the causes of an incident. </p>
<p>So when you are investigating an incident or nonconformity, tell your story.  It is, after all, human nature and likely irresistible.  But when you start your root cause analysis, put the story aside and take the “who” completely out of the analysis.  Remove the names and strike the identifiers.  Instead, focus your attention on the actions and conditions that lead to the situation (effect) that you are investigating.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/12/15/ban-the-blame/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Should I Write a Procedure?</title>
		<link>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/</link>
		<comments>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/#comments</comments>
		<pubDate>Fri, 06 Nov 2009 22:14:55 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Documentation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[decision making]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=274</guid>
		<description><![CDATA[One of the difficult questions that OH&#38;S managers face is &#8211; &#8220;Do we need a written procedure for [some process]?&#8221;  The dilemma is that although written procedures are a necessary part of an occupational safety and health management system &#8211; if you create too many formal procedures your OHSMS becomes complex, cumbersome and unwieldy.  I just got done reading an article in [...]]]></description>
			<content:encoded><![CDATA[<p>One of the difficult questions that OH&amp;S managers face is &#8211; &#8220;Do we need a written procedure for [some process]?&#8221;  The dilemma is that although written procedures are a necessary part of an occupational safety and health management system &#8211; if you create too many formal procedures your OHSMS becomes complex, cumbersome and unwieldy.</p>
<p> I just got done reading an article in the October 2009 <strong><em>Quality Progress Magazine</em></strong> that sets out a nifty tool for making this decision &#8211; a 2 x 2 matrix for deciding whether or not to standardize a process.  Although the example given in this article &#8211; <a href="http://www.asq.org/quality-progress/2009/10/one-good-idea/building-a-consensus.pdf" target="_blank">Building a Consensus</a> &#8211; is  for a quality system process, it can be easily adapted to making standardization decisions in an OH&amp;S management system.</p>
<p>Try it out for your OH&amp;S management system and let me know &#8211; &#8220;Did it work?&#8221; - by posting your comments below.</p>
<h6>© ENLAR® Compliance Services, Inc. (2009)</h6>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/11/06/should-i-write-a-procedure/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What are you going to STOP doing?</title>
		<link>http://ohsas18001expert.com/2009/02/25/what-are-you-going-to-stop-doing/</link>
		<comments>http://ohsas18001expert.com/2009/02/25/what-are-you-going-to-stop-doing/#comments</comments>
		<pubDate>Wed, 25 Feb 2009 16:26:01 +0000</pubDate>
		<dc:creator>Thea</dc:creator>
				<category><![CDATA[OHSMS Implementation]]></category>
		<category><![CDATA[Resources & Tools]]></category>
		<category><![CDATA[OHS performance]]></category>
		<category><![CDATA[Peter Drucker]]></category>

		<guid isPermaLink="false">http://ohsas18001expert.com/?p=58</guid>
		<description><![CDATA[Many OHS management systems and programs have a major problem – they are bloated with paperwork, inefficient in their operation and filled with busywork.  These programs are often focused on the achievement of arbitrary metrics rather than improved OH&#38;S performance. As a result, the managers of these programs are often fed-up, burned out and overwhelmed.  [...]]]></description>
			<content:encoded><![CDATA[<p>Many OHS management systems and programs have a major problem – they are bloated with paperwork, inefficient in their operation and filled with busywork.  These programs are often focused on the achievement of arbitrary metrics rather than improved OH&amp;S performance. As a result, the managers of these programs are often fed-up, burned out and overwhelmed.  They are also increasingly being told – “Given the current economy, you need to do more with less.”</p>
<p>That is the wrong message and the wrong goal. </p>
<p>To quote <a href="http://en.wikipedia.org/wiki/Peter_Drucker" target="_blank">Peter Drucker</a> – “There is nothing so useless as doing efficiently what should not be done at all.” </p>
<p>The goal should not be to do more with less – it should be <strong><em>to do less</em></strong>.</p>
<p><span id="more-58"></span>What many OHS programs really need is a good pruning.  It is common for occupational health and safety management systems – particularly those driven by corporate mandates – to be filled with procedural “deadwood” and nonsensical “undergrowth”.</p>
<p>Want to start cutting back?  Try the following –</p>
<p><strong>1.  Re-examine your Assumptions</strong></p>
<p>Often OH&amp;S programs are put in place because of so-called “good practice”.  These “good practices” are often characterized as requirements so the needed resources can be justified. </p>
<p>Review your programs and procedures. For each program, procedure and form, re-examine the assumption that “we must do it this way”.   Do you need to do it at all?  Is there a more effective way?</p>
<p><strong>2. Push Back on Busywork</strong></p>
<p>It is a fact of life.  People like to tell other people how to do things. </p>
<p>Evaluate the “busywork” quotient of your processes and procedures.  Avoid creating unnecessary work for others and “push back” when others attempt to do the same to you. </p>
<ul>
<li>Don’t create a twenty page procedure if a one page form will do. </li>
<li>Don’t take on activities simply because they are “a nice idea” (often defined as something mentioned in a meeting by someone in senior management).</li>
<li>Don’t add multiple layers of redundancy when it is not needed – especially if it is only to please some auditor.</li>
</ul>
<p><strong>3.  Keep Your Focus on Performance</strong></p>
<p>Make sure you truly understand your OHSMS requirements – your OH&amp;S risks and your legal obligations.  Focus your efforts on addressing these first &#8211; in as an efficient a manner as possible.  Say “NO” to suggestions that are not focused on improving your OHS performance.</p>
<p><strong>4.  Be a Tortoise not a Hare</strong></p>
<p>Focus each day on consistently moving forward.  It is easy to get discouraged when progress is slow and results are not readily apparent. Keep at it. </p>
<p>Remain vigilant.  Resist the temptation to take on more than you have the resources to reasonably accomplish. If you have a plan and keep focused on doing what is important – rather than adding in additional activities that are new and exciting – you can accomplish your goals. </p>
<p><strong>Pruning is not easy.</strong> </p>
<p>The status quo is often comfortable.  Change often meets with resistance. </p>
<p> You are very likely to hear &#8211; “We have always done it this way.  Why do we have to change?”</p>
<p>The answer – to survive when resources are scarce.</p>
<p>Need additional help? </p>
<p>Check out the following –</p>
<ul>
<li><a href="http://www.e-bim.com/hr/article.cfm%5CexternalID:210%5CTitle:Abandoning_the_Obsolete_and_Unproductive:_A_Difficult_But_Necessary_Task_%5CAuthor:From%20the%20Editorial%20Staff%20at%20e-BIM" target="_blank">Abandoning the Obsolete and Unproductive</a> - Column on Human Resources IQ website discussing why organizations need to prune their efforts.</li>
<li><em><a href="http://www.amazon.com/Power-Positive-No-How-Still/dp/0553804987" target="_blank">The Power of a Positive No</a></em> by William Ury &#8211; Book offering concrete advice for saying No.</li>
</ul>
<p><span style="font-size: 8pt; font-family: Arial;">© ENLAR<sup>®</sup> Compliance Services, Inc. (2009)</span></p>
]]></content:encoded>
			<wfw:commentRss>http://ohsas18001expert.com/2009/02/25/what-are-you-going-to-stop-doing/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
