<?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>Bay Area Critical Incident Stress Management Team &#187; Tips</title>
	<atom:link href="http://criticalincident.net/category/debriefings/tips/feed/" rel="self" type="application/rss+xml" />
	<link>http://criticalincident.net</link>
	<description>CISM Information and Communications</description>
	<lastBuildDate>Tue, 14 Jun 2011 00:54:46 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1</generator>
		<item>
		<title>Tips, tips, tips</title>
		<link>http://criticalincident.net/2009/06/18/tips-tips-tips/</link>
		<comments>http://criticalincident.net/2009/06/18/tips-tips-tips/#comments</comments>
		<pubDate>Thu, 18 Jun 2009 22:22:41 +0000</pubDate>
		<dc:creator>admin</dc:creator>
				<category><![CDATA[Debriefings]]></category>
		<category><![CDATA[Tips]]></category>

		<guid isPermaLink="false">http://criticalincident.net/?p=67</guid>
		<description><![CDATA[The idea for this site came out of a desire to share practical tips that we have learned during debriefings and team meetings.  We&#8217;re thinking that one day, we might turn them into a book, but for now, they live as pages on this web...]]></description>
			<content:encoded><![CDATA[<p>The idea for this site came out of a desire to share practical tips that we have learned during debriefings and team meetings.  We&#8217;re thinking that one day, we might turn them into a book, but for now, they live as pages on this web site. We&#8217;d love your contributions.  Add your experiences in the comments and we&#8217;ll incorporate them&#8230; or you can email them to <a href="mailto:nick.arnett+cism@gmail.com">Nick </a>and he&#8217;ll do it.  So far, here are the pages we&#8217;ve developed.</p>
<ul>
<li><a href="http://criticalincident.net/tips-scheduling/">Scheduling a debriefing</a> &#8211; how to make debriefings happen and prepare for them.</li>
<li><a href="http://criticalincident.net/tips-introductions/">Introducing a debriefing</a> &#8211; things to say before you get started.</li>
<li><a href="http://criticalincident.net/tips-acknowledgement/">Acknowledge </a>- the first part of a debriefing.</li>
<li><a href="http://criticalincident.net/tips-acknowledgement/">Express </a>- second part.</li>
<li><a href="http://criticalincident.net/tips-action/">Act </a>- third part (send us your action step examples!).</li>
<li><a href="http://criticalincident.net/tips-celebrate/">Celebrate </a>- fourth part &#8211; how does your team do this?</li>
<li><a href="http://criticalincident.net/children-and-schools/">Children and schools </a>- tips specific to little ones</li>
<li><a href="http://criticalincident.net/out-of-control/">Out of control</a> &#8211; when debriefings take a detour</li>
<li><a href="http://criticalincident.net/tips-afterwards/">Afterwards </a>- debriefing the debriefers</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://criticalincident.net/2009/06/18/tips-tips-tips/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

