<?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: Avoid first-mover disadvantage</title>
	<atom:link href="http://jboye.com/blogpost/avoid-first-mover-disadvantage/feed/" rel="self" type="application/rss+xml" />
	<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/</link>
	<description>The international community for web and intranet professionals</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:45:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.1.2</generator>
	<item>
		<title>By: J. Boye &#124; Keine Experimente</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-3896</link>
		<dc:creator>J. Boye &#124; Keine Experimente</dc:creator>
		<pubDate>Thu, 11 Mar 2010 22:24:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-3896</guid>
		<description>[...] Instead of blindly experimenting and hoping for the best, use the vast knowledge that already exists to find tested solutions to your problems and requirements. You can tap into an endless source of inspiration by talking to your peers willing to share their lessons learned. If you are not able to find a reference for a given user experience, product or intranet application, it might be wise to wait and avoid potential first mover disadvantage. [...]</description>
		<content:encoded><![CDATA[<p>[...] Instead of blindly experimenting and hoping for the best, use the vast knowledge that already exists to find tested solutions to your problems and requirements. You can tap into an endless source of inspiration by talking to your peers willing to share their lessons learned. If you are not able to find a reference for a given user experience, product or intranet application, it might be wise to wait and avoid potential first mover disadvantage. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Boye &#187; Blog Archive &#187; Be careful with SharePoint integrators</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1959</link>
		<dc:creator>J. Boye &#187; Blog Archive &#187; Be careful with SharePoint integrators</dc:creator>
		<pubDate>Tue, 23 Jun 2009 04:54:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1959</guid>
		<description>[...] no SharePoint references on the same version as they are offering you, you risk being exposed to first-mover disadvantage. If you want to avoid paying for training the integrator, you should make references from related [...]</description>
		<content:encoded><![CDATA[<p>[...] no SharePoint references on the same version as they are offering you, you risk being exposed to first-mover disadvantage. If you want to avoid paying for training the integrator, you should make references from related [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janus Boye</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1957</link>
		<dc:creator>Janus Boye</dc:creator>
		<pubDate>Tue, 23 Jun 2009 04:06:09 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1957</guid>
		<description>&quot;Leading edge is bleeding edge&quot;</description>
		<content:encoded><![CDATA[<p>&#8220;Leading edge is bleeding edge&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Boye &#187; Blog Archive &#187; eXo Portal and JBoss Portal join forces</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1651</link>
		<dc:creator>J. Boye &#187; Blog Archive &#187; eXo Portal and JBoss Portal join forces</dc:creator>
		<pubDate>Wed, 10 Jun 2009 12:30:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1651</guid>
		<description>[...] old product and then be faced with the aforementioned upgrade or would you rather risk potential first-mover disadvantages by waiting for the new [...]</description>
		<content:encoded><![CDATA[<p>[...] old product and then be faced with the aforementioned upgrade or would you rather risk potential first-mover disadvantages by waiting for the new [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: J. Boye &#187; Blog Archive &#187; Overlooked SharePoint success factors</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1609</link>
		<dc:creator>J. Boye &#187; Blog Archive &#187; Overlooked SharePoint success factors</dc:creator>
		<pubDate>Mon, 08 Jun 2009 12:45:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1609</guid>
		<description>[...] Plan for future versions of SharePoint and see if you can be flexible and postpone the implementation of some of your most complex requirements. For the first many months after the release of SharePoint 2010, you need to a avoid first-mover disadvantage. [...]</description>
		<content:encoded><![CDATA[<p>[...] Plan for future versions of SharePoint and see if you can be flexible and postpone the implementation of some of your most complex requirements. For the first many months after the release of SharePoint 2010, you need to a avoid first-mover disadvantage. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anders B. Skjønaa</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1573</link>
		<dc:creator>Anders B. Skjønaa</dc:creator>
		<pubDate>Thu, 04 Jun 2009 14:20:25 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1573</guid>
		<description>Thanks for this post, Janus... It&#039;s really an interesting and important topic to discuss, since we all have to think hard about the pros and cons of everything we do - all the time.

It is my opinion - and experience as well - that new technology CAN open up for new opportunities for businesses. But the technology will never do so by itself - expectations and risks must be managed strictly.

All technologies mature over time. Remember that this is the result of someone that &quot;moves first&quot; and get the experience and the advantages first as well. There is no factual proof that states that these experiences - in GENERAL - are more expensive than the advantages thay may give.

That said - first movers on new technology - can absolutely end up in very unfortunate situations and end up paying far to high prices to maintain a reasonable business case. 

Since SharePoint is mentioned as an example in this post - and since this is an area where I spend a lot of time cleaning up messy projects and implementations - let me explain my view on why so many companies have been experiencing the difficulties thay have.

With SharePoint being a faily complex platform, it is my experience that a large percentage of companies have not had a solid understanding of the technology before implementing it. Martin White has an excellent post about this very issue (http://www.intranetfocus.com/blog/entry.php?entry=50). In this post Martin White explains the need for structured governance in SharePoint project - especially in larger organizations. 

With SharePoint the need for governance is the single largest factor to why organization are facing issues. This is really due to the fact that many organizations have not spend the time to investigate and plan their SharePoint implementations before hitting the &quot;setup-button&quot;. Guides, best practices and information have been available from the beginning (With SharePoint a large number of companies participated in early deployment programs, where Microsoft invested heavily in learning real life experiences from real life projects) but for some reason most companies dont use this information.

So what should we do then? Well - one solution is to wait for everyone else to move first and then hope that they are willing to share experiences. Another approach is to find people that can help you manage and plan your project. Yes this has a price - but I would argue anytime that the businesscase in being &quot;first to market&quot; a new service or product (which should be the reason to why you would implement a new technology in the first place) will often be very interesting. 

Examples; How Danfoss used the SmartWorker approach (a business-value driven proces to evaluating and implementing new software tool for knowledge workers) to implementing technologies like Outlook and SharePoint: http://www.franklincovey.dk/home.asp?ContentID=235</description>
		<content:encoded><![CDATA[<p>Thanks for this post, Janus&#8230; It&#8217;s really an interesting and important topic to discuss, since we all have to think hard about the pros and cons of everything we do &#8211; all the time.</p>
<p>It is my opinion &#8211; and experience as well &#8211; that new technology CAN open up for new opportunities for businesses. But the technology will never do so by itself &#8211; expectations and risks must be managed strictly.</p>
<p>All technologies mature over time. Remember that this is the result of someone that &#8220;moves first&#8221; and get the experience and the advantages first as well. There is no factual proof that states that these experiences &#8211; in GENERAL &#8211; are more expensive than the advantages thay may give.</p>
<p>That said &#8211; first movers on new technology &#8211; can absolutely end up in very unfortunate situations and end up paying far to high prices to maintain a reasonable business case. </p>
<p>Since SharePoint is mentioned as an example in this post &#8211; and since this is an area where I spend a lot of time cleaning up messy projects and implementations &#8211; let me explain my view on why so many companies have been experiencing the difficulties thay have.</p>
<p>With SharePoint being a faily complex platform, it is my experience that a large percentage of companies have not had a solid understanding of the technology before implementing it. Martin White has an excellent post about this very issue (<a href="http://www.intranetfocus.com/blog/entry.php?entry=50" rel="nofollow">http://www.intranetfocus.com/blog/entry.php?entry=50</a>). In this post Martin White explains the need for structured governance in SharePoint project &#8211; especially in larger organizations. </p>
<p>With SharePoint the need for governance is the single largest factor to why organization are facing issues. This is really due to the fact that many organizations have not spend the time to investigate and plan their SharePoint implementations before hitting the &#8220;setup-button&#8221;. Guides, best practices and information have been available from the beginning (With SharePoint a large number of companies participated in early deployment programs, where Microsoft invested heavily in learning real life experiences from real life projects) but for some reason most companies dont use this information.</p>
<p>So what should we do then? Well &#8211; one solution is to wait for everyone else to move first and then hope that they are willing to share experiences. Another approach is to find people that can help you manage and plan your project. Yes this has a price &#8211; but I would argue anytime that the businesscase in being &#8220;first to market&#8221; a new service or product (which should be the reason to why you would implement a new technology in the first place) will often be very interesting. </p>
<p>Examples; How Danfoss used the SmartWorker approach (a business-value driven proces to evaluating and implementing new software tool for knowledge workers) to implementing technologies like Outlook and SharePoint: <a href="http://www.franklincovey.dk/home.asp?ContentID=235" rel="nofollow">http://www.franklincovey.dk/home.asp?ContentID=235</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Velasco</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1571</link>
		<dc:creator>Stephen Velasco</dc:creator>
		<pubDate>Thu, 04 Jun 2009 09:25:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1571</guid>
		<description>I would have to respectfully disagree with Bo with regards to his example of the iPod and its classification of Apple as a first mover. The iPod while opening the media player world to a number of new customers, is not - i feel - an example of Apple as &quot;first mover&quot;. The first movers in that area would be the MPMan and the Diamond Rio. So much so, that Diamond was served with an injunction against sale (later revoked). Apple, I feel, would be more akin to the Japanese producers of CD players (for example) taking the invention from Philips (the first) and improving the design and making the technology more accessible. Apple&#039;s strength was in the marketing of the player as &quot;easy to use&quot; and as a &quot;must have&quot; accessory.</description>
		<content:encoded><![CDATA[<p>I would have to respectfully disagree with Bo with regards to his example of the iPod and its classification of Apple as a first mover. The iPod while opening the media player world to a number of new customers, is not &#8211; i feel &#8211; an example of Apple as &#8220;first mover&#8221;. The first movers in that area would be the MPMan and the Diamond Rio. So much so, that Diamond was served with an injunction against sale (later revoked). Apple, I feel, would be more akin to the Japanese producers of CD players (for example) taking the invention from Philips (the first) and improving the design and making the technology more accessible. Apple&#8217;s strength was in the marketing of the player as &#8220;easy to use&#8221; and as a &#8220;must have&#8221; accessory.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bo Møller</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1561</link>
		<dc:creator>Bo Møller</dc:creator>
		<pubDate>Wed, 03 Jun 2009 10:24:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1561</guid>
		<description>Hi there.

First, thanks for writing good blogposts!

Right now I&#039;m actually listining to music from my iPod, which is a great example.
Apple launched the iPod and created a whole market, gaining supreme first mover advantages.

The point should not be that we are all to follow companies like Apple. The point is to keep in mind that a golden direction does not exist. Chose a strategy that makes sence in your segment.

Bo.</description>
		<content:encoded><![CDATA[<p>Hi there.</p>
<p>First, thanks for writing good blogposts!</p>
<p>Right now I&#8217;m actually listining to music from my iPod, which is a great example.<br />
Apple launched the iPod and created a whole market, gaining supreme first mover advantages.</p>
<p>The point should not be that we are all to follow companies like Apple. The point is to keep in mind that a golden direction does not exist. Chose a strategy that makes sence in your segment.</p>
<p>Bo.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Janus Boye</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1560</link>
		<dc:creator>Janus Boye</dc:creator>
		<pubDate>Wed, 03 Jun 2009 08:16:05 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1560</guid>
		<description>Hi Bo,

Thanks for commenting.

Could you provide an example of real value a new system could bring? 

I can&#039;t really imagine a new feature or new version contributing any significant competitive advantage

Cheers,            Janus</description>
		<content:encoded><![CDATA[<p>Hi Bo,</p>
<p>Thanks for commenting.</p>
<p>Could you provide an example of real value a new system could bring? </p>
<p>I can&#8217;t really imagine a new feature or new version contributing any significant competitive advantage</p>
<p>Cheers,            Janus</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bo Møller</title>
		<link>http://jboye.com/blogpost/avoid-first-mover-disadvantage/comment-page-1/#comment-1493</link>
		<dc:creator>Bo Møller</dc:creator>
		<pubDate>Mon, 01 Jun 2009 13:04:14 +0000</pubDate>
		<guid isPermaLink="false">http://www.jboye.com/?p=2380#comment-1493</guid>
		<description>That&#039;s a really good point.
It&#039;s of course a compromise between being upbeat and innovative, and playing it safe. I think you should choose that which brings value to your business.

When choosing a risky first-mover advantage, you might end up giving yourself a disadvantage, as you point out. On the other hand - you might choose a direction that brings so much value, that the potential advantage outweighs the disadvantage.
There&#039;s always a tradeoff of sorts.</description>
		<content:encoded><![CDATA[<p>That&#8217;s a really good point.<br />
It&#8217;s of course a compromise between being upbeat and innovative, and playing it safe. I think you should choose that which brings value to your business.</p>
<p>When choosing a risky first-mover advantage, you might end up giving yourself a disadvantage, as you point out. On the other hand &#8211; you might choose a direction that brings so much value, that the potential advantage outweighs the disadvantage.<br />
There&#8217;s always a tradeoff of sorts.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

