<?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 for Frictionless Business Ecosystems</title>
	<atom:link href="http://frictionlessbusinessecosystems.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://frictionlessbusinessecosystems.com</link>
	<description>The science of non-friction business</description>
	<lastBuildDate>Sun, 21 Mar 2010 13:11:54 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Why we work with LIXI (pt. 1) by Why we work with LIXI (pt. 2) &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2010/03/why-we-work-with-lixi-pt-1/comment-page-1/#comment-24</link>
		<dc:creator>Why we work with LIXI (pt. 2) &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Sun, 21 Mar 2010 13:11:54 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=109#comment-24</guid>
		<description>[...] the previous post I described how the Australian lending industry was a great example of friction-loaded business [...]</description>
		<content:encoded><![CDATA[<p>[...] the previous post I described how the Australian lending industry was a great example of friction-loaded business [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Friction: A Recap and Overview by Why we work with LIXI (pt. 1) &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2010/03/friction-a-recap-and-overview/comment-page-1/#comment-23</link>
		<dc:creator>Why we work with LIXI (pt. 1) &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Sun, 14 Mar 2010 13:18:19 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=99#comment-23</guid>
		<description>[...] That&#8217;s at least nine different, operationally independent parties involved in handling your new property purchase, and clearly a classic example of a business ecosystem. Those with an eye for process efficiency will also recognise at least nine sources of transactional (Type 1) friction, not counting those activities within an organisation that may also be friction-loaded. (This, and the other forms of friction were described in the previous post.) [...]</description>
		<content:encoded><![CDATA[<p>[...] That&#8217;s at least nine different, operationally independent parties involved in handling your new property purchase, and clearly a classic example of a business ecosystem. Those with an eye for process efficiency will also recognise at least nine sources of transactional (Type 1) friction, not counting those activities within an organisation that may also be friction-loaded. (This, and the other forms of friction were described in the previous post.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Welcome by Friction: A Recap and Overview &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2009/11/hello-world/comment-page-1/#comment-20</link>
		<dc:creator>Friction: A Recap and Overview &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Sun, 07 Mar 2010 13:14:55 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=1#comment-20</guid>
		<description>[...] the very first post on this site I described how our team&#8217;s R&amp;D work was concerned with reducing friction in [...]</description>
		<content:encoded><![CDATA[<p>[...] the very first post on this site I described how our team&#8217;s R&amp;D work was concerned with reducing friction in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Avoiding the ‘Meltdown Scenario’ by Seeking industry validation partners &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2009/11/avoiding-the-%e2%80%98meltdown-scenario%e2%80%99/comment-page-1/#comment-18</link>
		<dc:creator>Seeking industry validation partners &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Sun, 28 Feb 2010 13:35:07 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=21#comment-18</guid>
		<description>[...] is piece of software that sits (non-intrusively) within a service-oriented IT environment and helps avoid the meltdown scenario, complimenting our performance modeling and simulation technology.  It can sense ‘trouble’ – [...]</description>
		<content:encoded><![CDATA[<p>[...] is piece of software that sits (non-intrusively) within a service-oriented IT environment and helps avoid the meltdown scenario, complimenting our performance modeling and simulation technology.  It can sense ‘trouble’ – [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Business rules and forms processing by Validating your business rules &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2010/02/business-rules-and-forms-processing/comment-page-1/#comment-17</link>
		<dc:creator>Validating your business rules &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Tue, 16 Feb 2010 13:14:25 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=79#comment-17</guid>
		<description>[...] the previous post I described the nascent need for business rules and their implementation in new software systems.  [...]</description>
		<content:encoded><![CDATA[<p>[...] the previous post I described the nascent need for business rules and their implementation in new software systems.  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Head in the clouds (part 1) by Dr. Anna Liu, Project Leader, NICTA Business Adaptation and Interoperation &#8594; Frictionless Business Ecosystems</title>
		<link>http://frictionlessbusinessecosystems.com/2009/12/head-in-the-clouds-part-1/comment-page-1/#comment-16</link>
		<dc:creator>Dr. Anna Liu, Project Leader, NICTA Business Adaptation and Interoperation &#8594; Frictionless Business Ecosystems</dc:creator>
		<pubDate>Sun, 31 Jan 2010 22:57:23 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=37#comment-16</guid>
		<description>[...] was only about 6 weeks ago that I reported on Anna&#8217;s position as contributed staff from UNSW (although some months earlier than that when [...]</description>
		<content:encoded><![CDATA[<p>[...] was only about 6 weeks ago that I reported on Anna&#8217;s position as contributed staff from UNSW (although some months earlier than that when [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Head in the clouds (part 1) by John Brondum</title>
		<link>http://frictionlessbusinessecosystems.com/2009/12/head-in-the-clouds-part-1/comment-page-1/#comment-10</link>
		<dc:creator>John Brondum</dc:creator>
		<pubDate>Thu, 17 Dec 2009 22:21:49 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=37#comment-10</guid>
		<description>Companies have outsourced resources, applications and whole business units for at least a decade or more, and as such the security concerns are no difference to those of Cloud Computing . The difference is probably more a question of (perceived) control, but the real question for both is more about who has access (both in terms of regulatory and privacy) and how the access control is enforced (both IT and policy matter) than a question of where the data is hosted. Data can be hosted in Australia, but potentially equally accessible by support staff from Australia, Brazil, Ireland, China, India or anywhere else in the World - no difference (assuming fast Internet connection). Regulatory access is probably the only aspect where location plays a (significant) role. 

And I also think that there is an emotional aspect to all of this - we think we know what&#039;s &#039;local&#039; (e.g., Australian), whereas Cloud Computing is &#039;global&#039; and therefore inherently less known = less trustworthy.</description>
		<content:encoded><![CDATA[<p>Companies have outsourced resources, applications and whole business units for at least a decade or more, and as such the security concerns are no difference to those of Cloud Computing . The difference is probably more a question of (perceived) control, but the real question for both is more about who has access (both in terms of regulatory and privacy) and how the access control is enforced (both IT and policy matter) than a question of where the data is hosted. Data can be hosted in Australia, but potentially equally accessible by support staff from Australia, Brazil, Ireland, China, India or anywhere else in the World &#8211; no difference (assuming fast Internet connection). Regulatory access is probably the only aspect where location plays a (significant) role. </p>
<p>And I also think that there is an emotional aspect to all of this &#8211; we think we know what&#8217;s &#8216;local&#8217; (e.g., Australian), whereas Cloud Computing is &#8216;global&#8217; and therefore inherently less known = less trustworthy.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vested interests by Paul M.</title>
		<link>http://frictionlessbusinessecosystems.com/2009/12/vested-interests/comment-page-1/#comment-8</link>
		<dc:creator>Paul M.</dc:creator>
		<pubDate>Wed, 16 Dec 2009 23:06:51 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=26#comment-8</guid>
		<description>Thanks Nick, and I&#039;m sorry it&#039;s taken me longer to follow this up than intended.
I&#039;m certain there are more factors than the described vested interests that are sources of e-commerce (and e-health) friction. And certainly I wouldn&#039;t want to trivialise all of the other economic, political and technical challenges with creating a straight-through processing world for personal healthcare-related data. The goal of the original piece of course was merely to highlight this one, important, source of friction.
On the issue of incentives and helping people be healthier, I would have thought the argument was simple: If an EHR system reduces to nearly zero the probability of a healthcare worker making an error with my diagnosis and treatment, then I&#039;d pay some reasonable premium in my health insurance or Medicare levy for that.</description>
		<content:encoded><![CDATA[<p>Thanks Nick, and I&#8217;m sorry it&#8217;s taken me longer to follow this up than intended.<br />
I&#8217;m certain there are more factors than the described vested interests that are sources of e-commerce (and e-health) friction. And certainly I wouldn&#8217;t want to trivialise all of the other economic, political and technical challenges with creating a straight-through processing world for personal healthcare-related data. The goal of the original piece of course was merely to highlight this one, important, source of friction.<br />
On the issue of incentives and helping people be healthier, I would have thought the argument was simple: If an EHR system reduces to nearly zero the probability of a healthcare worker making an error with my diagnosis and treatment, then I&#8217;d pay some reasonable premium in my health insurance or Medicare levy for that.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vested interests by Nick Carr</title>
		<link>http://frictionlessbusinessecosystems.com/2009/12/vested-interests/comment-page-1/#comment-6</link>
		<dc:creator>Nick Carr</dc:creator>
		<pubDate>Mon, 14 Dec 2009 03:26:41 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=26#comment-6</guid>
		<description>Paul, I&#039;m not sure about the &#039;vested interests&#039; argument. I feel like it relies on too many disconnected parties cooperating to be plausible.

Lately I&#039;ve been reading a bit about IT and transaction costs. To me this connection plausibly explains a why an investment in technology can sometimes increase costs rather than reduce them. I think this is where healthcare is.

http://www.instant-science.net/pub/tracost.pdf

Computerizing health transactions won&#039;t be cheaper if the move to technology increases uncertainty. Proving security, certifying the people viewing the data and tracking everywhere data has been used and by who is actually going to be pretty hard. 

Until people get an economic incentive to a) accept responsibility for managing their own EHR and b) take some risk with privacy, it is hard to see healthcare being computerized.

As an aside but along the same lines, it seems very rare for this discussion to ever focus on how computerizing will help people be healthier.  Until the discussion moves from industry costs to to incentives and rewards to the consumer, I can&#039;t see the change happening.</description>
		<content:encoded><![CDATA[<p>Paul, I&#8217;m not sure about the &#8216;vested interests&#8217; argument. I feel like it relies on too many disconnected parties cooperating to be plausible.</p>
<p>Lately I&#8217;ve been reading a bit about IT and transaction costs. To me this connection plausibly explains a why an investment in technology can sometimes increase costs rather than reduce them. I think this is where healthcare is.</p>
<p><a href="http://www.instant-science.net/pub/tracost.pdf" rel="nofollow">http://www.instant-science.net/pub/tracost.pdf</a></p>
<p>Computerizing health transactions won&#8217;t be cheaper if the move to technology increases uncertainty. Proving security, certifying the people viewing the data and tracking everywhere data has been used and by who is actually going to be pretty hard. </p>
<p>Until people get an economic incentive to a) accept responsibility for managing their own EHR and b) take some risk with privacy, it is hard to see healthcare being computerized.</p>
<p>As an aside but along the same lines, it seems very rare for this discussion to ever focus on how computerizing will help people be healthier.  Until the discussion moves from industry costs to to incentives and rewards to the consumer, I can&#8217;t see the change happening.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Vested interests by Paul M.</title>
		<link>http://frictionlessbusinessecosystems.com/2009/12/vested-interests/comment-page-1/#comment-5</link>
		<dc:creator>Paul M.</dc:creator>
		<pubDate>Fri, 11 Dec 2009 03:29:50 +0000</pubDate>
		<guid isPermaLink="false">http://frictionlessbusinessecosystems.com/?p=26#comment-5</guid>
		<description>Thanks for this contribution, Brett.
I&#039;d like to have a look at those cases.  The ASX one in particular looks pertinent.
Regarding electronic conveyancing and NECS, I think we are seeing an interesting piece of technology ecosystem history being played out.  I&#039;m not qualified to comment on the &#039;duplicate certificate of title&#039; issue of course - I gather this is something intimately familiar to conveyancers and land titles offices.  But whatever the problem, if it can be resolved and the NECS successfully delivered and adopted, (yes - a lot of &#039;ifs&#039; in there!) it has the potential to be a world class example of infrastructure reform on a whole of industry scale.</description>
		<content:encoded><![CDATA[<p>Thanks for this contribution, Brett.<br />
I&#8217;d like to have a look at those cases.  The ASX one in particular looks pertinent.<br />
Regarding electronic conveyancing and NECS, I think we are seeing an interesting piece of technology ecosystem history being played out.  I&#8217;m not qualified to comment on the &#8216;duplicate certificate of title&#8217; issue of course &#8211; I gather this is something intimately familiar to conveyancers and land titles offices.  But whatever the problem, if it can be resolved and the NECS successfully delivered and adopted, (yes &#8211; a lot of &#8216;ifs&#8217; in there!) it has the potential to be a world class example of infrastructure reform on a whole of industry scale.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
