<?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>Incident Check &#187; james</title>
	<atom:link href="http://www.incidentcheck.com/index.php/author/james/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.incidentcheck.com</link>
	<description>Affordable Incident Tracking Software</description>
	<lastBuildDate>Thu, 10 Jul 2014 05:27:34 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=4.2.2</generator>
	<item>
		<title>New Release &#8211; Investigation Timeline</title>
		<link>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/</link>
		<comments>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/#comments</comments>
		<pubDate>Tue, 29 Oct 2013 17:08:57 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=374</guid>
		<description><![CDATA[We are pleased to announce more new Incident Check Features! Additional functionality now available: Investigation Timeline Causal Analysis comments Faster corrective action updates Full size images File upload changes Leading / Lagging indicator summary Injury details &#8211; body part, nature of injury and injury cause Investigation Timeline Administrators can set a report to have an [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>We are pleased to announce more new Incident Check Features!</p>
<p>Additional functionality now available:</p>
<ul>
<li>Investigation Timeline</li>
<li>Causal Analysis comments</li>
<li>Faster corrective action updates</li>
<li>Full size images</li>
<li>File upload changes</li>
<li>Leading / Lagging indicator summary</li>
<li>Injury details &#8211; body part, nature of injury and injury cause</li>
</ul>
<p><strong>Investigation Timeline</strong></p>
<p>Administrators can set a report to have an investigation timeline on any report type in the system through the settings.  This will then allow you to specify dates and times and a description of the investigative activity that was undertaken.  Along with this you can upload files that are relevant to that investigation step.</p>
<p>Once this is complete, we have a mechanism where you can step through the timeline to review each step that you will see in the sidebar beside the incident.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture.png"><img class="alignnone  wp-image-377" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture.png" width="701" height="207" /></a></p>
<p><strong>Causal Analysis comments</strong></p>
<p>When choosing your causal analysis items, we now have an area for comments that pertain to each particular cause.</p>
<p>&nbsp;</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture2.png"><img class="alignnone  wp-image-382" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture2.png" width="538" height="299" /></a></p>
<p><strong>Faster corrective action updates</strong></p>
<p>In the corrective action emails, we have changed things just slightly to allow people to quickly click the email link and then choose to complete or cancel the corrective action without having to log in to Incident Check.</p>
<p><strong>Full page images in PDFs</strong></p>
<p>In the generated PDF for a report, there is now the option to attach full size images to the end of  the report.  This is very helpful when there is fine detail on an image that the thumbnail does not show.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture3.png"><img class="alignnone  wp-image-383" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture3.png" width="192" height="380" /></a></p>
<p>&nbsp;</p>
<p><strong>File upload changes</strong></p>
<p>We have modernized the file upload portion of the report page to allow either images or files to be uploaded, and to have multiple uploads running at the same time.</p>
<p><strong>Leading / Lagging indicator summary</strong></p>
<p>A quick report, the first of many, that will start focusing on Leading Indicators.  This is an area of focus for Incident Check in general in the upcoming weeks and months, as we are seeing more and more customers really looking to leading indicators to ensure that things are being handled pro-actively.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture4.png"><img class="alignnone  wp-image-384" alt="Capture" src="http://www.incidentcheck.com/wp-content/uploads/2013/10/Capture4.png" width="728" height="301" /></a></p>
<p><strong>Injury details</strong></p>
<p>Now, when a report dealing with an injury is entered, you have the option of adding details on the injured body part as well as  the nature of the injury and the cause of the injury.  Note that this cause is different from the overall causal analysis in subtle ways.  With Causal Analysis, a person is trying to get at the reasons for the incident happening.  With an injury cause, we are focusing on the more specific details of the injury itself.</p>
<p>&nbsp;</p>
<p>As always, feedback on these features is appreciated and if you would like to discuss them, feel free to email or calla t any time.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/new-release-investigation-timeline/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Latest Release Features &#8211; Stats and Multiple Groups</title>
		<link>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/</link>
		<comments>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/#comments</comments>
		<pubDate>Tue, 05 Feb 2013 20:38:44 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Release Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=310</guid>
		<description><![CDATA[The latest changes to IncidentCheck include 2 main changes to how groups are handled in the system. 1.  Better Group Level Statistics Statistics now have a way to break them down by the Groups that are set up in the system.  In our use at 3CIS, we have Wireless, Cabling, and Software Divisions in the [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The latest changes to IncidentCheck include 2 main changes to how groups are handled in the system.</p>
<p>1.  Better Group Level Statistics</p>
<p>Statistics now have a way to break them down by the Groups that are set up in the system.  In our use at 3CIS, we have Wireless, Cabling, and Software Divisions in the company.  You can now choose the ones you would like to see and export the graph or data to provide comprehensive, side-by-side comparisons of the performance of each division.</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/02/stats.png"><img class="alignnone size-full wp-image-312" alt="stats" src="http://www.incidentcheck.com/wp-content/uploads/2013/02/stats.png" width="449" height="357" /></a></p>
<p>2.  Multi-Groups per User</p>
<p>Additionally, we added the ability to have users be part of more than one group under a given label.  Again, in our case this means that a user from 3CIS can be part of the Cabling Division, the Wireless, or the Software division, or any combination of the 3.  Previously we limited this to only 1 choice but the newest change reflects the reality at many of our customers&#8217; companies &#8211; people are often part of more than one division or other group.</p>
<p>To do this, you set up a User Account for Group Access as per usual, but instead of a drop-down to choose the group, we have a combo box where you can Control-Click to select multiple items, as in the screenshot below:</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2013/02/gla.png"><img class="alignnone size-full wp-image-314" alt="gla" src="http://www.incidentcheck.com/wp-content/uploads/2013/02/gla.png" width="544" height="242" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/latest-release-features-stats-and-multiple-groups/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Near Misses &#8211; Failures or Successes?</title>
		<link>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/</link>
		<comments>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/#comments</comments>
		<pubDate>Tue, 14 Aug 2012 17:54:34 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=247</guid>
		<description><![CDATA[Wired magazine has an article out examining the perception of near misses (or close calls) and investigates if they are &#8220;Near Disasters&#8221; or &#8220;Lucky Breaks&#8221;. Essentially, they argue that we should look at them as a failure, not a success, as they are leading indicators of incidents.  Citing the Process Improvement Institute, across many industries [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Wired magazine has an article out examining the perception of near misses (or close calls) and investigates if they are &#8220;Near Disasters&#8221; or &#8220;Lucky Breaks&#8221;.</p>
<p>Essentially, they argue that we should look at them as a failure, not a success, as they are leading indicators of incidents.  Citing the <a title="PII" href="http://www.piii.com/">Process Improvement Institute</a>, across many industries there are between 50 and 100 near misses recorded per serious incident, and about 10,000 smaller errors occur during that time.</p>
<p><a title="Wired Near Misses" href="http://www.wired.com/wiredscience/2012/08/st_essay_close_calls/">It is also a great read.</a></p>
<p>With <a title="Incident Check" href="http://www.incidentcheck.com">Incident Check</a>, we have been focusing on that for years.  We provide the necessary tools to track near misses and provide roll-up statistics to show how many near misses are being recorded.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/near-misses-failures-or-successes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Getting a Latitude and Longitude for a Location</title>
		<link>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/</link>
		<comments>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/#comments</comments>
		<pubDate>Mon, 23 Jul 2012 15:54:41 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=238</guid>
		<description><![CDATA[For Incident Check, we require that all reports (incidents, near misses, and hazards) are tagged with a specific location.  This is for many reasons, the biggest one being that this is how our customers generally tracked things before Incident Check was implemented. There has been 1 stumbling block for locations, however, and that is our [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>For Incident Check, we require that all reports (incidents, near misses, and hazards) are tagged with a specific location.  This is for many reasons, the biggest one being that this is how our customers generally tracked things before Incident Check was implemented.</p>
<p>There has been 1 stumbling block for locations, however, and that is our mandatory latitude and longitude.  But, getting this information is as simple as firing up Google Maps.</p>
<p>For example, 3CIS headquarters is in Edmonton.  To get a lat/lon pair, simply zero in on the building in Google Maps, right click, and choose &#8220;What&#8217;s here?&#8221; from the menu.</p>
<p>You will then see the latitude and longitude in the search box at the top, like in the following screenshot:</p>
<p>&nbsp;</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/07/latlong.png"><img class="alignnone  wp-image-239" src="http://www.incidentcheck.com/wp-content/uploads/2012/07/latlong.png" alt="" width="878" height="593" /></a></p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/getting-a-latitude-and-longitude-for-a-location/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Loss Tracking</title>
		<link>http://www.incidentcheck.com/index.php/loss-tracking-2/</link>
		<comments>http://www.incidentcheck.com/index.php/loss-tracking-2/#comments</comments>
		<pubDate>Mon, 16 Jul 2012 20:03:59 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=235</guid>
		<description><![CDATA[Incidents, as we define them, are events that either 1) result in damage to people (injuries, etc.) or 2) result in damage or loss to the environment or property.  Of course, injuries and fatalities are the worst possible outcome and we all work to prevent them as much as possible.  That is always the first [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Incidents, as we define them, are events that either 1) result in damage to people (injuries, etc.) or 2) result in damage or loss to the environment or property.  Of course, injuries and fatalities are the worst possible outcome and we all work to prevent them as much as possible.  That is always the first focus.</p>
<p>However, we also want to track the amount of money involved in the other types of incidents.  These can be a powerful motivator for people to really understand what is happening at all levels in a company, and to realize substantial cost savings.</p>
<p>Many times people do not want to track these as the idea of a higher incident count is not appealing.  Lost a ladder at a job-site?  1 more incident this month.  Computer equipment stolen from head office?  Another one.  If someone looks at this and sees a large incident count, then they might draw the wrong conclusions, the thinking goes.</p>
<p>The industry already does a good job of this currently however.  The difference is that those incidents are not reportable, whereas classes of injuries are reportable.  We are doing our best to educate people on this, as the value of tracking losses can be a great way to have Incident Check pay for itself and more.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/loss-tracking-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Participation Tax&#8221;</title>
		<link>http://www.incidentcheck.com/index.php/participation-tax/</link>
		<comments>http://www.incidentcheck.com/index.php/participation-tax/#comments</comments>
		<pubDate>Thu, 31 May 2012 15:20:30 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=227</guid>
		<description><![CDATA[An article in Inc. Magazine sums up the reason why we don&#8217;t charge per user in Incident Check.  We don&#8217;t want to penalize companies for having more users in the system; in fact, we want the opposite, ideally everyone that needs to use the system should have access. In the safety area, particularly, company and [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>An article in Inc. Magazine sums up <a href="http://www.inc.com/magazine/201206/jason-fried/huge-accounts-make-me-nervous-it-takes-a-village.html" target="_blank">the reason why we don&#8217;t charge per user in Incident Check</a>.  We don&#8217;t want to penalize companies for having more users in the system; in fact, we want the opposite, ideally everyone that needs to use the system should have access.</p>
<p>In the safety area, particularly, company and workplace safety is everyone&#8217;s responsibility, so we would not want to stop people from using the best system out there for entering incidents, near misses, and hazards &#8211; Incident Check.</p>
<p>No &#8220;Participation Tax&#8221; here.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/participation-tax/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Other Changes</title>
		<link>http://www.incidentcheck.com/index.php/other-changes/</link>
		<comments>http://www.incidentcheck.com/index.php/other-changes/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:19:47 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Uncategorized]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=185</guid>
		<description><![CDATA[The major change in the latest release, as already blogged about, is the Report Group Access Restriction.  There are a couple of other changes worth mentioning as well, however: 1.  Alerts on Custom Incident Types: Following up to our immediately successful and well used Custom Incident Types, we added the ability to alert on those [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The major change in the latest release, as already blogged about, is the Report Group Access Restriction.  There are a couple of other changes worth mentioning as well, however:</p>
<p>1.  Alerts on Custom Incident Types: Following up to our immediately successful and well used Custom Incident Types, we added the ability to alert on those incident types when setting up automated emails.  You will now see this in the Alerts section of the Settings area (Admins only, of course).</p>
<p>2.  Incident Breakdown Chart: In general we hear a lot that <a title="pie charts are bad" href="http://www.stevefenton.co.uk/Content/Pie-Charts-Are-Bad/">Pie Charts are Bad</a>.  But, in this case we could not resist and truly feel that they are a great upgrade over the previous bar chart.  To illustrate the point, consider the following (fake data from 3CIS):</p>
<p><a href="http://www.incidentcheck.com/wp-content/uploads/2012/05/chart.png"><img class="alignnone size-full wp-image-186" src="http://www.incidentcheck.com/wp-content/uploads/2012/05/chart.png" alt="" width="800" height="576" /></a></p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>We feel that this chart gives us the most immediate impact of determining what we need to work on.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/other-changes/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Report grouping is Now Active!</title>
		<link>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/</link>
		<comments>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/#comments</comments>
		<pubDate>Tue, 22 May 2012 17:10:59 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[New Features]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=179</guid>
		<description><![CDATA[The latest release to Incident Check is out and active, and here is rundown of the most significant change &#8211; Report Group Access Restriction. Many of our customers need to limit access to reports for different divisions of their companies.  Currently, we have two access levels &#8211; Reporters and Administrators.  Reporters add and edit their [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>The latest release to Incident Check is out and active, and here is rundown of the most significant change &#8211; Report Group Access Restriction.</p>
<p>Many of our customers need to limit access to reports for different divisions of their companies.  Currently, we have two access levels &#8211; Reporters and Administrators.  Reporters add and edit their own reports and can only see what they have entered, whereas Administrators see and have access to everything.</p>
<p>However, there is an in-between access level that we have now addressed.  The challenge from the technical point of view was how to provide this functionality in a way that supports all of our various customers from the many different industries that have a strong safety component to them.</p>
<p>We have done this through our report groups, the current mechanism for &#8216;tagging&#8217; reports with company specific information &#8211; things like Division, Contractor, Operating Company, Supervisor, and many others defined by our users.  Now you can assign users into one or more of these groups and they will only see the appropriately tagged reports.</p>
<p>For people contemplating using this mechanism, all that is needed is to decide what characteristics you would like to use to restrict access, and then use the Settings area (available to admins only) to make this a locked and mandatory group.  Then simply add people to that group.</p>
<p>We are very excited to hear how our customers start using this feature and we are looking forward to feedback.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/report-grouping-is-now-active/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>5 Whys</title>
		<link>http://www.incidentcheck.com/index.php/5-whys/</link>
		<comments>http://www.incidentcheck.com/index.php/5-whys/#comments</comments>
		<pubDate>Wed, 09 May 2012 16:24:12 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Incident Check]]></category>
		<category><![CDATA[Safety Concerns]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=172</guid>
		<description><![CDATA[Ran across this nice little article about root cause analysis with your kids: When Kids Start Doing Root Cause Analysis. With Incident Check, we focus on the root cause analysis and provide a completely customizable  set of factors that are set up by your safety professional. We start with a basic set, but you are [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>Ran across this nice little article about root cause analysis with your kids: <a title="root cause" href="http://blog.marksweep.com/post/22692428919/when-kids-start-doing-root-cause-analysis"> When Kids Start Doing Root Cause Analysis</a>.</p>
<p>With Incident Check, we focus on the root cause analysis and provide a completely customizable  set of factors that are set up by your safety professional.</p>
<p>We start with a basic set, but you are free to remove all of them in order to set things up to work best with your company.  Our initial set consists of Immediate and Root Causes.  Under Immediate causes we have Unsafe Conditions and Unsafe Practices, under Root Causes we have Systemic Factors, Peronal factors, and Job factors.  We feel this is a very good base for people to use to really get at what is important &#8211; figuring out the underlying reasons for incidents and doing our best to eliminate them.</p>
<p>This is highlighted in our Pareto Charts that show the top 80% of factors leading to incidents, near misses, or hazards.  And we find that these charts become much more valuable over time.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/5-whys/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>&#8220;Why is your product so cheap?&#8221;</title>
		<link>http://www.incidentcheck.com/index.php/why-is-your-product-so-cheap/</link>
		<comments>http://www.incidentcheck.com/index.php/why-is-your-product-so-cheap/#comments</comments>
		<pubDate>Fri, 27 Apr 2012 15:46:01 +0000</pubDate>
		<dc:creator><![CDATA[james]]></dc:creator>
				<category><![CDATA[Best Practices]]></category>
		<category><![CDATA[Incident Check]]></category>

		<guid isPermaLink="false">http://www.incidentcheck.com/?p=168</guid>
		<description><![CDATA[This is a question I get many times when talking with potential and existing clients.  First, I like to change that to &#8220;inexpensive&#8221;, as a marketer once coached us. Second, most of the people asking are used to dealing with 2 different types of situations: In-house IT departments &#8220;Enterprise&#8221; Software Sales With Incident Check, we [&#8230;]]]></description>
				<content:encoded><![CDATA[<p>This is a question I get many times when talking with potential and existing clients.  First, I like to change that to &#8220;inexpensive&#8221;, as a marketer once coached us.</p>
<p>Second, most of the people asking are used to dealing with 2 different types of situations:</p>
<ul>
<li>In-house IT departments</li>
<li>&#8220;Enterprise&#8221; Software Sales</li>
</ul>
<p>With Incident Check, we have taken a different approach &#8211; Software as a Service (Saas) and we have specifically targeted safety management systems, incident tracking systems, incident management systems, etc. (as they are variously called in the industry) because we see a perfect fit in the safety area for a product that brings together best practices and procedures and provides great value to many companies.</p>
<p>For many customers, they have previously had (or tried to have) solutions built by in-house IT departments.  These can be successful, but many times IT departments are overworked, resulting in long times to development and large budgets.  Or just simply not having the capacity to deliver. And at the end you have a product that met your needs 8 to 12 months ago when you asked for it initially.</p>
<p>The other model we see in this industry is the &#8220;Enterprise&#8221; sales.  People working for those companies will explain how amazing their software is and how it can do everything, and will talk your ear off about everything except price.  Getting a price on a system from them is akin to pulling teeth, which is odd considering that you want to give them money.  Eventually you will get a price but they are built on formulas that Einstein would have problems with so you are left with nagging doubts as to if you received good value for your money.</p>
<p><a title="3CIS" href="http://www.3cis.com">3CIS</a> looked at the safety industry and thought &#8211; &#8220;No company uses safety as a trade secret, so we can collaborate to provide the best system out there.&#8221;  The information sharing nature that occurs in this industry benefits everyone at all levels.  Think about it &#8211; if you found a formula to reduce accidents in the workplace for a company you work for, would you hoard that information and use it in recruitment materials?  We don&#8217;t think so, which leads to people sharing their research, results, etc.</p>
<p>When it comes to providing a system to meet the data-capturing requirements and followup, we follow the same line of thinking to capture feedback from existing customers in order to make the product better for ALL customers.</p>
<p>Don&#8217;t let the price throw you off &#8211; we have all the features that companies need, and our product continually evolves to keep up with changing requirements and best practices in the industry.  And that beats &#8220;Enterprise&#8221; any day.</p>
<p>&nbsp;</p>
]]></content:encoded>
			<wfw:commentRss>http://www.incidentcheck.com/index.php/why-is-your-product-so-cheap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
