<?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: Worst Practices Alert!</title>
	<atom:link href="http://blog.insurance-technologies.com/2006/12/worst-practices-alert/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.insurance-technologies.com/2006/12/worst-practices-alert/</link>
	<description>E-Commerce in Insurance with an emphasis on Social Technology</description>
	<lastBuildDate>Fri, 27 Aug 2010 16:00:24 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: Mike Wise</title>
		<link>http://blog.insurance-technologies.com/2006/12/worst-practices-alert/comment-page-1/#comment-18</link>
		<dc:creator>Mike Wise</dc:creator>
		<pubDate>Tue, 16 Jan 2007 21:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insurance-technologies.com/?p=99#comment-18</guid>
		<description>Great point - on both fronts.  The question is, why do internal IT departments do this when there is a wealth of best-practice info at their fingertips?</description>
		<content:encoded><![CDATA[<p>Great point &#8211; on both fronts.  The question is, why do internal IT departments do this when there is a wealth of best-practice info at their fingertips?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anonymous</title>
		<link>http://blog.insurance-technologies.com/2006/12/worst-practices-alert/comment-page-1/#comment-17</link>
		<dc:creator>Anonymous</dc:creator>
		<pubDate>Tue, 16 Jan 2007 00:36:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.insurance-technologies.com/?p=99#comment-17</guid>
		<description>Mike- Great entry about having to know your audience.  Too many internal IT departments just look at the requirements spit out an application.  &lt;br/&gt;&lt;br/&gt;One note, you may want to be careful what you term &quot;Senior Citizens&quot;  Medicare Part D is open for anyone age 65 or older.  I know a lot of 65 year olds that would not want to be considered a &quot;Senior Citizen&quot;</description>
		<content:encoded><![CDATA[<p>Mike- Great entry about having to know your audience.  Too many internal IT departments just look at the requirements spit out an application.  </p>
<p>One note, you may want to be careful what you term &#8220;Senior Citizens&#8221;  Medicare Part D is open for anyone age 65 or older.  I know a lot of 65 year olds that would not want to be considered a &#8220;Senior Citizen&#8221;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
