<?xml version="1.0" encoding="UTF-8"?>
<!-- generator="wordpress/2.3.3" -->
<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/"
	>

<channel>
	<title>Medical Connectivity &#187; Business Planning</title>
	<link>http://medicalconnectivity.com</link>
	<description></description>
	<pubDate>Thu, 15 May 2008 21:33:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.3</generator>
	<language>en</language>
			<item>
		<title>Selling Connectivity - New Knowledge</title>
		<link>http://medicalconnectivity.com/2008/04/30/selling-connectivity-new-knowledge/</link>
		<comments>http://medicalconnectivity.com/2008/04/30/selling-connectivity-new-knowledge/#comments</comments>
		<pubDate>Wed, 30 Apr 2008 17:57:20 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Business Planning]]></category>

		<category><![CDATA[business delivery system]]></category>

		<category><![CDATA[selling connectivity]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/04/30/selling-connectivity-new-knowledge/</guid>
		<description><![CDATA[With connectivity, the vendor is inexorably forced to give up the rigid control they enjoy with their black box and support the standards and typical options of the general purpose computing world.]]></description>
			<content:encoded><![CDATA[<p>The most striking lesson that I&#8217;ve experienced, and witnessed repeatedly, is that when it comes to connectivity, &#8220;you don&#8217;t know what you don&#8217;t know.&#8221; This applies to providers (buyers) as much as it does vendors (sellers). When presented with a new problem, it&#8217;s human nature to apply current knowledge and mental models in search of a solution - thus the perennial appeal of the &#8220;intuitively obvious.&#8221; Intellectually we know that problems don&#8217;t all fall into the same logical framework. But, for various reasons we tend to apply known solutions to new problems, and only when the outcome is unacceptable do we contemplate the unknown. Decision making <a href="http://ezinearticles.com/?Einstein---Definition-of-Insanity&amp;id=12047">insanity</a> aside, this typical approach is inefficient - or worse.</p>
<p>The barrier to effectively applying the intuitively obvious to connectivity results from  fundamental differences between embedded system devices (i.e., conventional stand alone medical instruments) and the methods and technologies used for connectivity (i.e., general purpose computing technologies). This dichotomy in the application of the different technologies used in both embedded systems and connectivity, extends from product design to regulatory, manufacturing, marketing, sales, installation, service and support. For the vendor, the entire business delivery system is affected. Provider processes - needs assessment, vendor selection, implementation and ongoing internal support - are impacted as well by these differences.</p>
<p>So how are embedded systems different from connectivity? Embedded systems embody the following concepts: <a href="http://medicalconnectivity.com/2008/04/30/selling-connectivity-new-knowledge/#more-1181" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/04/30/selling-connectivity-new-knowledge/feed/</wfw:commentRss>
		</item>
		<item>
		<title>Selling Connectivity - A Series</title>
		<link>http://medicalconnectivity.com/2008/04/16/selling-connectivity-a-series/</link>
		<comments>http://medicalconnectivity.com/2008/04/16/selling-connectivity-a-series/#comments</comments>
		<pubDate>Thu, 17 Apr 2008 02:40:57 +0000</pubDate>
		<dc:creator>Tim Gee</dc:creator>
		
		<category><![CDATA[Business Planning]]></category>

		<category><![CDATA[sales]]></category>

		<category><![CDATA[selling connectivity]]></category>

		<guid isPermaLink="false">http://medicalconnectivity.com/2008/04/16/selling-connectivity-a-series/</guid>
		<description><![CDATA[You've heard all the questions and know all the answers.]]></description>
			<content:encoded><![CDATA[<p>I&#8217;ve written much in the past about the technical and product development issues of connectivity. Just as important are the issues that revolve around successfully selling your connectivity solution. (If you&#8217;re a provider reading this, this should provide a bit of insight into how to buy connectivity, and why sometimes vendors to the crazy things they do.)</p>
<p>You can place two seemingly identical medical devices side by side, with the only visible difference being that one has an Ethernet connector and the other does not. That &#8220;small&#8221; change makes a world of difference when it comes to selling these two devices. Here&#8217;s my list of the areas where adding connectivity to a medical device changes almost everything:</p>
<ul>
<li>Required new knowledge</li>
<li>Qualifying prospects</li>
<li>Dealing with new decision makers (typically with veto power)</li>
<li>Selling a solution, rather than selling the box</li>
<li>Selling one-off systems, rather than cookie cutter widgets</li>
<li>Aligning incentives</li>
<li>Making it work, getting paid</li>
<li>Keeping the customer happy, keeping the system working</li>
<li>Customers want a whole product solution</li>
</ul>
<p> <a href="http://medicalconnectivity.com/2008/04/16/selling-connectivity-a-series/#more-1179" class="more-link">(more&#8230;)</a></p>
]]></content:encoded>
			<wfw:commentRss>http://medicalconnectivity.com/2008/04/16/selling-connectivity-a-series/feed/</wfw:commentRss>
		</item>
	</channel>
</rss>
